You review a design that uses 25 microservices for an MVP with one team. What feedback do you give?

Short answer

Recommend a modular monolith with clear module boundaries aligned to the domain, explaining the costs of distribution (operations, consistency, latency, testing) for a single team, and agree on the triggers that would justify extracting services later. Frame feedback around goals and evidence, not preference.

Detailed answer

Ask about goals (time to market, scale, team growth). For one team, 25 services means 25 pipelines, distributed transactions, network failure handling and harder debugging, with no autonomy benefit. Propose: modular monolith with enforced boundaries (Spring Modulith/ArchUnit), separate schemas per module, async events internally, and an ADR with extraction triggers (new team ownership, distinct scaling needs). Offer help with the module design.

What the interviewer expects

Constructive, principled feedback and coaching mindset.

Common mistakes to avoid

Blocking the team without an alternative or dismissing their concerns about future scale.