A walkthrough of the 2019 Socrates paper behind Azure SQL Database Hyperscale. The design splits compute, transaction log, page servers and storage into separate tiers, which is why backups, restores and adding replicas no longer scale with database size. Developers running or evaluating Hyperscale get a clear view of the architecture behind it.
Part 3 of Scott Galloway's series builds a temporal predictor in C#. It tracks a journey's centroid, velocity and acceleration in real time, then forecasts whether it ends in purchase, cancellation or departure within 60 seconds. The engine learns only from actual endpoints and abstains when evidence is thin, which makes it a concrete example for teams building SQLite-backed behavioural or service-health models.
Mauro Servienti uses a shipping notification that arrived seven times to explain how duplicate messages happen in messaging systems. The post separates duplicates caused by sending, receiving and processing, and lists practical defenses for each. It is a useful read for any .NET developer building queue-based systems.
A team moving a relationship-heavy system from MySQL to graph databases reports that a recursive CTE collapsed at around 500 million rows. The author built a reproducible benchmark comparing the CTE, a C# breadth-first search on the same MySQL tables, and NebulaGraph. The results suggest the CTE's design, not the relational engine, caused most of the delay.
The article explains how to register MongoClient as a singleton in ASP.NET Core and how request-scoped services should borrow it. It shows that disposing the client through the container does not close the driver's cluster, and that the selected driver version changes the answer. It is a useful reference for teams running MongoDB in web apps.
This guide covers how ASP.NET Core background services can stop cleanly during shutdown without losing or duplicating work. It walks through cancellation tokens, scoped dependencies, queue acknowledgement order and host shutdown timeouts, with a test checklist for production readiness.
Wolverine 6.51.3 is a durability release that fixes a run of problems in the durable inbox and outbox. A new receiver compliance suite exercised PostgreSQL, SQL Server, Marten, EF Core, RabbitMQ and SQS, and the fixes cover transactions, deduplication, retries and dead lettering. There are no breaking API changes, and the one schema addition is optional.
Part 5 of the Transmitly eShop series shows how delivery updates that arrive after dispatch are captured and stored. Provider webhooks, such as Twilio status callbacks, are normalized into one DeliveryReport model and saved in a Communications database. It is a practical reference for building message history and delivery tracking in ASP.NET Core.
Part 4 of NimblePros' domain modeling series walks through saving C# 15 unions and closed hierarchies with System.Text.Json on the .NET 11 RC1 SDK. It shows where the built-in classifiers are enough and where a hand-made "kind" discriminator is still needed. Useful for any developer persisting polymorphic domain state to JSON.
The author of the C# interpreter HydraScript explains why numeric instruction indexes broke code generation and how switching to stable IAddress objects fixed it. Addresses now stay with their instructions when code is inserted, removed or replaced, so jumps keep pointing to the right place. It is a concrete case for developers building compilers or interpreters with the Visitor pattern.
This guide explains how to scale ASP.NET Core SignalR across several servers using either a Redis backplane or Azure SignalR Service. It covers why messages fail to reach clients on other servers, how each option distributes them, and when sticky sessions are still needed. It is a practical starting point for teams moving real-time apps into production.
An overview of the C# 15 features: union types, closed class hierarchies, named break and continue, extension indexers, with-arguments in collection expressions and the revised unsafe model. It shows how each one changes everyday code and where the caveats are.