System architecture diagram for a microservices platform
Prompt
Create a clean, professional system architecture diagram for a [platform_type] platform. The diagram should show:
- [num_services] microservices with clear boundaries
- API Gateway as the entry point
- Message queue for async communication
- Database per service pattern
- Shared services (auth, logging, monitoring)
- External integrations (payment, email, storage)
- Load balancer and CDN at the edge
Style: clean technical diagram with a [color_scheme] color scheme, rounded rectangles for services, arrows for data flow, and clear labels. No hand-drawn aesthetic — this should look like it belongs in a technical design document.Customise this prompt
Fill in 3 variables to personalise this prompt
Example output
A polished technical architecture diagram showing a microservices platform for a social content application. The layout flows left to right across five vertical swim lanes. **Edge Layer (leftmost):** A CDN node (Cloudflare icon abstraction) connects to a Load Balancer, which fans out to an API Gateway box. The edge layer uses a cool blue color scheme. **Gateway Layer:** The API Gateway (Kong/Nginx) sits centrally with dotted lines showing rate limiting, auth verification, and request routing. It connects to an Auth Service (with a key icon) that interfaces with a dedicated PostgreSQL database and Redis for session storage. **Core Services Layer (middle, largest section):** Six service boxes arranged in a 2x3 grid, each with its own small database icon below: 1. User Service → PostgreSQL 2. Content Service → PostgreSQL 3. Feed Service → Redis + PostgreSQL 4. Notification Service → PostgreSQL 5. Search Service → Elasticsearch 6. Analytics Service → ClickHouse Each service box is a rounded rectangle with a subtle gradient header in the brand color. Service-to-service communication flows through a central Message Queue (Redis Streams / RabbitMQ) depicted as a horizontal bus connecting all services. **Shared Infrastructure Layer:** Below the services, a horizontal bar contains: Logging (ELK Stack), Monitoring (Prometheus + Grafana), and Distributed Tracing (Jaeger). Dotted lines from every service feed into this layer. **External Integrations (rightmost):** Three boxes for external services: Payment Gateway (Stripe), Email Service (AWS SES), and Object Storage (S3/R2). Arrows from specific core services connect to their relevant external integration. Color scheme: navy blue for infrastructure, teal for core services, orange for external integrations, gray for shared services. All text uses a clean sans-serif font. Arrows are color-coded: solid blue for synchronous HTTP calls, dashed green for async message queue events, dotted gray for monitoring/logging data flow.