I've been following PaaSs built on docker for a while, and it seems like the new swarm mode in version 1.12 makes them pretty much obsolete. I was a huge fan of deis (deis.io), but it seems like they are pivoting away from docker to do something different (deis.com). At this point, think docker has become big enough such that building a platform on top of it is pretty much redundant, but something like this may prove useful for more modular container systems such as rkt.
My brief skim over the Swarm announcement was that, while it focuses on the orchestration problem, it's not a fully-fledged PaaS. It's somewhere closer to where Kubernetes is working.
Essentially, you turn on a swarm and then ... oh, I still need routing. And service injection. And I need something to build the app. Something to hold the images. I guess I need standard debugging interfaces. Standard performance measurement. And ... and ... and ...
PaaSes require a lot of engineering.
Disclosure: I work for Pivotal on the fringes of one such PaaS, Cloud Foundry.
Deis isn't pivoting away from Docker and has always required additional pieces of infrastructures that are not strictly Docker (Kubernetes in v2 and CoreOS in v1). I haven't tried Swarm but I'd be surprised if it came close to Kubernetes in terms of stability and community support given the latter had a good head start and is backed by Google which uses it in production.
This project has not been updated since February. Cursory searches are not showing more active forks. It might be interesting to look at the code for educational purposes, but I wouldn't recommend building on this.
There's quite a few options in this area. I've recently started using dokku for personal projects. My current plan is to migrate to deis in future if/when I want multiple nodes.
Cloud Foundry predates pretty much everything else. It was decided in the early days to support the full buildpack lifecycle as defined by Heroku, to the point that a lot of Heroku buildpacks run on Cloud Foundry with no or minimal changes.
Disclosure: I work on buildpacks for Pivotal, the majority donor of engineering to Cloud Foundry.
Really pleased to see that they've open-sourced this work! I interviewed at Ooyala back in 2013 when they were just getting started on this project so it's quite satisfying to see how far they've taken this project!
This looks cool. I'm using dokku to do that and I'm very satisfied with it, but I would like something closer to core docker experience, which would make it easier to integrate with other tools/process (like swarm, which not to have on dokku is a big problem).
This is where I want to see docker go, being able to handle zero downtime deployment without pain, good luck!
Unfortunately, none of those services or projects existed when we first started building Atlantis at Ooyala. I haven't been at Ooyala for a while now, so not sure what their plans are for this project now that open source tooling with wider support exists.
[+] [-] johnhenry|9 years ago|reply
[+] [-] jacques_chester|9 years ago|reply
Essentially, you turn on a swarm and then ... oh, I still need routing. And service injection. And I need something to build the app. Something to hold the images. I guess I need standard debugging interfaces. Standard performance measurement. And ... and ... and ...
PaaSes require a lot of engineering.
Disclosure: I work for Pivotal on the fringes of one such PaaS, Cloud Foundry.
[+] [-] olalonde|9 years ago|reply
[+] [-] dnsco|9 years ago|reply
[+] [-] ryanbertrand|9 years ago|reply
[+] [-] FabioFleitas|9 years ago|reply
[+] [-] grogs|9 years ago|reply
There's quite a few options in this area. I've recently started using dokku for personal projects. My current plan is to migrate to deis in future if/when I want multiple nodes.
[+] [-] seibelj|9 years ago|reply
[+] [-] sandGorgon|9 years ago|reply
one question - there have been a few open source PAAS out there for a while. But no real competitor to Heroku till now. What's missing ?
[+] [-] yannski|9 years ago|reply
Disclaimer: I'm a co-founder
[+] [-] jacques_chester|9 years ago|reply
Cloud Foundry predates pretty much everything else. It was decided in the early days to support the full buildpack lifecycle as defined by Heroku, to the point that a lot of Heroku buildpacks run on Cloud Foundry with no or minimal changes.
Disclosure: I work on buildpacks for Pivotal, the majority donor of engineering to Cloud Foundry.
[+] [-] jaytaylor|9 years ago|reply
[+] [-] oelmekki|9 years ago|reply
This is where I want to see docker go, being able to handle zero downtime deployment without pain, good luck!
[+] [-] dstroot|9 years ago|reply
[+] [-] irabinovitch1|9 years ago|reply
[+] [-] yeukhon|9 years ago|reply
AWS is IaaS. AWS does offer some 'PaaS' experience through the offerin go ElasticBeanstalk and ECS. But neither came close to a true PaaS.
[+] [-] bognition|9 years ago|reply
(Also I work at HubSpot where Singularity was developed)
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] qboxio|9 years ago|reply
[+] [-] fapjacks|9 years ago|reply
[+] [-] blakeyrat|9 years ago|reply
And yes, I looked at the link. It uses "PaaS" without defining it.
[+] [-] rfrey|9 years ago|reply