Centurion vs Docker Swarm: What are the differences?
Centurion: A mass deployment tool for Docker fleets. A deployment tool for Docker, made by New Relic. Takes containers from a Docker registry and runs them on a fleet of hosts with the correct environment variables, host volume mappings, and port mappings. Supports rolling deployments out of the box, and makes it easy to ship applications to Docker servers. New Relic is using it to run their production infrastructure; Docker Swarm: Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
Centurion and Docker Swarm can be primarily classified as "Container" tools.
Centurion and Docker Swarm are both open source tools. Docker Swarm with 5.63K GitHub stars and 1.11K forks on GitHub appears to be more popular than Centurion with 1.72K GitHub stars and 111 GitHub forks.
What is Centurion?
What is Docker Swarm?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Centurion?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Centurion?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...