Agent RulesAgent Rules
MI

Microservices

Distributed service architecture patterns

Universal
Architecture
api
Use in BuilderAll Universal Options

Details

Language / Topic
_UUniversal
Category
Architecture

Rules

balanced
- Each microservice owns its database — never share databases between services. Communicate via APIs, events, or message queues.
- Design services around business domains, not technical layers — a service should represent a bounded context with clear boundaries.
- Implement circuit breakers for inter-service calls — prevent cascading failures when a downstream service is slow or unavailable.
- Use API contracts (OpenAPI, protobuf) between services. Version contracts explicitly.
- Implement circuit breakers and retries for inter-service communication.
- Design for eventual consistency — avoid distributed transactions when possible.