SignalR.Orleans 7.2.0

dotnet add package SignalR.Orleans --version 7.2.0
NuGet\Install-Package SignalR.Orleans -Version 7.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="SignalR.Orleans" Version="7.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add SignalR.Orleans --version 7.2.0
#r "nuget: SignalR.Orleans, 7.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install SignalR.Orleans as a Cake Addin
#addin nuget:?package=SignalR.Orleans&version=7.2.0

// Install SignalR.Orleans as a Cake Tool
#tool nuget:?package=SignalR.Orleans&version=7.2.0

Build Package Version NuGet Downloads License Discord

Orleans is a cross-platform framework for building robust, scalable distributed applications. Distributed applications are defined as apps that span more than a single process, often beyond hardware boundaries using peer-to-peer communication. Orleans scales from a single on-premises server to hundreds to thousands of distributed, highly available applications in the cloud. See Orleans source code on Github

ASP.NET Core SignalR is an open-source library that simplifies adding real-time web functionality to apps. Real-time web functionality enables server-side code to push content to clients instantly.

SignalR.Orleans is a package that gives you two abilities:

  1. Use your Orleans cluster as a backplane for SignalR. Learn about scaling out SignalR on multiple servers.

There are various choices of backplane that you can use for SignalR, as you will see in the link above. If you're already using Orleans, then you might want to use Orleans as the backplane to reduce the number of dependencies used by your application and to reduce the number of network hops (and latency) that would be required when calling an external service.

  1. Send messages from Orleans grains to SignalR clients.

If the SignalR component of your application is cohosted with Orleans (same server, same process and Microsoft.AspNetCore.SignalR.IHubContext<MyHub> can be injected into an Orleans gain), you already have this ability without installing this package.

However, if the SignalR component of your application is "remote" from the grains, this package will give the grains a way of sending messages to SignalR clients by injecting SignalR.Orleans.Core.HubContext<MyHub>.

TODO: These two abilities should be provided independently of each other. Unfortunately at this stage, ability #2 is only provided if ability #1 is used as well.


Installation is performed via NuGet.

Packages with version 7.x.x are compatible with Orleans v7.x.x and above. If you're still using an earlier version of Orleans, you will need to use earlier versions of the package.

Package Manager:

PS> Install-Package SignalR.Orleans

.Net CLI:

# dotnet add package SignalR.Orleans


# paket add SignalR.Orleans

Version 7.0.0 documentation

Scroll down to see documentation for earlier versions.

Here is a complete starter example featuring cohosted aspnetcore app with SignalR and Orleans.

using Microsoft.AspNetCore.SignalR;
using Orleans.Hosting;
using SignalR.Orleans;

