CQRS.NET 2.0, faster than ever on Azure
Micro Servicing Properly One of the biggest mistake you can make is getting the granularity right for your micro-service. Where most developers go wrong is only thinking about the code, and not the operational resourcing required. By this I mean technical support, ensuring up-time, scaling easily, reconfiguring without recompiling etc. Think like you’re the guy […]
The of the more interesting realisations to make as you travel the CQRS path is that not all event data is equal. One of the simplest examples to help demonstrate this is applying event data to an aggregate. Paint this picture if you will. You have an aggregate, lets call it a Product aggregate. When […]
One of the worst pieces of advise I’ve read recently involved event sourcing… specifically the advise was in relation to performance. So a question you’ll regularly get is “Isn’t event sourcing slow?”. Loading all those events and replaying them to get an aggregate back to it’s current state to make a change to it MUST be slow. […]
When starting to talk about CQRS, there’s a lot of details that CTOs and architects can get bogged down by. One of the easiest way to start the discussions is with very high level concepts, like separating reading (querying) from writing data… allowing the separate systems to be scaled independently of each other.
One of the hardest concepts to learn and then over or come is “How do I query events?” The question in itself shows a disconnect from the concept of what events in an event sourced or CQRS application are there for. In short… you don’t query them, BUT… when you are faced with an architect […]