Architecture

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

I’m excited to announce the Loosely Coupled Show, a new project I’m working on with James Hickey. Check out the YouTube Channel and subscribe! The premise is simple. To have discussions about software architecture and design. The target audience is intermediate to senior software developers. Episode #000 We recorded a quick video to kind of describe what the plan is for the show, check out our “first” episode for more about the show and us and our backgrounds. Loosely Coupled Show I’ve also posted a short video on my CodeOpinion YouTube channel to elaborate a bit more on the announcement,… Read More »Loosely Coupled Show: Software Architecture and Design

For many years now I’ve advocated not using the repository pattern on top of an ORM such as Entity Framework. There are many reasons why that I’ll try and cover throughout this post based on ways that I’ve seen it implemented. Meaning, this post is talking about poorly implemented approaches or pitfalls that I’ve seen. To clarify, since this topic seems to really fire people up, I’m not saying that you shouldn’t use the repository pattern. I’m going to clarify why I don’t think under certain situations it’s very useful and other situations that I do find it useful. This… Read More »Avoiding the Repository Pattern with an ORM