DEV Community

Discussion on: How big or small should microservices be?

Collapse
 
imthedeveloper profile image
ImTheDeveloper

I've found most examples given on the internet tend to go even more micro than I had been initially thinking when researching the topic. Meaning.. there is "micro" in my mind and then I read an article and realise what they have built is seemingly "nano" to me.

Overtime and through working on breaking down a monolith first hand I generally found pulling apart the general features into containers first helped. Then maybe abstracting chunks of common usage into services. It was hard to pick out even with a monolith right there the general services.

Sure payments, authentication etc sound generic enough but I actually found there were much lower hanging fruit to go for first. Key indicators were areas which continually needing updating and full deployments felt heavy. Other areas of complex or high risk code that had become hard to debug also soon found themselves split out.

Are these "services"? Unsure. But I've definitely felt the benefits and now I can refactor again with much greater ease.