re: How Netflix Is Ruining Cloud Computing
Wow--nothing in my piece says anything about AWS not being modern or me abandoning it. AWS still gets the vast majority of my cloud spend today, and I think it's a wonderful service.
The point is that a *cloud architecture* that *only works with one cloud* is not a good cloud architecture going forward. Good cloud architectures will work with multiple clouds. If I am hiring you as a cloud architect today, and you tell me that you are going to create a greenfield cloud architecture that is going to hook directly into AWS APIs and that you are fundamentally uninterested in testing or supporting any other clouds in the future, then I would fire you on the spot.
I am also a big fan of Netflix's services, of their corporate culture, and of the fact that they're willing to be so open about so many things, including releasing so much source code. (I think I've been a Netflix member for more than 10 years now). The problem is that I am concerned about the vast number of people and organizations who are going to take Netflix's cloud deployment as a reference architecture, which will help Netflix, but will fundamentally set cloud architecture practices back to 2010.
All that said, if the result of this contest is to bring Netflix's tools into the future and make them multi-cloud, and use standardized configuration management, then that will be excellent (as I say at the end of my piece). However, for the many reasons I outlined in my piece, I am deeply skeptical of whether that will happen.