Thank you, this looks awesome! As someone who still hasn't embraced docker due to all the orchestration / discovery madness I really appreciate such an elegant solution. I love and run everything on AWS so building on top of ECS is just another selling point.
Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
11–20 of 80 posts
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#12personally 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.
http://www.openshift.org/ or http://cloudfoundry.org/index.html, both used in production by f500 companies
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#13This 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 :-)
Yep! We're definitely looking into Kong in the future. For now nginx + some static configuration works amazingly well for us. Very maintainable and minimizes external dependencies.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#14aws 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.
Haha, except AWS doesn't lock your account randomly or stop droplets for benign abuse reports.
Also, OP required Redshift. DO does not offer that.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#15personally 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.
Dokku is definitely an awesome project (pretty much anything from Jeff Lindsay is pretty good)! The primary problem is that dokku is meant for just 1 service and we have quite a few.
We'd love to see one standard too. Personally, I think it's good to have a lot of competing solutions right now (ECS vs Kubernetes, Docker vs Rocket, etc) and we'll see things settle in the next couple of years as containerization becomes more common.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#16How do you handle running one-off tasks (consoles, migrations etc) on this setup? This is something most of these systems seem to ignore...
We actually have a relay (https://github.com/remind101/empire/tree/master/relay) service that can be run alongside Empire that acts as a proxy to interactive Docker sessions. It's a bit of an experiment right now and something we'd like to solve better in the future, but it allows you to run containers with `emp run -a `.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#17Does this really classify as "self hosted" if it's heavily dependent on AWS?
It runs inside networks you control at least at the configuration level, so I would say so.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#18This 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.
KONG definitely looks interesting, and I'd love to know more about it. However, there's definitely not a lot written about it yet.
For example: I've gone searching through the blog posts, github readme, and KONG documentation, but I still have no idea _why_ it needs Cassandra. What does it store in there?
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#19Does this really classify as "self hosted" if it's heavily dependent on AWS?
I don't think so. It's their hardware, infrastructure, and engineers hosting it. They control those things. You get the rest. Sounds like an AWS-hosted solution with some advertised advantages over other solutions. Definitely not self-hosted.
Note: I think the only 3rd party thing I'd call self-hosted is colocation where I delivered the server, they plugged it in, and the most they do is reboot it for me.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#20This 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.
KONG definitely looks interesting, and I'd love to know more about it. However, there's definitely not a lot written about it yet. For example: I've gone searching through the blog posts, github readme, and KONG documentation, but I still have no idea _why_ it needs Cassandra. What does it store in there?
Kong uses Cassandra for storing config. This makes it easy to run a Kong cluster. Just add more instances that share the same Cassandra cluster.