Highlights via Twitter, mostly https://twitter.com/kelseyhightower . Like with any pres. like this, a lot is in the details and you're likely to get more juice out of docs than the slides, and an added disclaimer that I haven't been using GCE and some of this may be old stuff they just talked about today, not actual new hotness.

- moar price cuts (notably, network SSD storage price roughly /= 2): https://twitter.com/googlecloud/status/529684624747032576

- faster local SSD access for 21 cents/gig/month. https://cloud.google.com/pricing/ (search for "Local SSD")

- AWS-style "Autoscaler". https://cloud.google.com/compute/docs/autoscaler/v1beta2/ (They tried to demo activating an autoscaling group by voice. Didn't work. The first rule of demos is never ever rely on voice recognition in a demo.)

- "Container Engine" to simplify deploying Docker images to your VMs--still your VMs, not some kind of container-hosting-replacing-virtual-hosting situation. It's alpha--open but no SLA or pricing yet (free for now). https://cloud.google.com/container-engine/

- They name-dropped that Netflix is using GCE as well as EC2, and that they're integrating Firebase into GCE.

With the Managed VM and Container Engine releases today, is there now a way for frontend Python GAE apps and backend Java GAE/GCE apps to share the same development server (esp datastore, taskqueue)?

So how is it fundamentally different from what they had before - the Compute Engine, App Engine, BigQuery, Prediction API, etc?