Category: .NET & Architecture

“In progress” is doing a lot of work. Show meaningful status, make decisions clear and enforce access on the server, and keep the next step when things pause.

.NET 10 is a long-term support release. Map what you depend on, check licences as well as versions and prove the business workflows before you release.

Passkeys can make sign-in easier and phishing-resistant. Explain them plainly, test the second device and treat account recovery as a first-class journey.

When a library like AutoMapper or MediatR changes its licence, find out what you really use, separate the library from the idea and choose to pay, wait or replace.

Laravel and .NET are both credible for custom business systems. Compare integrations, team continuity, maintainability and the whole support path first.

.NET 9 brings runtime and tooling improvements. Separate the runtime decision from feature experiments and weigh support windows and testing effort.

Sometimes an app keeps asking the same expensive question. Decide what deserves caching and agree how old is too old before you buy more capacity.

A fast speed-test score doesn’t mean filters, bookings or checkouts feel fast. Find the delays people feel and measure the journeys they complain about.

Before adding more cloud services, name the dependencies, check what health checks really check and follow a delay across the boundaries.

Before splitting a small business app into services, consider a modular monolith: clear boundaries inside one deployment, without the network overhead.

A faster .NET 8 runtime only matters when customers feel it. How to baseline real journeys, check correctness and decide when an upgrade earns its cost.