Microservices is a software architecture where an application is built as a set of small services, each owning one business capability, running independently and communicating over the network, usually through HTTP APIs or messages.
Why it matters
Teams can deploy, scale and fix one service without releasing everything. A busy checkout service can scale separately from a rarely used admin service, and failures can be contained.
The price is distributed-system complexity: network failures, versioned APIs, tracing across services and harder local testing. Many teams do better starting with a well-structured monolith.
Example
An online shop has separate services for catalog, cart, payments and email. If the email service is slow, the cart can queue messages and continue, while a monolith might block the whole request.
Common mistakes
- Splitting too early, before the domain boundaries are understood.
- Sharing one database between services, which couples them again.
- Skipping monitoring and tracing, so no one can tell which service caused an outage.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.