.NEXT

.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:

• Buffer manipulations
• String building
• Monadic types
• Advanced GC notifications
• Low-level API to work with memory: alignment detection, type-safe unmanaged allocators, Span<T> manipulations
• Base64 streaming encoder/decoder
• Async-friendly SIEVE cache
• Async locks
• Extended LINQ Expression Trees and dynamic code generation tools with async lambdas for metaprogramming
• Raft Consensus Algorithm with extensions such as the failure detection
• Fast general-purpose Write Ahead Log
• TCP multiplexing protocol
• HyParView protocol implementation

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

Quick Links

• Features
• API documentation
• Benchmarks
• NuGet Packages

What's new

Release Date: 07-12-2026

DotNext 6.4.1

• Fixed race conditions occurred in async methods of the streams produced by StreamSource factory methods
• Updated dependencies

DotNext.Metaprogramming 6.4.1

• Updated dependencies

DotNext.Unsafe 6.4.1

• Updated dependencies

DotNext.Threading 6.4.1

• Reduced memory allocations in ManualResetCompletionSource class. short version token is no longer allocated on every Reset call. Additionally, even if timeout is happened, the internal timer can be reused again. It means that ManualResetCompletionSource class, it's derived classes and async locks do not allocate on all execution paths including worst cases
• ManualResetCompletionSource.Reset now throws an exception when the caller tries to reuse the completion source in the invalid state. Check Reset method remarks for more information

DotNext.IO 6.4.1

• Fixed race conditions occurred in async methods of FileReader and FileWriter classes
• Updated dependencies

DotNext.Net.Cluster 6.4.1

• Replication loop on leader doesn't allocate memory anymore when heartbeat timeout is happened. This is possible due to performance improvements in ManualResetCompletionSource class mentioned above
• Fixed issue when TCP multiplexer can hang

DotNext.AspNetCore.Cluster 6.4.1

• Updated dependencies

DotNext.MaintenanceServices 1.4.1

• 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	:x:
1.x	.NET Standard 2.0	:x:
2.x	.NET Standard 2.1	:x:
3.x	.NET Standard 2.1, .NET 5	:x:
4.x	.NET 6	:x:
5.x	.NET 8	:white_check_mark:
6.x	.NET 10	:heavy_check_mark:

:x: - unsupported, :white_check_mark: - bug and security fixes only, :heavy_check_mark: - 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

Users

.NEXT is used by several companies in their projects:

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.