DEV Community

Cover image for Microservices vs Monolithic Architecture: A Practical Approach

Microservices vs Monolithic Architecture: A Practical Approach

server side digest on January 02, 2023

πŸ“ Monolithic and Its issues πŸ™‚ When we start learning backend development and implementation, many of us implement all our functionalitie...
Collapse
 
ajimenezsa profile image
ajimenez

Thanks for sharing.
I would add a mention about the difficult introduced by microservices in the transaction management.
Think about an aborted paiment and the product stock control.
Surely this problem needs a complete blog entry to talk about it.

Collapse
 
ajimenezsa profile image
ajimenez

I'm not talking about a problem in my design. It is a problem in Microservices architectures.
It is covered for example in "Microservices Patterns" book, "Managing transactions with SAGAS". This is because I mentioned it, to add more information to your entry. 😜

Collapse
 
izio38 profile image
izio38

There are errors in this blog post, at a point that this is not serious.

Docker is not magically 'effective' because a team swaped to microservices.

This article promote microservices as if it was a magical response to the every day issues.

Note to readers: If your team is less than 20 tech people, and you are setting up a micro service architecture, then stop, micro services has many pros, so do monolithic.

Collapse
 
tamusjroyce profile image
tamusjroyce

I can’t wait until everyone stops using these terms. And instead learns hexagonal architecture vs n-tier vs workflow architecture vs plethora of architectures out there.

Only the Linux kernel 1.2 was large enough and not modular to be called a monolith. If you modularize, by definition not a monolith!

Rest endpoints + gateway is not an API! Unless your modules can use more than http. When that happens, even grpc or dynamic linking, no. No longer do have a microservice. You have an API.

There are some great points made. But please apply them beyond the two naive
terms.

Collapse
 
omars profile image
Omar Shaban • Edited

Microservices is a hype by big-tech to drive people towards managed/serverless services, or dive deep into a rather unneeded complexity on your own, in most cases you need SOA, clean design in general pays off big time, but this increases in complexity exponentially. Hopefully the world would understand one day what is a hype

Collapse
 
sweetestshuga profile image
Eze Sugar πŸ‘©β€πŸ’»

If we have databases for each service and one service handles users register and authentication, how does we duplicate this user information in all the database to give the permission across all services

Collapse
 
light_seekern profile image
Taha Syed

Good 😊

Collapse
 
fruntend profile image
fruntend

Π‘ongratulations πŸ₯³! Your article hit the top posts for the week - dev.to/fruntend/top-10-posts-for-f...
Keep it up πŸ‘

Collapse
 
jwp profile image
John Peters

Microservices are the end to traditional back-end architecture. Today it should be cloud-endpoints only.

 
ajimenezsa profile image
ajimenez

I'll review it. Thanks for the clarification. πŸ‘πŸΌ

Collapse
 
410nidhi profile image
Nidhi Upasani

Very Helpful. Thanks :)

Collapse
 
vaibhav68849256 profile image
Vaibhav Khandare

Impressive

Collapse
 
nikki_eke profile image
Nikki Eke

Wow. Thanks for sharing.

Collapse
 
rubenruvalcabac profile image
Ruben Ruvalcaba

Excellent concepts and overall explanation, can't wait to next articles on the serie

Can you consider scenarios for distributed transactions across services?

Regards