Docker Compose vs Otto

Overview

Docker Compose

Stacks22.3K

Followers16.5K

Votes501

GitHub Stars36.4K

Forks5.5K

Otto

Stacks27

Followers86

Votes18

GitHub Stars4.2K

Forks214

Docker Compose vs Otto: What are the differences?

Developers describe Docker Compose as "Define and run multi-container applications with Docker". With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. On the other hand, Otto is detailed as "Development and Deployment Made Easy. The successor to Vagrant". Otto automatically builds development environments without any configuration; it can detect your project type and has built-in knowledge of industry-standard tools to setup a development environment that is ready to go. When you're ready to deploy, otto builds and manages an infrastructure, sets up servers, builds, and deploys the application.

Docker Compose can be classified as a tool in the "Container Tools" category, while Otto is grouped under "Virtual Machine Management".

"Multi-container descriptor" is the primary reason why developers consider Docker Compose over the competitors, whereas "Vagrant-like" was stated as the key factor in picking Otto.

Docker Compose and Otto are both open source tools. Docker Compose with 16.4K GitHub stars and 2.52K forks on GitHub appears to be more popular than Otto with 4.41K GitHub stars and 252 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Docker Compose, Otto

Michael

CEO at asencis Ltd

Jan 5, 2021

Needs advice

We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.

272k views272k

Comments

Detailed Comparison

Docker Compose	Otto
With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.	Otto automatically builds development environments without any configuration; it can detect your project type and has built-in knowledge of industry-standard tools to setup a development environment that is ready to go. When you're ready to deploy, otto builds and manages an infrastructure, sets up servers, builds, and deploys the application.
Statistics
GitHub Stars 36.4K	GitHub Stars 4.2K
GitHub Forks 5.5K	GitHub Forks 214
Stacks 22.3K	Stacks 27
Followers 16.5K	Followers 86
Votes 501	Votes 18
Pros & Cons
Pros 123 Multi-container descriptor 110 Fast development environment setup 79 Easy linking of containers 68 Simple yaml configuration 60 Easy setup Cons 9 Tied to single machine 5 Still very volatile, changing syntax often	Pros 11 Vagrant-like 4 Written in golang 3 Hashicorp built
Integrations
Docker	Docker Consul Terraform Vagrant

What are some alternatives to Docker Compose, Otto?

Vagrant

Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.

Kubernetes

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Rancher

Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.

Docker Swarm

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.

Tutum

Tutum lets developers easily manage and run lightweight, portable, self-sufficient containers from any application. AWS-like control, Heroku-like ease. The same container that a developer builds and tests on a laptop can run at scale in Tutum.

Portainer

It is a universal container management tool. It works with Kubernetes, Docker, Docker Swarm and Azure ACI. It allows you to manage containers without needing to know platform-specific code.

boot2docker

boot2docker is a lightweight Linux distribution based on Tiny Core Linux made specifically to run Docker containers. It runs completely from RAM, weighs ~27MB and boots in ~5s (YMMV).

Codefresh

Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines.

CAST.AI

It is an AI-driven cloud optimization platform for Kubernetes. Instantly cut your cloud bill, prevent downtime, and 10X the power of DevOps.

libvirt

It is an open-source API, daemon and management tool for managing platform virtualization. It can be used to manage KVM, Xen, VMware ESXi, QEMU and other virtualization technologies.

Related Comparisons

"Multi-container descriptor" is the primary reason why developers consider Docker Compose over the competitors, whereas "Vagrant-like" was stated as the key factor in picking Otto.

Docker Compose vs Otto