--- title: "Getting Started With NATS JetStream in .NET" url: https://daily.dev/posts/getting-started-with-nats-jetstream-in-net-6r74llqr0 source_url: https://www.milanjovanovic.tech/blog/getting-started-with-nats-jetstream-in-dotnet type: article source: "Milan Jovanović" published: 2026-06-26T21:55:03.819Z updated: 2026-06-27T00:19:25.873Z tags: ["architecture", ".net", "aspnetcore"] reading_time: 6 upvotes: 16 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Getting Started With NATS JetStream in .NET **[Milan Jovanović](https://daily.dev/sources/milanjovanovic)** · 6 min read · 16 upvotes · 0 comments ## Summary NATS JetStream is a lightweight, fast messaging system that rarely gets mentioned in .NET circles despite being a compelling alternative to RabbitMQ or Azure Service Bus. Running as a single 18 MB Go binary with no external dependencies, NATS with JetStream enabled provides durable, at-least-once delivery. The guide walks through setting up NATS via Docker Compose, wiring the .NET client into ASP.NET Core DI, publishing typed messages from a Minimal API endpoint, and consuming them in a BackgroundService. Key concepts covered include stream retention modes (Workqueue, Limits, Interest), storage options (File vs Memory), and the critical rule of acknowledging messages only after the side effect completes to ensure reliability. Idempotent consumer handling is also highlighted as a necessary companion pattern. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#architecture](https://daily.dev/tags/architecture), [#.net](https://daily.dev/tags/.net), [#aspnetcore](https://daily.dev/tags/aspnetcore) [View this post on daily.dev](https://daily.dev/posts/getting-started-with-nats-jetstream-in-net-6r74llqr0)