Microservices Architecture
Generates a complete microservices architecture plan including service boundaries, communication patterns, data management, infrastructure, and observability strategies.
When to use this prompt
Use this when you need to design a microservices system from scratch or plan a migration from a monolithic application. It's appropriate when you have defined business domains, scale targets, and team structures that need to be reflected in your architecture.
You are a systems architect specializing in microservices. Design a microservices architecture for [APPLICATION]. Requirements: - Core domains: [DOMAINS] - Scale requirements: [SCALE] - Team structure: [TEAMS] - Current monolith: [IF MIGRATING] Create: 1. Service decomposition - Service boundaries - Domain ownership - API contracts 2. Communication patterns - Sync vs async - Event-driven design - Message queue selection 3. Data management - Database per service - Data consistency approach - Saga patterns 4. Infrastructure - Container orchestration - Service mesh needs - API gateway design 5. Observability - Logging strategy - Distributed tracing - Monitoring and alerts 6. Migration roadmap (if applicable) - Strangler fig pattern - Phase breakdown - Risk mitigation
Free to use — the optimizer tailors this template to your exact task and target AI.
How to customize it
- [APPLICATION] — Specify the system you're building, such as an e-commerce platform, financial processing system, or content management application
- [DOMAINS] — List the core business domains that will become separate services, like user management, payments, inventory, or notifications
- [SCALE] — Define your performance and capacity requirements, including expected traffic volume, data size, and geographic distribution
- [TEAMS] — Describe your development team structure and size to inform service ownership boundaries
What you'll get back
A structured architecture document covering six areas: service decomposition with boundaries and API contracts, communication patterns with sync/async recommendations, data management strategies including consistency approaches, infrastructure requirements for containers and gateways, observability setup with logging and tracing, and if applicable, a phased migration roadmap with risk mitigation s
More Coding prompts
Technical Spec Writer
Generates a structured technical specification document covering problem statement, design, implementation plan, and risks for engineering features or projects.
Code Reviewer
Instructs AI to perform a comprehensive code review covering bugs, security, performance, style, and best practices with severity ratings and corrections.
Security Audit Checklist
Generates a structured security audit checklist for code review, covering authentication, input validation, data protection, API security, and infrastructure concerns.
Legacy Code Modernization
Generates a structured modernization plan for legacy code, including assessment, migration options, phased implementation, testing strategy, and risk management.
Make this prompt yours
PromptWizz rewrites this template around your specific task, audience, and target AI — and shows you why each change works.
Try the Optimizer Free