Instead of nginx, we've had a pretty good experience using vulcand ( https://github.com/mailgun/vulcand ) as the front-end router for our micro-services.
Any reason(s) for switching to Vulcand rather than NginX ?
Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
51–60 of 80 posts
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#52Earlier quoted context omitted.
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.
I can identify with that, we built a custom nginx based load balancing / routing solution at QuizUp while I was there :-)
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#53Earlier quoted context omitted.
DO's "most popular plan" is $10/mo [1] AWS's t2.micro in us-east is ~$10.30/mo with a standard 8GB disk [2] Both VMs are single core, 1GB RAM. DO gives you 30GB SSD, but AWS has a freely adjustable disk size. Upscaling from 8 to 30GB is another $2 - but how many single-core low ram instances use double-digit GB? In the middle, DO has 8 core, 16GB for $160/mo, AWS has 4 core 16GB for 185/mo + storage. At the top end o…
You seem to make the implicit assumption that a DO $10 VPS is equal in performance to a AWS t2.micro instance, which is not the case. For an example, check out: http://serverbear.com/compare?Sort=Host&Order=asc&Server+Typ... DO 1GB instance at $10/month has a UnixBench of 1041 [1], to beat that with AWS you have to spend $374/month. Also, with the t2.micro you get an EBS disk, whose I/O you have to pay in addition to…
You seem to be ignoring my two other data points. Similarly, bandwidth costs are small, unless you're really pumping out a lot of data. I don't even notice our EBS transfer costs on our bill.
And how reliable a measure is UnixBench, when the top-performing server "CC2 Large" (by a factor of 25% over second place!) is a 2-core, 8GB RAM offering? It easily beats out all the two-dozen core, high-ram offerings below it.
Hell, the names of the AWS instances in that list aren't even correct. What's a "high-cpu medium"? They mean a "c1.medium" from looking at the stats page, which is now two generations obsolete - you have to know about them and go out of your way to provision one. The one name they do list, "m3.medium", is incorrectly labelled a "high i/o" VM; AWS doesn't have a "high i/o" VM, and the m3.medium is not considered by them to be network-, ram-, or storage-optimised, so I'm not sure where that's coming from. And if you do need disk i/o with AWS, you can provision reserved i/o (not very expensive), which needs to be accounted for in these comparisons. It's just getting my goat at the moment, because my comment was trying to argue against FUD, but that reference list can't even get well-known and advertised names correct.
AWS billing is complex, absolutely, but there is also a ton of flexibility, and it makes sense once you pass the learning curve. And micros do get throttled, but they also get a certain number of "throttle credits" that help them survive bursts. And yes, I agree that you should choose the right tool for the right job - one HNer really uses that huge amount of free bandwidth you get with the small DO servers with a media streaming service (I forget the handle). But that still doesn't change the fact that AWS is no longer "OMG expensive!" over DO.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#54How to autoscale with this?
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#55Earlier quoted context omitted.
http://www.openshift.org/ or http://cloudfoundry.org/index.html , both used in production by f500 companies
Cloud Foundry requires a ton of (compute) overhead to get set up. It's very much intended for large projects. Hell, you need a separate VM just to install it. For anyone looking at a Dokku alternative, Cloud Foundry isn't one. Openshift is nice though.
You should check out lattice:
http://blog.pivotal.io/pivotal-cloud-foundry/products/lattic...
it aims to address some of your concerns around starting small with cloud foundry
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#56Instead of nginx, we've had a pretty good experience using vulcand ( https://github.com/mailgun/vulcand ) as the front-end router for our micro-services.
Any reason(s) for switching to Vulcand rather than NginX ?
First off, nginx is awesome and you can do all the things we did with vulcand with nginx, so it was just a question of friction.
The reason we went with vulcand is that it natively supports what we wanted to do i.e. route to micro-services based on dynamic etcd driven configuration. To do the same thing in nginx (at the time), we would have either had to use confd or custom lua.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#57> We tried Deis briefly but ultimately decided that it was more complicated than we felt it needed to be.
That kind of reminds me of https://xkcd.com/927/
Sorry if that's not the case. I've also played briefly with Flynn and Deis and I haven't found anything that complicated that would need a whole rewrite and changing the entire approach. Moreover with Deis I can easily change providers (DO, AWS, Azure, etc.) and with Emprire I'm bound to ECS. At least that was my first impression, I have to read more.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#58Earlier quoted context omitted.
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 become…
Not exactly sure what you mean by its meant for just 1 service? Do you mean just one box? I run multiple services/apps on my dokku instance
If your app is 12-factor, why can't you just spin up more instances of your app on Dokku?
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#59I'm interested in hearing more about how you use this in terms of development lifecycle. Does a container image get created for every release of your app? I've always wondered about the more correct approach to this.
This is how I currently use Docker:
1) Custom base image with all the things my company needs like supervisord, libpq, etc..
2) Custom per-service base images like ones with Java for our Clojure services or Python for our research services which are built off of the base.
3) A release consists of pulling the latest version of the base image, example, acme-python, and then injecting the latest project code into it.
My concern here essentially boils down to the image repo. Github needs to add container storage because while I admire Docker Hub's efforts, I don't trust it.
Re: Introducing Empire: A Self-Hosted PaaS Built on Docker and Amazon ECS
#60personally 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
That project is not really maintained anymore, and it is nothing more then dokku with a bunch of plugins preinstalled. I would suggest just using dokku and installing the plugins you need. Dokku has moved forward in their API and stuff a lot since dokku-alt was forked and the documentation for dokku does not really apply to dokku-alt.