Docker Swarm vs OpenStack: What are the differences?
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; OpenStack: Open source software for building private and public clouds. OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
Docker Swarm and OpenStack are primarily classified as "Container" and "Open Source Cloud" tools respectively.
"Docker friendly" is the top reason why over 43 developers like Docker Swarm, while over 35 developers mention "Private cloud" as the leading cause for choosing OpenStack.
Docker Swarm is an open source tool with 5.61K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.
Bugsnag, Docker, and Dial Once are some of the popular companies that use Docker Swarm, whereas OpenStack is used by PayPal, HubSpot, and Wikipedia. Docker Swarm has a broader approval, being mentioned in 80 company stacks & 38 developers stacks; compared to OpenStack, which is listed in 66 company stacks and 50 developer stacks.
What is Docker Swarm?
What is OpenStack?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using OpenStack?
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...
IaaS for our core private cloud, and with AWS, HP Helion, and Rackspace to burst to public clouds to create a multi-sourced hybrid cloud setup.
필자가 온갖 서버사이드 지식들을 삽질하고 익힐 수 있었던 가장 큰 이유. 현대 퍼블릭/프라이빗 클라우드 환경을 막론하고 가장 표준이 되는 클라우드 플랫폼이다.