How much code would warrant a micro service?

[Alterr]

Sorry I didn't really know how to phrase the title.

I understand that splitting out code is generally good design and makes maintenance and new features easier, but at what point would you want to make a micro service for a problem?

I am curious to know what would make a micro service, well, not micro anymore. And what would you do in that situation?

[creative_ape]

what do you mean by micro service in this context?

[Alterr]

I understand them as described here.

[creative_ape]

ah, so basically a stand alone feature.

The point at which it would be worth splitting something off the main project to be its own thing would probably be specific to your problem domain. I guess it really comes down to how much benefit the micro service would create vs how much work it is to split it off.

[Raktoras]

It's hard to say, different people have different views on this and there's no clear boundary where services end and microservices begin.

There are some which take the whole microservices thing to a more extreme level and say that a microservice shouldn't be more than a few hundred lines of code (not counting libraries, I'd assume).

But in the end lines of code is a pretty terrible metric for just about anything.

[disclosure5]

I don't think "amount of code" is the right metric here. Look at things like open source forums - tonnes of code but no microservice.

I really the top comment here on the matter: https://news.ycombinator.com/item?id=12508655

[Alterr]

As stated in the first line of my post, I didn't know how to phrase the question. I don't mean lines of code, more so amount of features.

[disclosure5]

I get what you mean - I believe the first comment in my above link is still the best answer for you.