4 ms·
One thing I’ve wanted my team to automate is on boarding new microservices. Being able to create a repo, generate the baseline configuration necessary and deplo
by duncan-donuts 8y ago
One thing I’ve wanted my team to automate is on boarding new microservices. Being able to create a repo, generate the baseline configuration necessary and deploy a container all within an action or two. The reason we haven’t is it seems like a lot of work for a process that doesn’t happen very often (once or twice a month)
- quickthrower2 8y agoA github repo with a docker file and appveyor.yml or similar, then fork it would be most of the job done. You might need to manually create a new appveyor project each time though.
- prabugp 8y agoWe wouldn't want it to be too easy to create a new microservice, would we? :) Kidding aside, the closest we got to was a template service with a hello world API which has all the basic configuration goodies in a repo. Anytime we need a new service, we fork it, and start working on it in a few minutes. Wouldn't that work?
- shoo 8y ago> We wouldn't want it to be too easy to create a new microservice, would we? :) i'll assume you're serious, so i agree. every time someone launches a new service, there's an ongoing burden to maintain that service in production. so maybe one heuristic would be to make the cost of launching a new service roughly comparable to the discounted cost of maintaining that service for its entire expected lifetime. then you could use the rule of thumb that if it costs you X to build it, it'll cost you a second X to maintain it, so you should only do it if you get > 2X value out of it. see also: http://classicprogrammerpaintings.com/post/131118350394/army-of-contractors-migrating-to-microservices http://classicprogrammerpaintings.com/post/131118350394/army...