“Our infrastructure to deploy a single Docker container on AWS.”(twitter.com)
twitter.com
“Our infrastructure to deploy a single Docker container on AWS.”
https://twitter.com/jeremy_levy/status/1312065562915360769
4 comments
Exactly. This is more than just a single Docker container, this is all the architecture necessary to have a highly scalable, high availability setup where you can dial up the number of Docker containers as high as you want at the press of a button.
Not everyone needs all this, but most people who want scale and availability do need all this.
Not everyone needs all this, but most people who want scale and availability do need all this.
I think this is a great example of the existential dread I feel when thinking about modern cloud “solutions” — at what point are there too many moving parts? I say this as someone who administers kubernetes clusters in AWS (kops, not EKS). I’m starting to wonder how much of this abstraction and “scale” is needed for 99% of use cases
“Our infrastructure to deploy a load balancer, certificate store, secret manager, CI pipeline, internal-networked auto-scaling container”.
Alright.
Alright.
Of course it's looking complicated "for a single container", but if you wanted to deploy your app in a traditional server setup, the graph would look the same, if not worse.