Enterprise D365 Customer Service Reference Architecture
Rijwan Ansari The central thesis: An enterprise Dynamics 365 Customer Service solution should not be designed as an isolated CRM application. It should be designed as a business capability within a wider
Software Design
Copilot-First Development in Action: Building an AI-Powered Applications
Satya Karki There was a time—not very long ago—when building a feature meant sitting down with a well-defined requirement, designing the system upfront, writing code line by line, and hoping that by
Implementing CQRS Without MediatR in .NET 10 Using Clean Architecture
Introduction For years, MediatR has been the de facto standard for implementing CQRS (Command Query Responsibility Segregation) in .NET applications. It provided a clean mediator abstraction, pipeline behaviors, and a
Production-Grade Global Exception Handling in ASP.NET Core — An Architect’s Guide
Exception handling is one of those fundamental aspects of software development that often gets overlooked until something goes wrong in production. In any .NET application, exceptions are inevitable — they
Mastering yield return in C#: A Practical Guide for Modern .NET Developers
In modern enterprise applications, performance and memory efficiency are critical. Whether you're building APIs, processing large datasets, or working with real-time streams, you often need to return sequences of data…
SOLID Principles Explained: From Theory to Practice using C#
There are some essential principles and best practices that are generally recommended to help manage code and projects more easily. These practices make the code easier to maintain, scale, adopt,…
Understanding the Big Ball of Mud in Software Architecture
The concept of the "Big Ball of Mud" in software development was first introduced by Brian Foote and Joseph Yoder in their paper titled "Big Ball of Mud" presented at…