managedcode-orleans-signalr
ManagedCode.Orleans.SignalR
Trigger On
- integrating
ManagedCode.Orleans.SignalRinto a real-time distributed application - coordinating SignalR delivery from Orleans grains
- reviewing grain-to-hub push flows and connection routing
- documenting how Orleans state or events become SignalR messages
Workflow
- Confirm the application genuinely needs both Orleans and SignalR in the same flow.
- Identify which grain events or workflows should publish to connected clients.
- Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
- Document how user, group, or connection targeting is resolved.
- Validate end-to-end message delivery from grain event to connected client.
flowchart LR
More from managedcode/dotnet-skills
dotnet
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
18dotnet-aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.
13dotnet-entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications.
12dotnet-code-review
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.
11dotnet-architecture
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
11dotnet-signalr
Implement or review SignalR hubs, streaming, reconnection, transport, and real-time delivery patterns in ASP.NET Core applications.
10