How future-proof is the Google cloud portfolio?

Google is known for “just” throw a new service on the market. That’s their corporate culture. It promotes creativity within the company and ensures innovation. But at the end of the day also Google must be clean up the playground. This resulted in numerous closures of famous and lesser-known services in the recent past. Latest victim is the popular Google Reader. It will be shut down at 1th of July 2013. This naturally raises the question of how vulnerable Google’s cloud services are for a portfolio adjustment. At least the finger on the close button seems to fit very loosely.

Longevity vs. popularity

Google scrubs its Google Reader as its popularity has fallen sharply in the past, Google said. That Google is apparently not quite right here, shows a recent petition against its closure. After all, 20,000+ subscribed against its closing.

Google sometimes gives me the impression that it is like a big kid. They find many things at once exciting (20 percent rule), play with it, investing time and then loses interest and pleasure, when the playmates apparently no longer want to play with it. The concentration phase is only with a few products really high. (From a entrepreneurial point of view correct.)

Companies do not like that

Google is currently making great efforts to broadly make it in the business environment. Regarding current providers such as Microsoft and IBM no easy task. Google’s trump card is that they are born in the cloud and know the rules inside out. Finally, they almost self-developed them.

Nevertheless, the question is permissible. Why should a business use Google cloud services, such as Google Apps or the Google Cloud Platform, if services that are apparently not used sufficiently well, to be suddenly closed? Even if Google has monetized above named cloud solutions now, this question retains its place. Because by the monetization of individual service suddenly gets a new KPI, the revenue!

Google may assume that enterprises will not be thrilled if they suddenly get an e-mail that the service they are using will be closed due to lower attractiveness and revenue figures in three months.

For enterprises, this type of product management is not attractive and Google must learn that enterprises need to be treated differently from private users. Even if the consumerization progresses.

Clean up the portfolio is good, but…

No question, it makes sense to clean up the portfolio steadily. It is also recommended for many other providers. However, these seem to act in the interests of their customers and offer their products and services on a long-term roadmap. However, it seems that the finger at the “service close button” at Google sits relatively loose.

I do not think companies will come together for a petition against the closure of Google services. Indeed, you always hear about “too big to fail”, but Google is not as big as all that.


Google Cloud Platform vs. Amazon Web Services – Ein erster Vergleich

Nachdem Google sein Cloud Portfolio mit der Compute Engine erweitert hat, fangen erste Medien an darin den Killer der Amazon Web Services zu sehen. Ein Grund mal die Cloud Services von Google und Amazon gegenüberzustellen. Wer sich für einen direkten Vergleich von Microsoft Windows Azure mit den Amazon Web Services interessiert, sollte hier weiterlesen.

Der Vergleich: Google Cloud vs. Amazon Cloud

Die folgende Tabelle stellt das Cloud Services Portfolio 1:1 gegenüber und schafft Klarheit, wer in welchem Bereich was anbietet, wie der Name des jeweiligen Service lautet und unter welcher URL weitere Informationen zu diesem zu finden sind.


Amazon Web Services

Google Cloud Platform


Virtuelle Maschinen Elastic Compute Cloud Full Virtual Machines (Google Compute Engine)
High Performance Computing Cluster Compute Instances
MapReduce Elastic Map Reduce Google App Engine
Dynamische Skalierung Auto Scaling Google Compute Engine


Unstrukturierter Speicher Simple Storage Service Google Cloud Storage
Flexible Entities SimpleDB
Block Level Storage Elastic Block Store Persistent disk (Google Compute Engine)


RDBMS Relational Database Service Google Cloud SQL, BigQuery
NoSQL DynamoDB “Google F1”


CDN CloudFront
In-Memory ElastiCache


Load Balancer Elastic Load Balancer
Hybrid Cloud Virtual Private Cloud
Peering Direct Connect
DNS Route 53 Public DNS


Async Messaging Simple Queue Service
Push Notifications Simple Notification Service
Bulk Email Simple Email Service


Ressourcen Monitoring CloudWatch


Identitätsmanagement Identity Access Management


Ressourcenerstellung CloudFormation
Web Application Container Elastic Beanstalk Google App Engine

Wie man sieht, ist das Google Cloud Portfolio im Vergleich zum Service Angebot der Amazon Web Services noch sehr dünn. Falls ich etwas bei Google übersehen habe, macht mich darauf bitte aufmerksam. Ich werde das dann umgehend nachtragen.