Using a parcel-delivery story as its analogy, this guide walks through the Retry pattern with Polly v8's `ResiliencePipeline` model, covering retry, exponential backoff, jitter, timeouts and `Retry-After` handling for HTTP calls. The sample uses the `Microsoft.Extensions.Http.Resilience` 10.0.0 package on .NET 10 in a Clean Architecture product-lookup scenario.
C# 15 lands with .NET 11 in November, and beyond union types it brings a set of small changes that remove daily friction in ordinary code. The post walks through with(...) collection expression arguments, extension indexers, labeled break and continue, and the preview redesign of unsafe — including the rules and the traps.
Putting a queue in front of a struggling service absorbs a spike but never adds throughput. Irina Scurtu works through the arithmetic of backlog and drain time with Azure Service Bus and Azure Functions, shows how depth-based scaling pushes the overload one hop downstream, and explains the TTL and dead-lettering settings that keep stale work from clogging the pipeline.
News from Claude Code, Codex, GitHub Copilot and Cursor, every morning on a page of its own, summarized in Turkish and English.
Read the AI newsSince version 2.0, Microsoft's SQL MCP Server container image ships with a built-in configuration file, and a single environment variable named DAB_CONNSTRING overrides its connection string. That means a working MCP endpoint in minutes with no custom image and no mounted JSON file. The catch: the bundled defaults are built for developers, with anonymous CRUD permissions including mutations, so production needs real configuration.
Jeremy D. Miller walks through Bobcat's flow-based specifications using a trial-license feature on the JasperFx portal. Existing xUnit and Alba tests are re-expressed so the business rules read top to bottom like prose, with each step delegating to a helper method behind a Given/When/Then line. The post also shows how a failing spec renders a message-activity table that an AI agent can read to diagnose the failure.
Razi Syed, who works on Dotnet Report, shows how a self-service report builder separates authorization into three layers: server-side identity read from the auth cookie, access fields stored as data on each report and folder, and claims reserved for the operations that step outside the normal rules. The pattern carries over to any ASP.NET Core app where users create and share resources.
The redb.core team compares loading the same business object — an Employee with addresses, contacts and dictionaries — as 54 tables and 31 Include chains in EF Core versus a single class in their own ORM. On a 100k-object data set EF Core reads one employee with 62 SQL queries in almost two seconds, while redb Pro finishes in 131 ms with nine queries. The write-up argues the gap comes from how many tables a graph spans, not raw engine speed.
A ticketing team's account of wiring Telr's hosted payment page into ASP.NET Core, where the hard part is not the redirect but everything after it: a return URL that proves nothing, a signed callback that can arrive twice or late, and a server-side order/check that should be the only source of truth. Covers one session per order, invariant-culture amounts, callback signature checks and single-claim fulfilment.
The second part of this caching deep dive compares FusionCache and Output Cache and closes with a decision guide for picking a layer. FusionCache adds a Redis backplane, fail-safe and factory timeouts on top of the HybridCache shape, while Output Cache middleware stores whole HTTP responses and evicts them by tag.
A full-text search built on SQL Server stopped returning results for valid queries, and the reason was the word 'both' sitting on the English stoplist, so it never entered the index. The author shows how sys.dm_fts_parser exposes the Noise Word and weighs four fixes before turning the stoplist off entirely.
Alba, JasperFx's ASP.NET Core integration testing library, is close to its 9.0 release, with RC3 published on October 25 as the last release candidate. The headline feature is a host pool that avoids spinning up fresh IHost instances and databases for every parallel test, joined by scenarios addressed by route name, JSONPath and problem details assertions, endpoint coverage and authorization audits, a fake TimeProvider for time travel, and server-sent events support.