NOTE: This is Part 4 of a five-part series in which I detail how a real-world ASP.NET Web API app using the Command-Query Responsibility Segregation and Event Sourcing (CQRS/ES) [https://www.exceptionnotfound.net/pattern-overview-command-query-responsibility-segregation-and-event-sourcing/] patterns and the Redis [http://redis.io/] database might look. Here's Part 1 of
NOTE: This is Part 3 of a five-part series in which I detail how a real-world ASP.NET Web API app using the Command-Query Responsibility Segregation and Event Sourcing (CQRS/ES) [https://www.exceptionnotfound.net/pattern-overview-command-query-responsibility-segregation-and-event-sourcing/] patterns and the Redis [http://redis.io/] database might look. Here's Part 1 of
NOTE: This is Part 2 of a five-part series in which I detail how a real-world ASP.NET Web API app using the Command-Query Responsibility Segregation and Event Sourcing (CQRS/ES) [https://www.exceptionnotfound.net/pattern-overview-command-query-responsibility-segregation-and-event-sourcing/] patterns and the Redis [http://redis.io/] database might look. Here's Part 1 of
A while back I wrote a series of posts in which I built a simple web application that uses the Command-Query Responsibility Segregation and Event Sourcing patterns, as well as ASP.NET [https://www.exceptionnotfound.net/implementing-cqrs-in-net-part-1-architecting-the-application/] . I did this mostly as a way to explore these two difficult patterns,
I've been exploring ASP.NET Core 1.0 [https://www.exceptionnotfound.net/tag/asp-net-core-1-0/] for a little while now, and every step I take reinforces my opinion that Core is going to be a huge step forward for ASP.NET developers. However, in my eagerness to share all the stuff