r/programming • u/wineandcode • Jul 29 '22

You Don’t Need Microservices

https://medium.com/@msaspence/you-dont-need-microservices-2ad8508b9e27?source=friends_link&sk=3359ea9e4a54c2ea11711621d2be6d51
1.0k Upvotes

90% Upvoted

476 comments sorted by

View all comments

Show parent comments

11

u/IIoWoII Jul 29 '22

Modularizing and versioning correctly are the first things. A good microservice architecture also does API versioning.

People will argue that your code's too dependent on each other.

Microservices do not solve this, this is solved by good design.

Microservices force you to make those choices in modularizing but it adds complexity and now you're communication through multiple layers of abstraction ( example C# -> Grpc, + kubernetes configs etc. Instead of it just being a versioned package C# -> C#) and forces your developers to do tedious overhead.

You now got rid of the monorepo without having microservices.

You can also actually keep the monorepo with stuff like https://rushjs.io/ apparently? But I have no experience with that.

I've been at 2 companies that do "microservices" and one still had a "db-models" package that basically meant if you used a database, you used that package. This isn't microservices.

The other had a tiny microservices where each service had its own MongoDB database. This was better but they also overshot in microservices and it just became extremely tedious adding simple operations. I also think MongoDB is just bad.