How dotnet/orleans works
Core Components (Main Layer)
a. Silo Layer (Central Component)
• Multiple silos forming a cluster
• Runtime services within each silo
b. Grain Layer
• Grains inside silos
• Grain components: Identity, State, Behavior
• Grain lifecycle management
c. Client Layer
• Client applications connecting to the cluster
• Client library components
Key Subsystems (Secondary Layer)
a. Membership & Clustering
• Membership table
• Cluster management components
• Silo-to-silo communication
b. Storage Providers
• Persistence systems
• State management
• Different storage options (Azure, AWS, ADO.NET)
c. Streaming System
• Stream providers
• Pub/sub infrastructure
• Queue integration
Supporting Features (Tertiary Layer)
a. Transaction System
• Transaction manager
• ACID guarantees
• Distributed transaction coordination
b. Reminders & Timers
• Reminder service
• Timer management
c. Placement & Load Balancing
• Placement strategies
• Load balancer
• Directory service
Cross-Cutting Concerns
a. Security
• Authentication
• Authorization
• Transport security
b. Monitoring & Diagnostics
• Telemetry
• Logging
• Health monitoring
Use the following visual elements:
• Blue: Core runtime components
• Green: Grain-related components
• Orange: Client components
• Purple: Storage and persistence
• Yellow: Streaming and messaging
Labels
• Clear component names
• Interface definitions
• Protocol indicators
• Version information
Grouping
• Cluster boundary
• Silo boundaries
• Subsystem boundaries
Specific aspects from the codebase:
Relationship between
• src/Orleans.Runtime (Silo implementation)
• src/Orleans.Core (Core functionality)
• src/Orleans.Streaming (Streaming infrastructure)
• src/Orleans.Transactions (Transaction system)
Integration points
• Azure components (src/Azure)
• AWS components (src/AWS)
• ADO.NET providers (src/AdoNet)
Extension points
• Custom storage providers
• Stream providers
• Grain interfaces
• Distributed nature
• Elasticity and fault tolerance
• Virtual actor model
• State management
• Programming model simplicity
Remember to maintain a balance between detail and clarity, focusing on the architectural aspects while avoiding implementation-specific details.