Skip to content

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


Follow @CodeOpinion

Roundup #69: ASP.NET Core Urls & Ports, Tye, Orleans, and Diagnostics

After a bit of a break, the .NET Roundups are back! This week, it’s almost as if Andrew Lock was working on the exact same I was as he had two posts back to back that solved two issues I was having. Incredible timing and as always great content from Andrew. 5 ways to set the URLs for an ASP.NET Core app In this post I show 5 different ways to change which URLs your app listens on. We’ll look at each of these options in more detail below. Link: https://andrewlock.net/5-ways-to-set-the-urls-for-an-aspnetcore-app/ How to automatically choose a free port in ASP.NET… Read More »Roundup #69: ASP.NET Core Urls & Ports, Tye, Orleans, and Diagnostics

Queuing Background Jobs with Coravel

In one of my live streams on my YouTube Channel, I took a look at using Coravel to refactor some code that was sending out an email. Emailing is a good example of something that can be created as a background job that frees up your web application to return a result quicker to the client. Coravel Coravel gives you a zero-configuration queue that runs in-memory to offload long-winded tasks to the background instead of making your users wait for their HTTP request to finish! It’s pretty easy to get started to run background jobs with Coravel in your ASP.NET… Read More »Queuing Background Jobs with Coravel

CQRS: Refactoring Queries without Repositories

This question posted on Twitter (and the subsequent thread) caught my attention. I had to pipe in with my own opinion on having queries without repositories. To summarize, the question is about using Aggregate Roots with an ORM like Entity Framework. Should you eager load all navigation properties or alternatively I guess, use lazy loading? My answer is if you’re only using an aggregate root for commands (to change state) and you generally have a higher read to write ratio, then eager load the navigation properties. As a general rule of thumb. eShopOnWeb I recently heard about eShipOnWeb from Steve… Read More »CQRS: Refactoring Queries without Repositories