Suggest an editImprove this articleRefine the answer for “How do microservices differ from a monolith?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)A **monolith** is an application where all the code (logic, interface, database) is combined into one common block. **Microservices** are a set of separate modules, each of which is a self-contained service with its own logic and database. **Key point:** a monolith is simpler at the start but harder to scale; microservices are more complex in infrastructure but provide flexibility, independence, and resilience to failures.Shown above the full answer for quick recall.Answer (EN)ImageA **monolith** is an application where all the code (logic, interface, database) is combined into one common block. **Microservices** are a set of separate modules, each of which is a self-contained service with its own logic and database. --- ### The main difference | Characteristic | Monolith | Microservices | |---|---|---| | **Structure** | Everything in one application | Split into independent services | | **Development** | One codebase, one team | Many teams, each responsible for its own service | | **Deployment** | Everything is updated at once | A single service is updated | | **Scaling** | Only the whole application | Selective - only the needed services | | **Dependencies** | Strong coupling | Loose, through APIs | | **Data storage** | Shared database | A separate database for each service | --- ### Example Monolith: an online store where one server handles orders, payments, and delivery. Microservices: orders, payments, and delivery are three separate services that communicate through APIs. --- **Summary:** A monolith is simpler at the start but harder to scale. Microservices are more complex in infrastructure but provide flexibility, independence, and resilience to failures.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.