Tags Overview for All Blog Topics

The cloud is not a deployment target. It is a different operating model with different identity primitives, a different cost model, and a different definition of what “available” means. Articles tagged here focus on the platform-specific decisions — Azure managed services, identity federation, regional design, billing — that decide whether a workload behaves like a cloud system or like a lift-and-shift that happens to run in someone else’s data centre.

Cloud-native is the part of a system that survives a node restart, a region failover, and a container image swap without anyone logging into a server. The label gets attached to a lot of architectures that fail at least one of those tests. The articles here treat cloud-native less as a marketing category and more as a set of properties — declarative configuration, externalized state, replaceable instances, observable behavior — that a .NET workload either has or does not have.

“Quality” is the word teams reach for when a codebase frustrates them and nobody wants to argue about specifics. The articles in this collection try to put specifics back: which metric actually predicts maintainability, which Clean Code rule survives contact with a real change request, which analyzer warning is signal and which is decoration. Quality without a measurement attached is taste, and taste does not survive a team rotation.