workOwonworkOwonA New Way to Connect
HomeFeedJobsCommunitiesEventsFeaturesAbout workOwon
HomeFeedJobsCommunitiesEventsFeaturesAbout workOwon
HomeCommunitiesJava & Spring Developers India

Reviewed three architectures this month where a 6-person team runs 12 services. Every one of them had:

RM

Rohan Malhotra

Staff Engineer @ Orbitly | Distributed systems, Go, Postgres | Writing about architecture tradeoffs

3 Oct 2026· Java & Spring Developers India

Reviewed three architectures this month where a 6-person team runs 12 services. Every one of them had: • distributed transactions they didn't know they had • a shared DB anyway • a deploy pipeline more complex than the product A well-structured modular monolith (Spring Modulith is great for this) gets you 90% of the benefit. Split a service out when you have a real reason: different scaling, different team, different release cadence. Change my mind.
8 reactions3 comments

Comments

  • AS

    Aarav Sharma3 Oct 2026

    Agree mostly. We split payouts out because it needed different on-call and compliance boundaries. That was a real reason. The other 4 splits... not so much.

  • KS

    Kabir Singh3 Oct 2026

    As someone who joined a 'microservices' startup with 3 devs, I feel this in my bones.

  • RA

    Riya Agarwal4 Oct 2026

    The org chart argument is underrated. If one team owns everything, one deployable is usually right.

Join the conversation

Join workOwon to react, comment and follow people and communities you care about.

Log inJoin now

Popular communities

See all