Hacker News new | past | comments | ask | show | jobs | submit login

In 2019, would you choose something else for container orchestration?



Yes - I maintain that Swarm is a much simpler offering that's easier to get started with in a 'smaller' setup, or in a mixed environment of monoliths and miniliths and microliths in one big family.

There is much less in terms of cognitive load on the developers, fewer moving parts to know about. Importantly the ability to use the same docker-compose.yml for develop, debug, build, deployment comes with the immense value of the boring sameness that a production deployment should have, and not having to worry over 'one more thing' or 'one more moving part' or 'one more translation layer'.


Swarm might be a simpler option in the sense that FreeBSD is a simpler option than Linux in some cases (perhaps not the most apt comparison, but bear with me). Sure, by itself it may win out on technical merit in some cases, but: * Nothing you want to use will target it as a supported platform. It may very well work, but you're going to be figuring out how it works yourself. * Most community discussion around general architecture/networking/common problems/workarounds for those problems will be for the other, more popular platform. Again, you'll be blazing your own trail.

That all said, figuring how to do this yourself or how to adopt solutions for other platforms can be _fun_. I find it fun. I wish more people found it fun, and believe we'd have a more diverse, vibrant infrastructure ecosystem if most other people also found it fun. In practice, however, I've found that few people find this fun, and those that do have no time to have said fun. Most users I work with ask a combination of "can you provide idiot-proof instructions for this?" and "have other people done this already to hash out the difficult bits?".

For a variety of reasons, Swarm lost the popularity war, and so it doesn't matter what, if anything, it does better.


Same experience here, I feel Docker Swarm is a bit underappreciated. I have experimented with Kubernetes but Swarm seems a lot simpler when you have a mix of stateful and stateless services. You can have many of the benefits of an orchestrator but still manually manage volumes, and configuration files are very understandable.


> Yes - I maintain that Swarm is a much simpler offering that's easier to get started with in a 'smaller' setup, or in a mixed environment of monoliths and miniliths and microliths in one big family.

+1 on Docker Swarm. Although it does have its kinks, it's far simpler to get working, has a smoother learning curve, and does the job well.

I would argue that Docker Swarm is ideal for those cases where it's unlikely you'll need a lot of autoscaling or operate a large cluster.


Nomad is a solid, less complex, alternative. Docker Swarm is also an option. Mesos. I'm sure if you look you can find others.


I'll rephrase..

You probably didn't need "container orchestration"




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: