How To Use Domain Events To Build Loosely Coupled Systems
Domain events are a Domain-Driven Design tactical pattern for building loosely coupled systems. You raise an event from the domain to record a fact th...
Page 18 of 22. Practical .NET and software architecture lessons.
Domain events are a Domain-Driven Design tactical pattern for building loosely coupled systems. You raise an event from the domain to record a fact th...
Clean code is code that's easy to read, maintain, and understand. It's a skill you can learn with deliberate practice. My favorite way to practice is ...
A client application shouldn't need to know about every service in your system. An API gateway acts as a reverse proxy, accepting API calls and forwar...
Reducing the size of your API responses can noticeably improve performance. Response compression in ASP.NET Core takes two method calls, and in the be...
If you need real-time functionality in .NET, there's one library you will most likely reach for: SignalR. It allows you to push content from your serv...
Is the anemic domain model an antipattern? It works great in simple applications, but with rich business logic the important rules end up scattered al...
The easy way to make HTTP requests in .NET is HttpClient. Unfortunately, it's easy to misuse, and port exhaustion and DNS behavior are some of the mos...
How can you create a recurring background job in .NET? Quartz.NET is a full-featured, open source job scheduling system that can be used from smallest...
Imagine being able to automatically build, test, and deploy your .NET applications with every code change. GitHub Actions are completely free and simp...
One application serves multiple customers, while keeping their data isolated. You can approach multi-tenancy with a single database and logical isolat...
Join 66,000+ readers of The .NET Weekly for practical tips and resources to improve your .NET and software architecture skills.