26 April, 2013. It was a Friday. In the last few posts on sagas, we looked at a variety of patterns of modeling long-running business transactions. However, the general problem of message routing ...

13 October, 2016. It was a Thursday. A while ago, I blogged about using MediatR to build a processing pipeline for requests in the form of commands and queries in your application. MediatR is a ...

6 February, 2013. It was a Wednesday. In my Scaling Backbone Apps With Marionette talk, I have some slides that deal with JavaScript zombies in Backbone apps. This isn’t a new subject by any means. It ...

22 April, 2014. It was a Tuesday. I’ve been a supporter and user of NHibernate for nearly 10 years. While not part of the original NHibernate Mafia, I’ve long enjoyed NHibernate’s ability to rich, ...

20 June, 2016. It was a Monday. In Part 1 of this 2-part series, I walked through some lessons learned from the first incarnation of our project. The original project I’d still qualify as a success, ...

18 June, 2013. It was a Tuesday. One of the keys to having maintainable tests are to make sure that tests are isolated and reproducible. For unit tests, this is easy as long as we stay away from ...

19 July, 2016. It was a Tuesday. To help those building applications using the new Microsoft DI libraries (used in Orleans, ASP.NET Core, etc.), I pushed out a helper package to register all of your ...

19 April, 2010. It was a Monday. If you’re using Double Dispatch in your code, this may be a symptom of an underlying design issue which may impact the maintainability of your application. Due to the ...

17 February, 2012. It was a Friday. If you write any code in JavaScript then you’ve probably used closures, but do you actually understand what they are and how they work? Taking the time to ...

19 May, 2015. It was a Tuesday. REST, a term that few people understand and fewer know how to implement, has become a blanket term for any sort of Web API. That’s unfortunate, because the underlying ...

In my opinion Command Query Responsibility Segregation (CQRS) is one of the most useful architectural patterns when used in the context of a complex line of business application (LOB). Martin Fowler ...

1 June, 2016. It was a Wednesday. In many of my applications, the UI and API gravitate towards task-oriented UIs. Instead of “editing an invoice”, I “approve an invoice”, with specialized models, ...