One of the hot topics in Domain Driven Design over the last few years has been the applications of the Event Sourcing and CQRS patterns.In this session we'll go back to basics and examine some of the motivations for event sourcing, and where it may or may not be appropriate to adopt. We'll look at companion pattern of Command-Query Responsibility Segregation, and show some of the benefits which can be derived from adopting both patterns together. We'll also look at some basic implementation patterns.
Every developer needs a set of tools, especially web developers that bend under the pressure of multiple languages, environments, IDEs and what not. One of the most comprehensive tool out there today is Chrome Developer Tools. It contains so many amazing features other than the common ones, and it’s just a shame most developers don’t know about them!
Come to the session to learn about the known and less-known features of Chrome Developer Tools and see how your everyday web development can become easier by just a few simple steps.
When many developers think of Command-Query Responsibility Segregation (CQRS), they envision separate datastores for reads and writes, linked together by some kind of event-based synchronization mechanism. The reality is that for many domains this is overkill, while for others it still doesn’t solve fundamental concurrency issues. Join Udi for a different approach to CQRS – with a nice mix of NoSQL databases thrown in for good measure.
For too long we've lived under the tyranny of n-tier architectures. Building systems with complicated abstractions, needless indirection and more mocks in our tests than a comedy special. But there is a better way - thinking in terms of architectures of vertical slices instead horizontal layers. Once we embrace slices over layers, we open ourselves to a new, simpler architecture, changing how we build, organize and deploy systems.