Microservices Architecture Planner
By Mr Tech King · Published · Updated
Plan and define a microservices architecture for a given application.
Tags: coding, architecture, microservices
Prompt template
## Introduction Design a scalable microservices architecture for your application including service boundaries and communication patterns. ## Application Overview - Application Type: [text: e.g., E-commerce platform, SaaS dashboard, Fintech app] - Current Architecture: [dropdown: Monolith, Mini-services, Already microservices, Greenfield] - Expected Scale: [dropdown: Small (<1000 users), Medium (1000-100k users), Large (100k+ users), Massive (millions)] ## Service Design - Domains to separate into services: [textarea: List business domains, e.g., Authentication, Orders, Inventory, Notifications] - Communication Pattern: [multi: REST API, gRPC, GraphQL, Message queue (Kafka/RabbitMQ), Event sourcing] ## Infrastructure - Container orchestration: [dropdown: Kubernetes, Docker Swarm, ECS (AWS), Cloud Run, None] - Service mesh: [toggle: Yes, No] - API Gateway: [toggle: Yes, No] - Include observability (logging, metrics, tracing): [toggle: Yes, No]