Suggest an editImprove this articleRefine the answer for “What is a "bounded context" in microservices architecture?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Bounded context** is a principle from **Domain-Driven Design (DDD)** that, in microservices architecture, defines **the boundaries of each service's responsibility**. **Key point:** a bounded context is a clear boundary around a microservice's business meaning: inside are its own rules and data model, outside there is interaction only through a public API.Shown above the full answer for quick recall.Answer (EN)Image**Bounded context** is a principle from **Domain-Driven Design (DDD)** that, in microservices architecture, defines **the boundaries of each service's responsibility**. --- ### The meaning Each microservice exists **in its own context**: it has its own business area, terminology, logic, and data. It does not share a database or models with others and does not interfere with their internal rules. *Example:* - The **orders** service works with concepts like "product", "status", "payment". - The **delivery** service uses "address", "courier", "tracking number". Both talk about orders, but each in its own context, and neither is required to understand the other's internal structures. --- ### Why this is needed - It removes overlapping logic and dependencies between services. - It lets different teams develop their parts independently. - It makes the system scalable and flexible: each service lives in its own domain "zone". --- **Summary:** > A **bounded context** is a clear boundary around a microservice's business meaning: > inside are its own rules and data model, > outside there is interaction only through a public API.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.