An Interest In:
Web News this Week
- April 19, 2024
- April 18, 2024
- April 17, 2024
- April 16, 2024
- April 15, 2024
- April 14, 2024
- April 13, 2024
Some of Our Sources
- Techcrunch
- Team Treehouse
- Smashing Apps
- Abduzeedo
- Web Designer Depot
- Web Design Ledger
- Reencoded
- Specky Boy
- Design Modo
- Codrops
Help Webnuz
Referal links:
July 14, 2013 11:00 pm GMT
A Google engineer concluded on his Google+ pagelast week that a cloud platform can’t be built without some form of lock-in. That’s evidently true but there really is one main reason for making such a point. Google wants to show that it is not much different from its competitors when it comes to thishot topic with cloud customers. The post by Google Engineering Director Peter Magnusson has to be read with a dash of skepticism. Magnusson does focus on the lock-in issue with Google App Engine (GAE), but he also uses the topic to show the difference between its managed services and the infrastructure as a service (IaaS) from a provider like AWS. He says without restrictions Google could not offer the service that it does. What they do try to do is offer alternatives such as from services like AppScale. Reading into what Magnusson says, it appears that some customers are not accustomed to the restrictions that come with Google App Engine: The run-time environment is different and customers can’t make systems calls, write directly to the file system, or choose their own operating system. In the end, Magnusson says that lock-in is inevitable for Google to offer the service that it does with GAE: You cant build an innovative platform without some measure of lock-in. For example, the Datastore is unlike any other NoSQL or NearSQL service or stack out there. It has multi-datacenter synchronous replication, cursors, distinct queries, projection queries, zigzag merge join, transactional tasks, automatic sharding/load balancing, managed secondary indexes, and multi-row and multi-machine transactions. Our developers dont want us to dumb down those features to some lowest common denominator; they want us to build more features that leverage the unique underlying software systems. GAE comparess to other PaaS providers such as Cloudbees,Heroku,and AppFog, acquired in June by CenturyLink. Google abstracts the actual hands-on work of managing the infrastructure that is a hallmark of other services. That means there are certain aspects of Google’s app service that have to be restricted. These restrictions allow Google to take responsibility for a customer’s firewall, mostdenial of service attacks, viruses — the list goes on. The upside, Magnusson argues, is that for most mobile and web apps, instances can be started quickly, allowing apps to scale fast. Google manages that scale and the problems that arise when, for example, an app has to be moved to another data center.
Original Link: http://feedproxy.google.com/~r/Techcrunch/~3/DSw7F8clclY/
Google Explains Why Its Cloud Service Is Different When It Comes To Lock-In
A Google engineer concluded on his Google+ pagelast week that a cloud platform can’t be built without some form of lock-in. That’s evidently true but there really is one main reason for making such a point. Google wants to show that it is not much different from its competitors when it comes to thishot topic with cloud customers. The post by Google Engineering Director Peter Magnusson has to be read with a dash of skepticism. Magnusson does focus on the lock-in issue with Google App Engine (GAE), but he also uses the topic to show the difference between its managed services and the infrastructure as a service (IaaS) from a provider like AWS. He says without restrictions Google could not offer the service that it does. What they do try to do is offer alternatives such as from services like AppScale. Reading into what Magnusson says, it appears that some customers are not accustomed to the restrictions that come with Google App Engine: The run-time environment is different and customers can’t make systems calls, write directly to the file system, or choose their own operating system. In the end, Magnusson says that lock-in is inevitable for Google to offer the service that it does with GAE: You cant build an innovative platform without some measure of lock-in. For example, the Datastore is unlike any other NoSQL or NearSQL service or stack out there. It has multi-datacenter synchronous replication, cursors, distinct queries, projection queries, zigzag merge join, transactional tasks, automatic sharding/load balancing, managed secondary indexes, and multi-row and multi-machine transactions. Our developers dont want us to dumb down those features to some lowest common denominator; they want us to build more features that leverage the unique underlying software systems. GAE comparess to other PaaS providers such as Cloudbees,Heroku,and AppFog, acquired in June by CenturyLink. Google abstracts the actual hands-on work of managing the infrastructure that is a hallmark of other services. That means there are certain aspects of Google’s app service that have to be restricted. These restrictions allow Google to take responsibility for a customer’s firewall, mostdenial of service attacks, viruses — the list goes on. The upside, Magnusson argues, is that for most mobile and web apps, instances can be started quickly, allowing apps to scale fast. Google manages that scale and the problems that arise when, for example, an app has to be moved to another data center.Original Link: http://feedproxy.google.com/~r/Techcrunch/~3/DSw7F8clclY/
Share this article:
Tweet
View Full Article
Techcrunch
TechCrunch is a leading technology blog, dedicated to obsessively profiling startups, reviewing new Internet products, and breaking tech news.More About this Source Visit Techcrunch