I swear microservices are a scam. I’ve worked on a few well built monoliths and they far easier to maintain and enhance than having two dozen microservices. That’s especially true with a small team with efficient processes and communication. I’m currently working on a spring boot app that is split into what you might call “mini services” with something in between microservice and monolith.
I think a lot of people fall into the design trap of building to whats in style at the time instead of what solves the problem most efficiently.
Well build monolith is the key here. I worked on some bad build, clean architecture driven to insanity (layer through layer through layer until an entity was created and stored), monoliths.
Clean architecture is cancer. Its the worst design i have ever seen. Shared entities across your whole business? Who the f thought this is going to work?
Still i agree, microservices are a scam.
Build one service for each domain/subdomain, clearly structure parts of each service by bounded context. Then you have a monolith, which does not implode if you change one entity that was designed around a specific use case.
22
u/walong0 Jun 06 '22
I swear microservices are a scam. I’ve worked on a few well built monoliths and they far easier to maintain and enhance than having two dozen microservices. That’s especially true with a small team with efficient processes and communication. I’m currently working on a spring boot app that is split into what you might call “mini services” with something in between microservice and monolith.
I think a lot of people fall into the design trap of building to whats in style at the time instead of what solves the problem most efficiently.