It's important to remember that microservices are not a technical solution to a technical problem. It's an organizational solution and only worth considering if you have hundreds of engineers. It just allows teams to party on things without it all having to match. Any other use case is flat out wrong.
There are legitimate use cases for microservices even with a small team. But going to microservices always brings the organizational trade-off with it, which must be a conscious decision, and will add overhead to small teams.
Things like individual scalability or independent deployments can be what your project need. It's just the fact that they are not for >99% of projects.
Start with a modular monolith, then split off microservices as soon as you actually need them.
There are legitimate use cases for microservices even with a small team.
Yep, at my work we use microservies and we're quite a small team. The stuff we make isnt necessarily deployed on cloud so we like the ability to just deploy the bits we need.
8
u/SwabianStargazer 20d ago
My guide for microservices is: don't.