CQRS Tech Talk Slides
Slides from my CQRS Tech Talk @ Hackforge. Command Query Responsibility Segregation (CQRS) from Derek Comartin
Sponsor: Using RabbitMQ or Azure Service Bus in your .NET systems? Well, you could just use their SDKs and roll your own serialization, routing, outbox, retries, and telemetry. I mean, seriously, how hard could it be?
Derek Comartin
CAP Theorem, CQRS and Eventually Consistent
First, if you haven’t heard of Eric Brewer’s CAP theorem, it basically states that you can must choose two of three: Consistency Availability Partition Tolerance CQRS doesn’t solve CAP issues, however it allows you to decide independently what is important on both read and write side. For example, you could assume a systems would be ACID (Atomic, Consistent, Isolated, Durable) compliant on the write/domain site and BASE (Basic Availability, Soft-State, Eventually Consistent) on the read side. Eventual consistency is something that requires a change of mindset. Because of our heavy use in ACID compliant databases, thinking about possibly having stale data blows our mind. There… Read More »CAP Theorem, CQRS and Eventually Consistent
Greg Young: 8 Lines of Code
Greg Young gave a good talk titled 8 Lines of Code, discussing simplicity, dependencies, and magic. Magic is always something I try and identify and stay away from in my own code, however I really failed to realize how much magic goes on in some of the libraries/frameworks that I often use. Entity Framework and nHibernate come to mind. You really should understand the magic happening in these libraries to use them. Which is very problematic. If you take the dependency ownership seriously, then a lot of folks developing the front-end of a “modern” web applications are in a world of… Read More »Greg Young: 8 Lines of Code