This is definitely a visionary post and the title is a little misleading. A more useful title might be: A Vision for a Container-based Production Stack (based

This is definitely a visionary post and the title is a little misleading. A more useful title might be: A Vision for a Container-based Production Stack (based on experiences at Google). I think the post covers the scope of container-related problems very well, but I definitely know of a lot of production stacks that work well and don't look at all like the post describes :) One consideration missing from the post: one day we could very well have a ton of opaque/sealed/closed-source container images provided as SaaS. For example, Oracle could provide their products in containers which you would then use on your own hardware or your own cloud provider. This sort of product would give CIOs a bit more control over OPEX/CAPEX and security. The current post assumes a single central registry. IMO it's more likely containers drive a distributed ecosystem of registries, and container-oriented stacks will need to deal with this.