re: How Netflix Is Ruining Cloud Computing
You keep insisting that pre-baking AMIs is somehow adds complexity but have yet to articulate how. Please explain how pre-staging content and configuration on a fixed image prior to launch is any more complex than maintaining push/pull infrastructure and servers to dynamically turn running instances into services. I have no extra infrastructure to maintain to support configuration management other than version control. I have a process that reaps old, unused images. I have, at the end of a bake, an entire OS image that represents a point-in-time configuration of my application that I can refer to for triage. The absolute minimum bake script would be maybe 50 lines of bash? This is more complex....how?
Think of the rate at which the average enterprise is releasing their applications. How many AMIs is a smaller, slower-moving organization really going to produce in reality? Given the cost of S3 storage, is that really a significant cost? If it is...well... *baking is not for them.* Period. Full stop. End of story.
Do people managing 20-node clusters not have the need to roll out identical images too? Do smaller organizations have no need to dynamically manage capacity? What is it about baking that makes you think it's specifically intended for large launches? Every developer at Netflix uses the process, whether their autoscaling group is a single node or 1000 nodes.
Also please explain why you believe that the Netflix platform *depends* on baking in any way, shape, or form. It does not. We choose to bake and feel it is the best thing for us, but it's not required by any component in our infrastructure.
There is nothing whatsoever stopping folks from using Asgard to launch N instances that then have configurations applied to them post launch by Puppet, Chef, Saltstack, cfengine, etc. They just have to wait longer for the instances to become ready to take on traffic than they would if they baked ahead of time. That's the *major* difference.
The Netflix way of "adopting the cloud" is not sub-par in any way *for Netflix.* It's not for everyone, but it works and it works very well. I still fail to see how Netflix or any other organization providing open source software is at all responsible for any enterprise that blindly adopted tooling, process, policy, or anything without evaluating whether or not it made sense in the context of their business. The assertion that Netflix, by virtue of releasing its software and encouraging folks to help improve, extend, and *port it to other clouds*, is somehow beholden to organizations who have no ability to decide whether a solution is the right one is patently absurd.
Op ed and blogging does not disavow one from journalistic integrity. Each and every one of your points could have been addressed by engaging anyone at Netflix. Little things, like ensuring that someone tweeting about 25,000 cowsay AMIs isn't on the team that produced the tooling, or confirming that pre-staged AMIs are mandatory for playing in the ecosystem... Failing to follow through on that before posting a manifesto of FUD will be far more damaging to cloud computing than any contest could ever hope to be.
At this stage, though, we might as well be talking about guns or abortion or right- versus left-wing politics, as your insistence on regurgitating falsehoods underscores the fact that there is no shaking your preconceived notions and biases. I'm going to get back to the herd, 25,000 cows is a lot of cows.