Saving a lead and then calling Odoo means two writes that can each fail on their own. Anas Amin describes a transactional outbox where the lead and a message describing it commit together, and a Hangfire job delivers the message later. Leased claims, error classification, dead-lettering and idempotent Odoo writes carry the rest of the design.
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.
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.
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.
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.
NimblePros published its Tiles & Tokens sample, which relies on C# 15 unions and closed hierarchies, as a Native AOT binary on the .NET 11 RC1 SDK. The domain and serialization code produced no trimming or AOT warnings, and the native app ran correctly. The publish errors came from a reflection-based converter, an anonymous type and EF Core, which is a useful checklist for anyone planning a Native AOT app.
ServiceStack v10.4 adds db.Explain() to OrmLite, which returns the query plan of a typed query without running it. The Profiling Admin UI also gets a Slowest Queries view where you can explain, analyze and re-run an app's slowest SQL from the browser. Together they make it easier to spot missing indexes.
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.
After six years without a stable release, Dapper FluentMap is maintained again and version 3.6.0 adds nested mappings, property converters, isolated runtimes, analyzers and source generators. The author stresses keeping existing applications working during upgrades. The piece also covers what to check before moving from 2.0.0 and which databases are certified.
A practical guide to configuring Npgsql connection pooling in .NET and sizing pools across multiple application instances so PostgreSQL does not run out of connections. It stresses that pool limits must be calculated for the whole deployment, not a single process.
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.