James Sanders at TechReplublic interviews Corey Quinn,
Is Kubernetes better for building a resume than a platform?
Corey is the snarky, observant, and talented author behind Last Week in AWS. If you haven’t subscribed you’re definitely missing out!
Join 35,000 others and follow Sean Hull on twitter @hullsean.
The observation about Kubernetes is not new. My friend & colleague over at Smash Company, Lawrence Krubner, wrote an exhaustive piece commenting on the flaws of docker, kubernetes and their eco-system.
It’s October 7th, 2019. I will revisit the question of Kubernetes demise again in six months. First thing in April 2020 we can see where my prediction stands!
1. Senior engineers are asking hard questions
The new generation of engineers, are more open to new solutions. They’re not bogged down by history, and legacy limitations. They’ll try new things, and embrace new technologies if they can solve a problem.
But senior engineers have been bitten. They’ve had the sorry job of untangling over engineered solutions. They’ve seen small firms live and die by wrong choices, and tech stack decisions. They’ve hit the wall on architectures, that were designed without enough perspective and foresight.
2. Trends come come and go
Kubernetes could go the same way. Not least because AWS has their own ECS.
3. Complexity is getting out of control
Kubernetes is sure great for doing blue-green deployments. And dockerizing all the things, helps developers and ops teams work together. After all just handing over the container asset, means ops can concentrate on deploying that. And kubernetes is great right up to this point.
But what about when kubernetes itself introduces application problems?
What about when kubernetes introduces performance and scalability problems?
And don’t even get me started about the crazy problems of running a database on Kubernetes.