How spicycoder/dapr-blocks works
High-Level Architecture Overview
a. Building Blocks Layer
• State Management
• Secret Management
• Service Invocation
• Pub/Sub
• Bindings
b. Infrastructure Layer
• Dapr Runtime & Sidecars
• Tye Orchestration
• Supporting Services (Redis, etc.)
Component-Specific Details
For each building block, include:
a. Service Invocation
• HeroesApi and ContactsApi as separate microservices
• Direct service-to-service communication via Dapr
b. Pub/Sub
• Publisher and Subscriber services
• Redis PubSub component
c. State Management
• StateStore service
• To Redis state store
• State persistence flow
d. Secret Management
• SecretStore service
• Connection to local secret store
• Secret retrieval flow
e. Bindings
• InputOutputBindings
• Cron and Email binding components
Cross-Cutting Concerns
Sections for:
• Distributed Tracing
• Logging
• Common Library (shared models)
Implementation Details
• Controllers within each service
• Shared models from Common/Library
• Configuration files (tye.yaml, component yamls)
• Deployment configurations
Relationships
Clearly indicate:
• Service-to-service communication patterns
• Data flow directions
• Component dependencies
• Infrastructure requirements
• Maintain hierarchy: Start with high-level architecture, then drill down into building blocks
• Both runtime and deployment views
• Scaling points and potential bottlenecks
• Version information for major components
• Notes about configuration requirements
• Integration points with external systems
• Service discovery
• State management
• Pub/sub messaging
• Secret management
• External bindings
• Deployment orchestration
Remember to maintain a balance between detail and clarity, focusing on the architectural decisions while avoiding overwhelming implementation details.