How nzuguem/quarkus-temporal-petstore works
Main Components
a. Client Layer:
• Web UI (Purchase Order Gateway - Port 8082)
• REST API endpoints
b. Microservices:
• Purchase Order Gateway Service (Workflow Orchestrator)
• Notification Service
• Order Service
• Payment Service
• Warehouse Service
• Shipment Service
c. Infrastructure Components:
• Temporal Server
• PostgreSQL Database
• Mailpit (SMTP Server)
• Jaeger (Distributed Tracing)
┌─ Client Layer ─────────────────────────────────┐
• Web UI (JSF) │ REST API │
• Service Layer ──────────────────────────────┐ │
• ┌─────────────┐ ┌─────────────┐ │ │
• Purchase │ │ Notification │ │ │
• Gateway │──▶ Service │ │ │
• ┘ └─────────────┘ │ │
• ┌─────────────┐ │ │
• ▶│ Order │ │ │
• Service │ │ │
• ┘ │ │
• ┌─────────────┐ │ │
• ▶│ Payment │ │ │
• Service │ │ │
• ┘ │ │
• ┌─────────────┐ │ │
• ▶│ Warehouse │ │ │
• Service │ │ │
• ┘ │ │
• ┌─────────────┐ │ │
• ▶│ Shipment │ │ │
• Service │ │ │
• ┘ │ │
• Infrastructure Layer ────────────────────────┤
• ┌─────────┐ ┌────────┐ ┌───────┐ ┌────────┐ │
• Temporal │ │Postgres│ │Mailpit│ │ Jaeger │ │
• ┘ └────────┘ └───────┘ └────────┘ │
• ┘
Important Workflow Patterns to Highlight
• Main workflow path:
1. Order Submission → Gateway
2. Notification (Order Received)
3. Order Creation
4. Payment Processing
5. Inventory Check
6. Shipment Creation
7. Order Completion
8. Final Notification
• Compensation workflow:
1. Error Detection
2. Payment Reversal
3. Order Status Update
4. Error Notification
Additional Elements
• Port numbers for each service
• Temporal workflow boundaries
• Error handling paths
• Monitoring points for Jaeger tracing
Technical Details
• Quarkus Framework indicators
• Temporal workflow boundaries
• Database connections
• Email notification paths
• REST endpoint locations
• OpenTelemetry integration points
Notes for Implementation
• Keep the main workflow path clear and central
• Related services together
• Clear boundaries between layers
• External integration points
• Critical transaction boundaries
• Where compensating transactions occur
Remember to maintain a balance between detail and clarity, focusing on the key architectural components while ensuring the workflow patterns are easily understood.