3 ms·
rancher is a bit different. It's based on lower-level APIs which allow your containers to hook into a certain cloud-provider features like Amazon's EBS, ELBs an
by bacongobbler 12y ago
rancher is a bit different. It's based on lower-level APIs which allow your containers to hook into a certain cloud-provider features like Amazon's EBS, ELBs and VPCs. Deis uses the docker engine to ship and run applications, providing an easy developer workflow. We're similar to other PaaS solutions like Dokku[1], Flynn[2], and Cloud Foundry[3].
[1]: https://github.com/progrium/dokku https://github.com/progrium/dokku
[2]: https://flynn.io/ https://flynn.io/
[3]: http://cloudfoundry.org/ http://cloudfoundry.org/
- sciurus 12y agoI think you misunderstood my question. I know that Deis is focused on running 12-factor apps and does not try to provide a platform on which to implement backing services. There are proprietary implementations of backing services that are tied into specific cloud providers, such as Amazon's RDS. There are open-source implementations of backing services that are tied into specific cloud implementations, such as OpenShift's Trove. What I am asking is this: what projects are attempting to implement open-source backing services in a cloud-agnostic manner? Put another way, if I choose to run Deis right now, I have the benefits of a PaaS without lock-in. However, I still have to either accept a degree of lockin to a service like RDS or attempt to roll my own automated database management. What projects should I be watching or contributing to that are trying to change this for databases? For queues? Etc. I mentioned Rancher because they included creating clones of EBS and RDS in their goals, but surely they're not the only project biting this off.