Maybe old and unsexy, but in terms of simplicity, docker swarm seems to do the job with one major hassle and that is no managed services for it. But in terms of orchestration, same docker compose on local to prod well almost, prod I had to have 16 replicas of a service to handle the load of 6000 concurrent users vs one on my local PC and using larger memory caps since I have 36 machines. The good part as well is there is no other technology stack to deal with, just Docker. I think @Bret pointed out in one of his earlier videos about how most Docker Swarm installations generally fail due to lack of system resources (since the minimum stack is very small) but K8S back in the day required a lot more resources and skills to start.
i love swarm, it kinda makes compose redundant? it might just be me but even for my small local things i run swarm in attachable overlay and haven’t used compose in awhile..
Wow.. Such a GREAT show... Thanks Bret & Eric🍻
Maybe old and unsexy, but in terms of simplicity, docker swarm seems to do the job with one major hassle and that is no managed services for it. But in terms of orchestration, same docker compose on local to prod well almost, prod I had to have 16 replicas of a service to handle the load of 6000 concurrent users vs one on my local PC and using larger memory caps since I have 36 machines. The good part as well is there is no other technology stack to deal with, just Docker.
I think @Bret pointed out in one of his earlier videos about how most Docker Swarm installations generally fail due to lack of system resources (since the minimum stack is very small) but K8S back in the day required a lot more resources and skills to start.
i love swarm, it kinda makes compose redundant? it might just be me but even for my small local things i run swarm in attachable overlay and haven’t used compose in awhile..