Microservices Architecture Design
Plan a scalable microservices architecture with communication patterns and service boundaries.
Prompt template
Design a microservices architecture for [PROJECT DESCRIPTION]. **Requirements:** - Current architecture: [Monolith/already partially split] - Expected load: [REQUESTS PER SECOND] - Team structure: [NUMBER OF TEAMS] - Technology preference: [TECH STACK] **Please create:** 1. **Service Decomposition:** Identify bounded contexts and define services 2. **Service Communication:** Synchronous (REST/gRPC) vs. Asynchronous (Events/Messages) — with reasoning for each service 3. **Data Strategy:** Database-per-service, Saga pattern for distributed transactions 4. **API Gateway:** Routing, rate limiting, authentication 5. **Service Discovery:** How do services find each other? 6. **Resilience:** Circuit breaker, retry, fallback strategies 7. **Observability:** Distributed tracing, centralized logs, metrics 8. **Deployment:** Container orchestration, CI/CD per service **Diagrams:** - Architecture overview as text diagram - Sequence diagrams for critical flows - Data flow diagram
Replace placeholders in [square brackets]: [PROJECT DESCRIPTION][Monolith/already partially split][REQUESTS PER SECOND][NUMBER OF TEAMS][TECH STACK]
How to use this template
Copy the prompt, replace the placeholders in square brackets with your details and paste it into the AI assistant of your choice. The more precise your details, the better the result.
Tips for better results
- Start with the bounded contexts of your domain
- Specify expected load and scaling requirements
- Ask for a migration strategy from monolith
- Request cost estimation for the infrastructure
Suitable open models
The selection names current open models as a starting point for your own tests. It is not a measurement for this template.
Keywords: #microservices #architecture #distributed-systems #scalability