News for hackers. Stuff that matters.
Re:Microservices – Not a free lunch by ryanbrunner on Sunday December 28, 2014 @06:02AM (#8805994)
Cloud66 can handle most of what you describe using manifest files. You can have a relatively simple yml file describing what types of servers exist in your stack - something like "I need Postgres servers, Redis, a RabbitMQ server, oh and here's the 3 different types of process servers I have and also how my main web server functions."

There's still a point where it's beneficial to split an application into seperate stacks, in which case the manifest concept breaks down and you're stuck doing a lot of work yourself, but they can take you a fairly long way.

Re:Microservices – Not a free lunch by olalonde on Sunday December 28, 2014 @06:55AM (#8806079)
> There's still a point where it's beneficial to split an application into seperate stacks

Do you mean like having a different "infrastructure manifest" for each micro-service? In that case, couldn't each micro-service specify which other micro-service it depends upon? For example, I could have a central "API gateway" service which would specify all the other micro-services it depends upon. This reminds me a bit of a Gemfile/Package.json but for processes instead of libraries. On the other hand, I can easily see how this could turn into a dependency hell.