What does it really mean to “run like Google”? Is that even a good idea? Andrew Shafer comes back to the podcast to talk with Coté about how the Google SRE book and the newly announced Google CRE program start addressing those questions. We discuss some of the general principals, and “small” ones too that are in those bodies of work and how they represent an interesting evolution of it IT management is done. Many of the concepts that the DevOps and cloud-native community talks about pop in Google’s approach to operations and software delivery, providing a good, hyper-scale case study of how to do IT management and software development for distributed applications. We also discuss Pivotal’s involvement in the Google CRE program.
Check out the SoundCloud listing, or download the MP3 directly.
From 451’s report on Google Next:
Google believes that a hybrid architecture will persist in the coming years as enterprises continue to migrate workloads to various clouds. Its hybrid cloud architecture revolves around its virtual private cloud. Google VPC is an instantiation of GCP that can dedicate compute, storage and network resources to an enterprise. It is built upon Google’s proprietary private global network designed for high reliability, low latency and hardened security. Kubernetes acts as the orchestration and operational backplane for hybrid implementations. Elasticity and scale are achieved by linking to Google public cloud services.
It also has many numbers on market-share, SI/channel development, and geographic foot-print.
Source: Google Cloud Next 2017: Slow and steady race to greater enterprise public cloud adoption
Google is able to automatically reward end users a discount for loyalty through a sustained-use pricing scheme – the company claims its method for high utilization means reservations do not hugely benefit them, and so it would rather reward users for loyalty rather than for paying up front and forecasting capacity. Google also offers a per-minute billing model (as opposed to per-hour offers from many providers), and this advantage can also be attributed in part to containers. However, as we show, the benefit of per-minute billing only becomes important when workloads are very bursty.
Source: Google economics: Containers are the key
Post Alphabet, where any previous inhibitions about pursuing new hobbies have evaporated, it is even harder to imagine the “capital allocators” choosing to invest in thousands of enterprise sales and support people given alternatives involving life extension and/or space elevators. After all, won’t the robotics division eventually solve any problem that today requires humans?
The rest of the state of cloud is pretty good. It’s a regular “pulls no punches and punches everyone” type situation.
If you threw in some charts and numbers, you’d have an even fancier missive, but qualitatively: just Jim-dandy.
From a piece on Google’s history:
In that sentence is buried the heart of a company like Google, a company founded by engineers and with an engineer’s practicality in that something can always be improved upon but you need to get something done now to fix a big problem.