Skip to content

Repository files navigation

.NEXT

Build Status License Test Coverage CodeQL Ask DeepWiki

.NEXT (dotNext) is a set of powerful libraries designed for high-performance scenarios when your application expects near zero memory allocation and high flexibility. It is aimed to high-load microservices, database engines, actors, and various types of distributed applications. The feature list includes a rich set of efficient tools with low overhead:

All these things are implemented in 100% managed code on top of existing .NET API.

Quick Links

What's new

Release Date: 09-20-2026

DotNext 6.8.0

  • Added read-only concurrent access to custom struct field in Atomic<T> container

DotNext.Metaprogramming 6.8.0

  • Updated dependencies

DotNext.Unsafe 6.8.0

  • Updated dependencies

DotNext.Threading 6.8.0

  • Updated dependencies

DotNext.IO 6.8.0

  • Updated dependencies

DotNext.Net.Cluster 6.8.0

  • Added FlushOnCommit option to WriteAheadLog.Options: guarantees that a log entry is durably flushed to disk before AppendAsync/CommitAsync returns, even if not yet committed — closes a gap where a follower could lose an uncommitted entry on restart and later end up with a conflicting committed entry once a new leader replicates a different value at the same index. Trades away eager durability of the checkpoint's commit index (which is safely recomputed from committed entries on restart) for this guarantee
  • Fixed a race in WriteAheadLog's background flusher where the commit index could be considered "flushed" before it was actually written to the checkpoint, causing FlushAsync to return prematurely
  • Fixed a bug where installing a snapshot that skips over a range of log indices (e.g. via InstallSnapshot) could leave the flusher and page-compaction logic reading uninitialized metadata for that boundary index, in rare cases causing background flushes to stall for extended periods or, more seriously, causing compaction to delete data pages still needed by log entries appended after the snapshot
  • Fixed a bug in WriteAheadLog's cleanup scheduling that could repeatedly re-trigger page compaction for the same snapshot on every flush cycle instead of once per snapshot advancement
  • WriteAheadLog writes the checkpoint in a durable way on DisposeAsync call, no need to call FlushAsync explicitly before it

DotNext.AspNetCore.Cluster 6.8.0

  • Updated dependencies

DotNext.MaintenanceServices 1.8.0

  • Updated dependencies

Release & Support Policy

The libraries are versioned according to Semantic Versioning 2.0.

Version .NET compatibility Support Level
0.x .NET Standard 2.0
1.x .NET Standard 2.0
2.x .NET Standard 2.1
3.x .NET Standard 2.1, .NET 5
4.x .NET 6
5.x .NET 8
6.x .NET 10 ✔️

❌ - unsupported, ✅ - bug and security fixes only, ✔️ - active development

Development Process

Philosophy of development process:

  1. All libraries in .NEXT family are available for various .NET form factors: Mono, WASM, NativeAOT
  2. Minimal set of dependencies
  3. Provide high-quality documentation
  4. Stay cross-platform
  5. Provide benchmarks

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the .NET Foundation Code of Conduct. For more information see the Code of Conduct FAQ or contact conduct@dotnetfoundation.org with any additional questions or comments.