|
Pretty much the same as Heroku. As a developer, I want to deploy my application as quickly as possible without setting up nginx, gunicorn, etc. per service. I have a front-end service, three API services, and some daemon services. I'd like to be able to scale eventually. With Deis, you first allocate the number of machines you want to be your cluster and install Deis on them. Think of the cluster as a large physical machine that can run many services. You might have a production cluster (7 machines), dev (3 machines), staging (3 machines), etc. Now, deploy your apps to that cluster via a git push for each. Need to boot a new front-end server to handle load? Just run an extra container in your cluster. Same with API. How would you do that with your current setup? I'm guessing provision an entire second machine (or VM, same thing) and put them behind a load balancer. With Deis, each cluster is exposed behind a single load balancer and each app/service is exposed as a subdomain on that loadbalancer. Deis handles the internal load balancing. Cluster getting full? Just add a new machine/vm to it. So, if you like the idea of Heroku, you might like Deis, especially if you'd like to use your own hardware/VPC or want to use Docker locally and in production. |