Home Archive Issue #586
Issue #586

Queues, JSON, and ASP.NET Core

This edition examines backpressure, .NET 11 JSON contracts, keyed DI, threading, large-file streaming, event counting, and money rules.

Jasen's top three picks

  1. 1
    A queue is a shock absorber, not a pump

    C# Digest

    A useful framing: queues buy time during bursts, but downstream throughput still determines whether the system recovers.

  2. 2
    System.Text.Json in .NET 11: What Actually Changed for Backend APIs?

    Medium

    Worth reviewing for backend teams adopting newer JSON features without losing sight of generated contract behavior.

  3. 3
    Need a Dictionary of Keyed Services in ASP.NET Core 8? Here’s What You Should Know

    Medium

    Keyed DI can simplify multiple implementation selection, but it still deserves clear composition-root conventions.

Editor's note

I pulled together a deliberately broad mix today, from runtime mechanics to API design and business correctness. The queue article is a useful correction to a common scaling misconception, while the large-file upload piece covers the practical streaming choices that prevent avoidable memory pressure. I also liked the attention given to JSON contracts and idempotent play counting, where small implementation decisions can become production problems.

Today's articles

Five Questions I Ask of Every .NET Release

Bipin Joshi .NET | Thus said a Byte • Insights on .NET and Web Development

Every new .NET release brings a familiar wave of announcements, features, and improvements. But do we all read these announcements in the same way? Over the years, I have noticed that the questions I ...

Topics: .NET Core

Read article

Related issues

📬 Save the search. Get the .NET stories worth reading at 7 AM ET.