Error responses are part of an API contract. Still, many systems grow them incidentally: one endpoint returns { "error": "not found" }, another returns an array of validation errors, a gateway adds its own structure and …
Blogbeitrag lesen
.NET 11 adds a small but useful improvement to the built-in observability story: MemoryCache can now publish OpenTelemetry-compatible metrics directly through System.Diagnostics.Metrics. That makes cache behavior visible …
Blogbeitrag lesen
Hono is often associated with Cloudflare Workers and for good reason. Its small routing model, Web Standard API surface and direct fetch integration make it a natural fit for edge runtimes. That association can obscure a …
Blogbeitrag lesen
Azure Cosmos DB has a habit of exposing architectural weaknesses very early. Classic data-access patterns that work perfectly fine with relational databases often become expensive, noisy and operationally awkward once …
Blogbeitrag lesen
Many long-lived .NET repositories did not start with semantic versioning. They grew up with major.minor.build.revision, often set in AssemblyInfo.cs, sometimes mixed with wildcard auto increment, sometimes duplicated …
Blogbeitrag lesen
ASP.NET Core applications are usually released often enough that versioning stops being a documentation concern and turns into delivery infrastructure. Once an application moves through CI, staging, production, …
Blogbeitrag lesen
Desktop software makes versioning visible in a way that web systems often do not. A backend can hide a surprising amount of release machinery behind its platform. A Windows executable cannot. Explorer exposes file …
Blogbeitrag lesen
Versioning stays invisible right up to the point when it fails. A package has to be reissued, a support case depends on one exact binary or staging and production turn out to run artifacts from the same commit that do …
Blogbeitrag lesen
Distributed applications tend to feel straightforward until a real cloud dependency enters the picture. Azure Cosmos DB is a good example. In Azure, the preferred model is usually clear: the application should connect …
Blogbeitrag lesen
MiMo V2.5 is the latest reasoning and coding model from Xiaomi’s AI lab. Xiaomi positions MiMo as a general-purpose reasoning model with particular strength in code generation, structured output and tool calling. In May …
Blogbeitrag lesen