Framework Distributed v3.0.2

Microsoft Orleans

Design Microsoft Orleans systems from each primitive's purpose and failure model. USE FOR: grains, digital twins, state versus databases, transactions, messaging, streams, timers, reminders, Durable Jobs, stateless workers, grain services, startup, and hosting. DO NOT USE FOR: other actor stacks, batches, relational-only CRUD, or advice without an Orleans decision. INVOKES: inspect version and topology, choose the primitive, implement, and validate.

Workflow

  1. Inspect the solution, Orleans version, hosting topology, grain interfaces, providers, and tests.
  2. Identify domain identities and invariants. Prefer many independent, bounded entities over global coordinator grains.
  3. Choose state, communication, and time-based work from the tables below.
  4. Keep default non-reentrant scheduling and placement until a measured requirement justifies a change.
  5. Configure providers independently and test the failure model the design depends on.

Load References

Related skills

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph…

ManagedCode.Orleans.Graph

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows.

ManagedCode.Orleans.SignalR.ServerManagedCode.Orleans.SignalR.Client

Related agents

Orchestration agent
8 linked skills

.NET Aspire Orchestrator

Specialist orchestration agent for .NET Aspire work.

agents install aspire-orchestrator

Also works: dotnet agents install aspire-orchestrator

Orchestration agent
5 linked skills

Orleans Specialist

Orleans specialist agent for purpose-first grain design, state versus database ownership, timers, reminders, Durable Jobs, stateless workers…

agents install orleans-specialist

Also works: dotnet agents install orleans-specialist