3 ms·
It depends how you do micro services. There are middle grounds. One big gain of micro-services is that it guarantees things are separate and can be handled by s
by timothycrosley 9y ago
It depends how you do micro services. There are middle grounds. One big gain of micro-services is that it guarantees things are separate and can be handled by separate teams if the need arises. That doesn't mean you need to start out that way. For instance in Python I use hug to create my microservices https://github.com/timothycrosley/hug https://github.com/timothycrosley/hug, then I can just install them to create a "monolithic" services that consumes all the microservices, the great thing is that hug allows you to expose both as a webservices, and as a Python library so I can consume as a Python library with no overhead, until the need to split is evident, and then can split up the services with very little work. Of course the need may never arrive, but the modularity that is forced when using micro-services pays dividends quickly regardless
- mattmanser 9y agoI, my, I, I. Sounds like you really don't need microservices.
- StavrosK 9y agoAlso refer to the handy flowchart I created in my post (https://www.stavros.io/posts/microservices-cargo-cult/ https://www.stavros.io/posts/microservices-cargo-cult/) for judging whether you need microservices: https://www.stavros.io/files/images/microservices-cargo-cult/flowchart.png https://www.stavros.io/files/images/microservices-cargo-cult...
- timothycrosley 9y agoNo, I, don't because they are my own at home projects that haven't taken off, but I'm able to use the same library and code structure at work for things that absolutely do need microservice because of the power of the framework. And if any of my at home projects take off and I have huge teams and load then I may need microservices. It becomes a deployment question instead of a code question with the right framework.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]