A production write-up on rate limiting and resource governance for MCP orchestration servers, where a single tenant's burst can exhaust shared LLM token quota and starve everyone else. It compares the common limiter algorithms and lands on per-tenant token buckets with Redis-backed state and quota-aware refill rates.
A method that returns IReadOnlyList<T> tells the caller it cannot write, but says nothing about whether the data is an independent copy, a live view or a fixed report. The article separates the declared capability from the ownership and lifetime contract, then evaluates each collection return shape against both layers.
A C# walkthrough of Gauss-Legendre quadrature that computes Legendre polynomial roots and weights at runtime instead of shipping precomputed tables. Bonnet's recurrence keeps the polynomial evaluation stable past degree 15, and Newton's method finds each root to about 1e-10 in a few iterations.
NebulaGraph has no unique indexes, so duplicates in a graph load usually come from unstable vertex IDs and edge ranks. The author shows how to derive deterministic VIDs from business keys with FNV-1a and pin edge rank, which makes repeated loads safe. A batched .NET ingestion pipeline with checkpoints and retries is included.
This article explains the difference between delegates and events in C#, the subscription boundary an event creates, and how multicast invocation behaves when a handler throws. It also covers what notification does not guarantee: completion of every subscriber, async handling and subscription lifetime. Read it to design event-based notifications with clearer contracts.
Azure SQL Database Hyperscale splits a single-writer SQL engine across separate compute, log, page server and storage tiers, so it is distributed in architecture but not in write capacity. The author explains where that line falls against the usual meaning of distributed SQL, and cites a commissioned benchmark against Aurora PostgreSQL. Useful when you choose a database for a growing workload.
In SQL Server 2019 and later, varchar columns using a collation whose name ends in _UTF8 can store Unicode text, so not every text column has to become nvarchar. The change is more than a single database setting, though: comparisons, sorting, unique indexes and storage sizes all shift. The article lays out a step-by-step path from column inventory to production rollout.
C# 15 lets you declare indexers inside extension blocks, so types you don't own can support square-bracket access. Adding Count and Slice also unlocks index-from-end, ranges, and list patterns. The feature was tested on the .NET 11 RC 1 SDK, and the article lists its gotchas: real indexers win silently, arrays and strings are excluded, and expression trees reject it.
This post explains how a .NET ERP framework applies TableSchema definitions to the physical database without migration scripts. Each upgrade compares the live structure with the definition, then separates compare, plan and execute so the mode (ALTER or rebuild) can be checked before running. It is useful for developers who maintain schemas that already hold production data.
JasperFx shipped 72 tagged releases across Wolverine, Marten and shared libraries between October 12 and 30. The headline theme is a durable inbox and outbox hardening pass that closed about a dozen ways messages could go missing or run twice, much of it driven by community bug reports. For .NET developers running durable messaging, the review also covers performance fixes, cleaner shutdown and multi-tenant Marten changes.
CodoMetis.ValueRanges 10.4 and EFCore.ComplexIndexes are used to build a holiday-cottage booking API end to end. Date ranges are modelled as single values, overlapping bookings are blocked by a PostgreSQL exclusion constraint, and free nights are computed in one query. A practical example for EF Core developers working with PostgreSQL.
This article outlines five EF Core query patterns behind many slow pages, plus one habit that catches them all: read the SQL EF generates instead of judging the C# code. It covers N+1 queries, loading whole tables or unneeded columns, cartesian explosions from collection Includes, and filters that prevent index use. It is a practical checklist for anyone writing data access code.