Deis vs tsuru: What are the differences?
Developers describe Deis as "Open Source PaaS that builds upon Docker and CoreOS to provide a lightweight PaaS with a Heroku-inspired workflow". Deis can deploy any application or service that can run inside a Docker container. In order to be scaled horizontally, applications must follow Heroku's 12-factor methodology and store state in external backing services. On the other hand, tsuru is detailed as "Extensible and open source Platform as a Service software". tsuru is an open source polyglot cloud application platform (PaaS). With tsuru, you don’t need to think about servers at all. You can write apps in the programming language of your choice, back it with add-on resources such as SQL and NoSQL databases, memcached, redis, and many others. You manage your app using the tsuru command-line tool and you deploy code using the Git revision control system, all running on the tsuru infrastructure.
Deis and tsuru can be primarily classified as "Platform as a Service" tools.
Some of the features offered by Deis are:
- Deis can deploy any language or framework using a Dockerfile
- If you don't have a Dockerfile, Deis includes Heroku buildpacks for Ruby, Python, Node.js, Java, Clojure, Scala, Play, PHP, Perl, Dart and Go.
- Deis can be deployed on any system that supports CoreOS including your workstation, as well as most public clouds, private clouds and bare metal.
On the other hand, tsuru provides the following key features:
- Fast and secure. The entire process is really simple with no special tools needed, just a simple git push.
- Scaling in Tsuru is completely painless. Just add a unit and Tsuru will take care of everything else.
- Tsuru is built to be extensible. Through services you can provide anything your application needs.
"12-factor methodology" is the top reason why over 15 developers like Deis, while over 4 developers mention "Very receptive to contributions" as the leading cause for choosing tsuru.
Deis and tsuru are both open source tools. Deis with 6.12K GitHub stars and 861 forks on GitHub appears to be more popular than tsuru with 3.13K GitHub stars and 421 GitHub forks.
What is Deis?
What is tsuru?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Deis?
What are the cons of using tsuru?
Sign up to get full access to all the companiesMake informed product decisions
Tsuru allows developers the necessary and dreamed autonomy, maintaining the infrastructure department confident and is very business oriented as it improves the time to market with safety. Where is the magic?! It is not just starting to treat people as adults(that is mandatory), you also need a system that automatically recover itself(self-healing) after any mistake, misconfiguration, infrastructure problem, etc and (auto)scale easily as needed. We have it for about 4 years at Globo.com using Tsuru PaaS, one of the most loved projects we maintain, totally opensource, powered by Docker, no vendor lock-in, no comercial version(what we use is what we provide) and very receptive to new contributions, discussions, and fix of serious issues(stop the line mindset). Tsuru manages applications with millions of users with no headaches. The main value is that tsuru allowed a new and desired culture, finally developer can have the freedow they want to deploy(the freedom comes with responsability) - thousands of deploys/month and increasing - with increased stability/availability of ours portals We can finally rest calmally at night and in the weekends, letting tsuru dealing automatically with any operational problem may happen. Try it in your company, you too deserve to be happy! https://tsuru.io https://github.com/tsuru/tsuru