Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#1

Post by streeter » Tue, Jun 16, 2015, 11:09 PM UTC

Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
engineering.remind.com

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#2

Post by justinsb » Wed, Jun 17, 2015, 12:29 AM UTC

This looks great: simple yet powerful. I'm working a lot with Kubernetes, and you don't actually need to run an overlay network on AWS (or GCE). On AWS, there's some VPC magic that surprised me when I first saw it! But I believe that's beside the point; it's not about ECS vs Kubernetes, it is about what we can build on top.

In particular, I think the idea of embedding a Procfile in a Docker image is really clever; it neatly solves the problem of how to distribute the metadata about how to run an image.

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#3

Post by fosk » Wed, Jun 17, 2015, 1:02 AM UTC

This is neat. You might want to check out KONG (https://github.com/Mashape/kong) instead of putting a plain nginx in front of the containers/microservices. It is built on top of nginx too, but it provides all the extra functionality like rate-limiting and authentication via plugins.

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#4

Post by phantom_oracle » Wed, Jun 17, 2015, 1:08 AM UTC

http://www.openshift.org/

Just putting this out there in case anyone is looking for an alternate open-source PaaS.

I've never personally used it before (self-hosted), but it may be something that someone out there is looking for.

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#5

Post by sagivo » Wed, Jun 17, 2015, 1:13 AM UTC

personally i use dokku (https://github.com/progrium/dokku). i would be happy to see one standard "heroku-like" paass since i feel too many people trying to tackle the same problem.

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#6

Post by stephenr » Wed, Jun 17, 2015, 1:13 AM UTC

Does this really classify as "self hosted" if it's heavily dependent on AWS?

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#7

Post by floridaguy01 » Wed, Jun 17, 2015, 1:16 AM UTC

aws is silly expensive. Why didnt you build this on top of digitalocean? Digitalocean is so awesome right now. They dont even charge for bandwidth overages.

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#8

Post by jordanthoms » Wed, Jun 17, 2015, 1:22 AM UTC

How do you handle running one-off tasks (consoles, migrations etc) on this setup? This is something most of these systems seem to ignore...

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#9

Post by steinnes » Wed, Jun 17, 2015, 1:29 AM UTC

fosk wrote: post #3

This is neat. You might want to check out KONG ( https://github.com/Mashape/kong ) instead of putting a plain nginx in front of the containers/microservices. It is built on top of nginx too, but it provides all the extra functionality like rate-limiting and authentication via plugins.

Good thought, I even think the article mentions kong as a future replacement for nginx :-)

Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS

#10

Post by dstroot » Wed, Jun 17, 2015, 1:34 AM UTC

sagivo wrote: post #5

personally i use dokku ( https://github.com/progrium/dokku ). i would be happy to see one standard "heroku-like" paass since i feel too many people trying to tackle the same problem.

And there is dokku-alt. https://github.com/dokku-alt/dokku-alt