// Create a host that can cohost aspnetcore AND orleans together in a single process.
var builder = WebApplication.CreateBuilder(args);
builder.Host.UseOrleans(siloBuilder => 
    siloBuilder.UseSignalR(); // Adds ability #1 and #2 to Orleans.
    siloBuilder.RegisterHub<MyHub>(); // Required for each hub type if the backplane ability #1 is being used.

    .AddSignalR()  // Adds SignalR hubs to the web application
    .AddOrleans(); // Tells the SignalR hubs in the web application to use Orleans as a backplane (ability #1)

var app = builder.Build();
await app.RunAsync();

// A SignalR Hub.
class MyHub : Hub

Silo configuration - grain storage

The SignalR.Orleans backplane (ability #1) uses grains under the hood that use storage to keep track of where each SignalR client is connected and what groups it belongs to. The storage used by default is MemoryStorage.

Use the given storage name constant to configure the correct storage provider.

// **************************************************************************
// Use memory storage ONLY when your app is not clustered, otherwise you'll
// need to use proper external storage providers
// **************************************************************************
// Customize the storage used by the SignalR Orleans backplane grains.


Silo configuration - stream type and stream storage

SignalR.Orleans uses streams under the hood to provide the backplane (ability #1). The default stream type is MemoryStream. All streams in a given Orleans instance must use the same storage provider, named PubSubStore, currently defaulted to MemoryStorage.

// FIRST customize the storage used by ALL stream providers in the entire Orleans host:
// Remember, memory storage won't work if you're using a cluster.

// THEN customize the type of stream used for the backplane, using the correct stream provider name
siloBuilder.AddPersistentStreams(SignalROrleansConstants.SIGNALR_ORLEANS_STREAM_PROVIDER, adapterFactory, configureStream);


Sending messages from Orleans grains

If the SignalR app is cohosted as demonstrated above, you don't need this package to send messages from an Orleans grain. Simply inject IHubContext<MyHub> to the grain's constructor and call its methods to send messages. Read more about it here.

However, if the SignalR app is not cohosted, and if it's using Orleans as a backplane, then it's possible to use this package to send messages to the SignalR clients using the backplane streams in Orleans as a conduit (ability #2).

class SampleGrain : Grain, ISampleGrain
  private readonly SignalR.Orleans.Core.HubContext<MyHub> _hubContext;

  public SampleGrain(SignalR.Orleans.Core.HubContext<MyHub> hubContext)
    _hubContext = hubContext;

  public async Task SendMessageToClients()
    // Create an invocation message
    var msg = new InvocationMessage("method", new object?[]{ 1, 2, 3 }).ToImmutable();

    // Send a message to a single client
    await _hubContext.Client("someConnectionId").Send(msg);

    // Send a message to a group
    await _hubContext.Group("someGroupName").Send(msg);

    // Send a message to all connections made by a particular authenticated user
    await _hubContext.Group("someUserId").Send(msg);

    // TODO: We have not implemented ability to send a message to ALL clients yet.

Configuring the IClusterClient

If your SignalR app is cohosted with Orleans, it will automatically grab an IClusterClient from the service provider and connect to the Orleans backplane.

However, if it's not cohosted, you'll have to give it an IClusterClient to use:

using Microsoft.AspNetCore.SignalR;
using Orleans.Hosting;
using SignalR.Orleans;

// Create a web application that will connect to a remote Orleans cluster
var builder = WebApplication.CreateBuilder(args);
    // Adds an IClusterClient to the service provider.
    .AddOrleansClient(clientBuilder =>
        // Tell the client how to connect to Orleans (you'll need to customize this for yourself)
        // Tells the client how to connect to the SignalR.Orleans backplane.
        clientBuilder.UseSignalR(configure: null);
    .AddSignalR()  // Adds SignalR hubs to the web application
    .AddOrleans(); // Tells SignalR to use Orleans as a backplane (ability #1)

var app = builder.Build();
await app.RunAsync();

// A SignalR Hub.
class MyHub : Hub

This is the end of documentation for versions >= 7.0.0. Below is older documenation for previous versions.

Earlier version documentation

Configure the Silo

We need to configure the Orleans Silo with the below:

  • Use .UseSignalR() on ISiloHostBuilder.
  • Make sure to call RegisterHub<THub>() where THub is the type of the Hub you want to be added to the backplane.


var silo = new SiloHostBuilder()
  .RegisterHub<MyHub>() // You need to call this per `Hub` type.
  .AddMemoryGrainStorage("PubSubStore") // You can use any other storage provider as long as you have one registered as "PubSubStore".

await silo.StartAsync();

Configure Silo Storage Provider and Grain Persistance

Optional configuration to override the default implementation for both providers which by default are set as Memory.


.UseSignalR(cfg =>
  cfg.Configure((builder, config) =>


Now your SignalR application needs to connect to the Orleans Cluster by using an Orleans Client:

  • Use .UseSignalR() on IClientBuilder.


var client = new ClientBuilder()
  // optional: .ConfigureApplicationParts(parts => parts.AddApplicationPart(typeof(IClientGrain).Assembly).WithReferences())

await client.Connect();

Somewhere in your Startup.cs:

  • Add IClusterClient (created in the above example) to IServiceCollection.
  • Use .AddSignalR() on IServiceCollection (this is part of Microsoft.AspNetCore.SignalR nuget package).
  • Use AddOrleans() on .AddSignalR().


public void ConfigureServices(IServiceCollection services)

Great! Now you have SignalR configured and Orleans SignalR backplane built in Orleans!


Hub Context

HubContext gives you the ability to communicate with the client from orleans grains (outside the hub).

Sample usage: Receiving server push notifications from message brokers, web hooks, etc. Ideally first update your grain state and then push signalr message to the client.


public class UserNotificationGrain : Grain<UserNotificationState>, IUserNotificationGrain
  private HubContext<IUserNotificationHub> _hubContext;

  public override async Task OnActivateAsync()
    _hubContext = GrainFactory.GetHub<IUserNotificationHub>();
    // some code...
    await _hubContext.User(this.GetPrimaryKeyString()).Send("Broadcast", State.UserNotification);

Complete examples

Cohosting aspnetcore website and orleans

using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.ResponseCompression;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Orleans;
using Orleans.Hosting;

// Cohosting aspnetcore website and Orleans with signalR
var host = Host.CreateDefaultBuilder(args)

  // Add the webhost with SignalR configured.
  .ConfigureWebHostDefaults(webBuilder =>
    webBuilder.ConfigureServices((webBuilderContext, services) =>
      // Add response compression used by the SignalR hubs.
      services.AddResponseCompression(opts =>
        opts.MimeTypes = ResponseCompressionDefaults.MimeTypes.Concat(
            new[] { "application/octet-stream" });

      // Adds SignalR hubs to the aspnetcore website 
      services.AddSignalR(options =>
      .AddOrleans(); // Tells SignalR to use Orleans as the backplane.

    webBuilder.Configure((ctx, app) =>
      // Adds response compression for use by the SignalR hubs
      // Map SignalR hub endpoints
      app.UseEndpoints(endpoints =>
        endpoints.MapHub<MyHubType1>("/hub1"); // use your own hub types
        endpoints.MapHub<MyHubType2>("/hub2"); // use your own hub types
        // ... etc

  // Add Orleans with SignalR configured
  .UseOrleans((context, siloBuilder) =>
      .UseSignalR(signalRConfig =>
        // Optional.
        signalRConfig.UseFireAndForgetDelivery = true;

        signalRConfig.Configure((siloBuilder, signalRConstants) =>
          // **************************************************************************
          // Use memory storage ONLY when your app is not clustered, otherwise you'll
          // need to use proper external storage providers
          // **************************************************************************

          // This wouldn't be be necessary if you already added "PubSubStore" elsewhere.
          siloBuilder.AddMemoryGrainStorage(signalRConstants.PubSubProvider /*Same as "PubSubStore"*/);

      // Allows Orleans grains to inject IHubContext<HubType>
      // ... etc

await host.StartAsync();
await host.WaitForShutdownAsync(default);


PRs and feedback are very welcome!

Product Compatible and additional computed target framework versions.
.NET net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
7.2.0 2,026 8/28/2023
7.1.0 7,610 2/15/2023
7.0.1 690 2/14/2023
2.2.1 5,969 1/19/2023
2.2.0 10,504 8/8/2022
2.1.0 17,713 10/5/2021
2.0.1 6,338 2/15/2021
1.5.0 18,070 11/1/2019
1.4.4 7,759 11/1/2019
1.4.3 7,382 9/23/2019
1.4.2 2,765 9/8/2019
1.4.0 3,874 7/8/2019
1.3.2 3,497 6/13/2019
1.3.1 1,443 6/10/2019
1.2.0 2,873 3/21/2019
1.1.2 1,296 2/25/2019
1.1.1 1,717 1/24/2019
1.0.6 3,729 10/12/2018
1.0.5 1,973 7/24/2018
1.0.4 1,339 7/24/2018
1.0.3 1,361 7/4/2018
1.0.2 1,528 7/4/2018
1.0.1 1,533 6/23/2018
1.0.0-preview-65 1,579 5/31/2018
1.0.0-preview-63 1,404 5/8/2018
1.0.0-preview-60 1,317 4/25/2018
1.0.0-preview-58 1,249 4/24/2018
1.0.0-preview-52 1,421 3/28/2018
1.0.0-preview-50 1,542 3/28/2018
1.0.0-preview-47 1,374 3/16/2018
1.0.0-preview-44 1,314 3/13/2018
1.0.0-preview-42 1,332 3/5/2018
1.0.0-preview-39 1,336 3/5/2018
1.0.0-preview-37 1,293 3/2/2018
1.0.0-preview-32 1,754 12/21/2017
1.0.0-preview-26 1,251 12/12/2017
1.0.0-preview-22 1,243 11/24/2017
1.0.0-preview-19 1,181 11/22/2017