Microservices is a great architectural style that helps to scale the system and the organization. But probably you don’t need microservices...

Master Yoda

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Microservices offer benefits like scalability and independent team operations, but also bring added complexity and costs. The post discusses real-world examples where companies faced challenges like high maintenance overhead, performance issues, and complexity in managing numerous services. Before adopting microservices, consider if they are the right fit for your organization, as sometimes simpler architectures like monoliths may be more effective.

You probably don’t need microservices

modules within one monolith &gt;&gt; microservices

Well, I need write a large post to answer this. but i’m lazy. jajaja some details.
To use Microservice in your Architecture, you need know the true concept service. The services must be represent independent business concepts, otherwise you are develop modules connected throuth http or kafka . Service Calling to other Service is an anti-pattern. using differents service have to implicited deacopledment mechanism, like kafka or MQ.
If your business don’t support eventual integrity, microservices is bad idea. you are running into the distributed transaction jungle.
Microservices Always have implicit data redundancy, that’s why, more cost. The Scalability Needs have to paid the over Architecture’s cost

Just use whatever works, dunno why people/companies make such a big deal about this, then come up with a 3d graph that makes absolutely no sense.