Scry.Server.Rebus
0.1.0-beta.13
dotnet add package Scry.Server.Rebus --version 0.1.0-beta.13
NuGet\Install-Package Scry.Server.Rebus -Version 0.1.0-beta.13
<PackageReference Include="Scry.Server.Rebus" Version="0.1.0-beta.13" />
<PackageVersion Include="Scry.Server.Rebus" Version="0.1.0-beta.13" />
<PackageReference Include="Scry.Server.Rebus" />
paket add Scry.Server.Rebus --version 0.1.0-beta.13
#r "nuget: Scry.Server.Rebus, 0.1.0-beta.13"
#:package Scry.Server.Rebus@0.1.0-beta.13
#addin nuget:?package=Scry.Server.Rebus&version=0.1.0-beta.13&prerelease
#tool nuget:?package=Scry.Server.Rebus&version=0.1.0-beta.13&prerelease
Scry.Server.Rebus
Carries Scry commands over Rebus: a command a client sends is sent to the handler that handles it, and its outcome comes back to the client when the handler replies.
On the Scry server:
builder.Services.AddScry<SampleContext>(
_ =>
{
_.MaxPendingCommands = 100;
_.UseRebusCommands(_ => _.For<RepriceOrder>());
});
builder.Services.AddRebusHandler<RebusCommandCompletedHandler>();
builder.Services.AddRebus(
configure => configure
.Transport(_ => _.UseRabbitMq(connection, "web-node-1"))
.Routing(_ => _.TypeBased().Map<RepriceOrder>("worker")));
On the worker:
builder.Services.AddRebusHandler<RepriceOrderHandler>();
builder.Services.AddRebus(
configure => configure
.Transport(_ => _.UseRabbitMq(connection, "worker"))
.Options(_ => _.EnableScryCompletion()));
The server validates, authorizes and binds the command as it would for an in-process handler, then sends it with the command's id and caller as headers, routed by the bus's own routing. The handler is an ordinary IHandleMessages<T>. Once the handlers have returned, the worker replies inside the message's own transaction, so the reply leaves only if the handler's work was kept, and once for a message that was retried. A message that exhausts its delivery attempts is answered as failed as it goes to the error queue. A handler of a command with a result answers with MessageContext.Current.SetScryResult(result).
It claims nothing until told: a Rebus message is any class. Everything it does not claim stays with its in-process handler. The reply comes back to the input queue the command was sent from, so each node needs an input queue of its own.
This package carries no change backplane. A handler's writes reach live queries through the notification the server raises on completion for a targeted command, a change probe, or the poll.
Docs: Commands
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.EntityFrameworkCore (>= 10.0.12)
- Rebus (>= 8.9.5)
- Scry.Server (>= 0.1.0-beta.13)
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 |
|---|---|---|
| 0.1.0-beta.13 | 0 | 10/7/2026 |
| 0.1.0-beta.12 | 44 | 10/1/2026 |
| 0.1.0-beta.11 | 47 | 9/30/2026 |
| 0.1.0-beta.10 | 55 | 9/24/2026 |