The Azure Cosmos DB Change Feed Processor spreads change processing across several .NET workers using a lease container for ownership and checkpoints. The article walks through the setup in the .NET SDK and explains when adding workers actually helps. It also covers why downstream operations must be idempotent, since changes can be delivered again after a failure.
The author compares Vertical Slice and Clean Architecture on the same Product API in .NET 10, counting the files each layout touches for one new feature. He then presents a hybrid layout that keeps the Domain project, drops the Application project, and groups endpoints by feature. It is a practical reference for teams deciding how to structure a Web API.
Microsoft Fabric IQ is a new Fabric workload that maps OneLake tables, Power BI semantic models and real-time Eventhouse streams to shared business entities. Its Ontology item, currently in preview, lets Fabric Data Agents and Operations Agents work with business concepts instead of raw schemas. Read on if you are deciding whether to model business meaning before connecting LLMs to your data.
The author shows a multi-tenancy pattern for ASP.NET Core and EF Core that uses global query filters so each request only sees its own tenant's rows. When no tenant is set, filtered queries return nothing, which fails closed. The post also covers tenant-scoped unique indexes, limiting IgnoreQueryFilters(), and an integration test that checks cross-tenant access. It is a practical starting point for SaaS backends.
JasperFx rewrote the Wolverine best practices guide from scratch, replacing the 2023 version. The new guide centers on the A-Frame Architecture and gives concrete advice on splitting handlers, error handling, and at-least-once messaging rules. It is a practical reference for .NET teams building messaging systems with Wolverine.
Mauro Servienti examines how strongly typed view models in ServiceComposer can reintroduce the coupling that ViewModel Composition is meant to remove. He proposes per-service interfaces for response models and per-service request models for decomposition, and discusses a DispatchProxy idea that would drop the concrete class. Read on for the trade-offs and deployment caveats, including property name collisions.
This tutorial shows how to grow a single LLM call into a production-ready AI feature on ASP.NET Core. It covers authentication, retrieval-augmented generation, security and failure handling. It is a practical roadmap for .NET developers who want the model to stay a replaceable dependency inside their application.
Axia is an open-source .NET 10 web console and REST API for Active Directory and OpenLDAP. Its author explains why half of the initial DDD design was dropped after several security reviews. The article covers what paid off, including value objects, ports and adapters, and architecture tests, and what was replaced, such as domain-event auditing.
Jeremy D. Miller explains how to read your own writes in event-sourced systems that use async projections in Marten. Switching from FetchLatest to ProjectLatest removes an extra database round trip by reusing pending events in the session. Wolverine's UpdatedAggregate type then lets HTTP endpoints and message handlers return the current aggregate with less code.
MauiReactor is a library that brings the MVU (Model-View-Update) pattern to .NET MAUI, letting you define UI in fluent C# without XAML or bindings. This article builds a habit tracker step by step, covering stateful components, [Prop] parameters for child components and how SetState triggers re-rendering. It is a useful starting point for developers curious about a reactive alternative to MVVM, keeping in mind the library is not officially supported by the .NET MAUI team.
Part 5 of Scott Galloway's series packages the recommendation and intervention ideas from earlier parts into Mostlylucid.Relevance, a framework that runs inside the application process and keeps its state in SQLite. It can serve several isolated domains at once, and an optional native package adds an HNSW vector index. The package also ships an AGENTS.md guide describing extension points and invariants for developers and their coding assistants.
This guide shows how to combine FusionCache's in-process L1 memory with a shared Redis L2 layer in a product catalog API. The author keeps Clean Architecture boundaries intact and focuses on correct cache behavior rather than raw speed numbers. It is a practical starting point for developers who run several instances and need to plan freshness and invalidation.