A 6-person startup with one product debates microservices. The strongest argument against starting with them?
Options
- Microservices cannot scale beyond a few nodes
- Operational overhead: network failures, deploys (Correct option)
- They require Java as the only possible language
- They are not cloud-native by their very design
Answer
Operational overhead: distributed debugging, network failures, deployments, data consistency across services
Why
Microservices split an app into many small services that talk over the network. That brings real costs: many deployments and pipelines, network errors and timeouts, debugging across services, and keeping data consistent without one shared transaction.
A small team usually moves faster with a well-organized monolith (one app with clear internal modules), and extracts services later when scale or team size justifies it.
Remember
Start with a modular monolith; split when there is a real reason.