Architecture · English usage comparison
Microservice vs Monolith: English Usage Guide for IT Professionals
A monolith is a single deployable application; microservices split that application into independent services. Monoliths are simpler to start with; microservices provide team independence and targeted scaling at the cost of distributed-systems complexity.
Side-by-side comparison
| Aspect | Microservice | Monolith |
|---|---|---|
| Deployment unit | Many small independent services | One large application |
| Team structure | Each team owns a service | All teams share the codebase |
| Scaling | Scale each service independently | Scale the whole application |
| Complexity | High (distributed systems) | Lower (single process) |
Example sentences
Microservice
- "We split the payments logic into its own microservice — the team deploys it independently without touching other services."
- "Each microservice has its own database, so schema changes in one service don't affect others."
Monolith
- "Our monolith has served us well for three years, but now all 20 developers contend for the same release cycle."
- "Starting with a monolith is fine — split into microservices only when the pain is real."
Exercises: choose the correct English usage
Select the best answer for each question, then check your reasoning.
1. "All features are in one deployable app." This describes a ___.
Explanation: A monolith is a single deployable unit containing all features.
2. Team A can deploy the payment service without coordinating with Team B (user service). This is a benefit of ___.
Explanation: Deployment independence is a core microservices benefit.
3. Which architecture has lower operational complexity at the start?
Explanation: Monoliths are one process — no network calls between services, no distributed tracing required.
4. "The ___ is hard to scale because we can only scale all of it at once." Which word fits?
Explanation: Monoliths must be scaled as a whole, even if only one component is the bottleneck.
5. What is a "distributed monolith"?
Explanation: A distributed monolith has the complexity of microservices but the tight coupling of a monolith — the worst of both worlds.
Frequently asked questions
Should I start with microservices or a monolith?
Start with a monolith. The complexity cost of microservices is only worth paying when you have the team size and operational maturity to manage it. Martin Fowler calls this "MonolithFirst".
What is "service mesh"?
Infrastructure that handles service-to-service communication in microservices — load balancing, mTLS, retries, and observability (e.g. Istio, Linkerd).
What is the "strangler fig" migration?
Gradually replacing a monolith by building new microservices alongside it, routing traffic incrementally, until the monolith can be retired.
What is "domain-driven design" (DDD)?
A software design approach that structures code around business domains. Microservice boundaries often align with DDD "bounded contexts".
What is "eventual consistency"?
In distributed microservices, data across services may be temporarily out of sync. Eventual consistency means all nodes will converge to the same state — eventually.
What is a "saga" in microservices?
A pattern for managing distributed transactions across multiple services using a sequence of local transactions with compensating actions on failure.
What does "independently deployable" mean?
Each microservice can be deployed to production without requiring simultaneous deployment of other services.
What is "service discovery"?
The mechanism by which microservices find each other's network addresses at runtime, since they may move between containers or scale dynamically.
What is a "sidecar"?
A container deployed alongside the main service container, providing shared functions like logging, config, or a service mesh proxy (e.g. Envoy).
What does "tight coupling" mean?
When one service depends heavily on another's internal details — changes in one break the other. Microservices should be "loosely coupled, highly cohesive".