Packages

Relay ships as ~40 focused packages under the Nuvora.Nexus.Relay.* prefix, all versioned together (currently 1.3.0, MIT licensed, targeting net10.0). Start with the meta package and add capabilities as you adopt them.

Area	Packages
Entry point	Nuvora.Nexus.Relay (meta), Nuvora.Nexus.Relay.Core
HTTP & web	.Http, .Web
Persistence	.Persistence, .Persistence.EfCore
Event store	.EventStore, .EventStore.EfCore
Projections	.Projections, .Projections.EfCore
Reliable messaging	.Outbox, .Outbox.EfCore, .Inbox.EfCore
Transports	.Messaging, .Messaging.RabbitMq, .Messaging.Kafka, .Messaging.AzureServiceBus, .Messaging.AmazonSqs, .Messaging.Nats, .Messaging.Pulsar, .Messaging.Nms, .Messaging.InMemory
Workflows	.Sagas, .Sagas.EfCore
Scheduling	.Scheduling, .Scheduling.EfCore
Tenancy	.Tenancy, .Tenancy.EfCore
Security	.Auth
Caching	.Cache, .Cache.InMemory, .Cache.Redis
Operations	.Diagnostics, .Management, .Management.Agent, .Management.Contracts
Tooling	.Generators (source generators + RelayHandlerAnalyzer)

Conventions worth knowing:

• .EfCore suffix — the PostgreSQL/EF Core persistence implementation of a capability; the base package holds the abstractions.
• .Messaging.* — one package per broker; all implement the same IMessageBroker / IMessageConsumer contract, so transports swap without code changes.
• .Generators — compile-time diagnostics: RELAY001 (no handler for a message) and RELAY002 (duplicate handlers).

Source, samples and demos live in the nuvora-nexus-net monorepo.