3 ms·
Honestly I never understood why Docker stopped at where it's at. Imagine a world where a "docker push aws.io production" leads to an automatically updated dock
by cookiengineer 3y ago
Honestly I never understood why Docker stopped at where it's at.
Imagine a world where a "docker push aws.io production" leads to an automatically updated docker remote, and where the endpoint is automatically NATed, scaled and shutdown if not needed anymore.
Could have been so convenient. Instead there's this pile of networking glue code that's so custom for each platform that nobody wants to deal with load balancers.
In my opinion the biggest "innovation" in the cloud space was heroku back then, where code deployment was fully integrated to the dev workflow via git.
- siquick 3y agoThey kind of have it[0] with ECS deployments but it’s being retired in November. [0] https://docs.docker.com/cloud/ecs-integration/ https://docs.docker.com/cloud/ecs-integration/
- cookiengineer 3y agoThe issue I had with the EC2 deployment workflow was that it needed the AWS CLI configured, so it relied totally on AWS'es locked in workflow. I was thinking more of the lines as a standard API/set of protocols that works on the NAT-scale automatically. Humans are bad at guessing resources, and having people tweak all their VMs all the time with crappy code and crappy APIs is kinda the weakness of all dyno based workflows nowadays. All the "web scale" jokes have a core truth in them, and are actually not so funny for a reason :-/ But relying on a standard set of NAT rules and relationships, which the Dockerfile already provides, could make this an advantage instead.
- re-thc 3y ago> Honestly I never understood why Docker stopped at where it's at. They originally wanted to build docker swarm, which was to compete with kubernetes. Direction 360-ed after that fizzed.
- fomine3 3y agoThey originally dotCloud...