The Azure Cosmos DB Change Feed Processor spreads change processing across several .NET workers using a lease container for ownership and checkpoints. The article walks through the setup in the .NET SDK and explains when adding workers actually helps. It also covers why downstream operations must be idempotent, since changes can be delivered again after a failure.
In .NET 11, the runtime can suspend and resume async methods itself, so the C# compiler no longer generates a state machine for them. The feature is in preview and is opted into per project. The post shows the much smaller IL, cleaner stack traces, and what still changes when you debug.
C# Corner walks through reading CBOR data with the System.Formats.Cbor package, from a basic CborReader example to buffering partial network reads. It stresses separating incomplete input from malformed data, enforcing size limits and defining message boundaries. Useful for services that receive binary payloads from devices or APIs.
NimblePros published its Tiles & Tokens sample, which relies on C# 15 unions and closed hierarchies, as a Native AOT binary on the .NET 11 RC1 SDK. The domain and serialization code produced no trimming or AOT warnings, and the native app ran correctly. The publish errors came from a reflection-based converter, an anonymous type and EF Core, which is a useful checklist for anyone planning a Native AOT app.
CritterWatch 1.1 groups dead letters by the failure that produced them, merging matches across every monitored service and database into one row. An operator can replay, archive, restore or discard a whole group as a single tracked operation with a required reason. The release also exposes the same loop through MCP, so teams running Wolverine can handle incidents faster and check whether replayed messages failed again.
ServiceStack v10.4 adds db.Explain() to OrmLite, which returns the query plan of a typed query without running it. The Profiling Admin UI also gets a Slowest Queries view where you can explain, analyze and re-run an app's slowest SQL from the browser. Together they make it easier to spot missing indexes.
This installment of Microsoft's PostgreSQL-to-SQL field notes compares how each engine helps you diagnose slow queries. It shows which Azure SQL dynamic management views and functions expose in-flight plans, last actual plans, wait statistics and memory grants without preinstalled extensions. Developers moving data access code or troubleshooting Azure SQL performance will find the setup details useful.
.NET 11 moves async method suspension from compiler-generated state machines to the runtime, with the JIT optimizing the boundaries between async methods. The author reruns the official benchmarks on RC2 and compares allocations, stack traces and assembly size. The gains are real in synchronous await chains and exception-heavy paths, but measurement setup changes the picture.
After six years without a stable release, Dapper FluentMap is maintained again and version 3.6.0 adds nested mappings, property converters, isolated runtimes, analyzers and source generators. The author stresses keeping existing applications working during upgrades. The piece also covers what to check before moving from 2.0.0 and which databases are certified.
A practical guide to configuring Npgsql connection pooling in .NET and sizing pools across multiple application instances so PostgreSQL does not run out of connections. It stresses that pool limits must be calculated for the whole deployment, not a single process.
A new dotnetpro series walks through building a Game Boy emulator in C#. Part one covers the 16-bit address bus, the 64 KB memory map, CPU registers modeled as C# fields and properties, and the flag register. It also shows how opcodes are dispatched in a switch loop and how cycle counting keeps components in sync.
ServiceStack v10.4 lets OrmLite retry temporary database errors such as deadlocks, throttling and failovers through a single configuration line. It also adds read replica support, with read-only connections that reject writes even on the primary so replica bugs surface during development. Both features matter for any .NET app that talks to a database under load.