Install
| Product | Versions |
|---|---|
| .NET |
README
K4os.NatsTransit
Messaging library built on top of NATS JetStream: commands, queries, requests and events with pluggable serialization, OpenTelemetry instrumentation, outbox, sagas, distributed locks, key-value/object stores and caching.
Source, issues and full documentation: https://github.com/MiloszKrajewski/K4os.NatsTransit
Packages
All packages depend on K4os.NatsTransit.Abstractions and are peers, not layers (unless noted):
K4os.NatsTransitβ message bus (needs.Serialization)K4os.NatsTransit.Serialization,.NewtonsoftJson,.GoogleProtobufβ serializersK4os.NatsTransit.Storage,.Storage.AdoNetβ value store / object store (NATS KV, Object Store, SQL)K4os.NatsTransit.Lockingβ distributed locksK4os.NatsTransit.Caching,.Caching.FusionCacheβIDistributedCache/ FusionCache backplaneK4os.NatsTransit.Outbox,.Outbox.EFβ outbox patternK4os.NatsTransit.Sagasβ stateful long-running workflowsK4os.NatsTransit.HealthChecks,.OpenTelemetryβ observability
For AI agents: cheat sheet
Opinionated, recipe-style briefs for bootstrapping a service with these packages ship inside
K4os.NatsTransit.Abstractions (every package depends on it), in its doc/cheat-sheet/ folder. Once the package is
restored it is in the NuGet global-packages cache:
<global-packages>/k4os.natstransit.abstractions/<version>/doc/cheat-sheet/index.md
- If you are reading this file from the cache (
<global-packages>/k4os.natstransit.<package>/<version>/README.md), the same file is at../../k4os.natstransit.abstractions/<version>/doc/cheat-sheet/index.md. Inside the Abstractions package itself it is simplydoc/cheat-sheet/index.md. <version>is the currently referenced version of the package.<global-packages>is usually~/.nuget/packages, or the folder in theNUGET_PACKAGESenvironment variable when it is set. If neither helps,dotnet nuget locals global-packages -lprints the actual location.
Start with index.md, then read only the files matching the packages you use.
Changes from Previous Version
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.