Engineering Decisions · Senior · Question 3 of 14
A six-person startup is still searching for product-market fit, and domain boundaries keep moving. What architecture do you start with?
- 1Serverless functions, one per API endpoint
- 2A modular monolith with clear internal boundaries
- 3Microservices from day one, one per domain
Show the answer
Correct answer: A modular monolith with clear internal boundaries
Explanation
A modular monolith keeps refactoring cheap while boundaries move, and clean modules can become services later. Microservices fit many teams that need independent releases, but six people would spend their time on network and deployment concerns. Per-endpoint functions fit spiky, isolated workloads, while spreading a changing domain across them makes shared logic hard to evolve.