Nabeel's Blogs

Designing Resilient .NET Applications: Handling Failures in Distributed Systems Designing Resilient .NET Applications Handling Failures in Distributed Systems Overview: Distributed systems fail by default, not by exception. This article explains how to design resilient .NET applications using proven patterns like retries, circuit breakers, and fallback strategies. You will learn how failures propagate across microservices and how to control them using modern .NET 8 tooling. The focus is on real production systems, not theory. 1. The Reality of Distributed Systems In monoliths, failures are predictable. In distributed systems, failures are inevitable and unpredictable . Network latency, service downtime, partial failures, and cascading outages are normal behavior. Engineering truth: “Everything fails eventually. The only question is whether your system is prepared.” Critical mistake: Assuming services will always respond successfully leads to cascad...

JWT vs Sessions vs Azure AD B2C: Modern Authentication Strategies Explained Choosing the wrong authentication strategy can break scalability, security, and developer velocity. This guide explains how JWT, Sessions, and Azure AD B2C actually behave in production .NET systems. 1. The Authentication Confusion Problem Most developers don’t fail because they lack knowledge. They fail because they copy patterns without understanding trade-offs. Common anti-patterns: Storing JWT in localStorage Building custom session stores Ignoring OAuth/OIDC standards Security principle: Every shortcut in authentication becomes long-term security debt. Reality Check: Authentication is not a feature. It is infrastructure. Treat it like one. 2. JWT Explained (Production Reality) JWT is a stateless authentication mechanism. The server does not store session state. Instead, identity is encoded in a signed token. Structure: Header.Payload.Signature builder.Services.Add...