Orbit · Explore

Programming · by Khalid Al Zahrani · 2026-10-15

Monolith vs microservices in 2026: what would you pick for a 5 person team?

Every few months the debate returns. For a small team shipping fast, what's your default and why?

50 sparks · 13 comments

Comments

Élodie Favre · 14 likes

I just want one repo and one deploy button, is that so much to ask

Lucas Dubois · 3 likes

Not at all, that's the dream.

Maksym Bondar · 10 likes

Modular monolith. Always. You can split later when it hurts.

Irene López · 6 likes

Splitting later is harder than people say but still cheaper than ops overhead.

Hugo Martin · 9 likes

5 people running 12 services is a staffing problem disguised as architecture.

Isha Menon · 6 likes

Ouch, but true.

Grace Parker · 8 likes

We went micro too early and spent a year on Kubernetes yaml.

Noah Miller · 0 likes

yaml engineer is not a career goal

Mina Chowdhury · 7 likes

Depends on deploy needs. If one part scales 100x differently, extract only that.

Arif Hasan · 0 likes

This. Extract by pain, not by principle.

Minji Kim · 2 likes

Team topology matters more than team size honestly.

Mara Fischer · 0 likes

Monolith plus a queue and a worker covers like 90% of cases.

Valeria López · 10 likes

Add Postgres and you're basically done.