A few years ago when I was I was just learning about CQRS and Event Sourcing I read the transcript of a fantastic talk by Martin Kleppman called Turning the Database Inside Out with Apache Samza (https://www.confluent.io/blog/turning-the-database-inside-out-with-apache-samza/). At the time I found it mind blowing, and actually still do several years later. I recommend reading or watching Martin’s content on this subject. In this article I would like to summarize my understanding of his points and make the case that what Martin describes is a description of the CQRS/Event Sourcing view of the world described from a database perspective.
Managing state of Microsoft Orleans Virtual Actors with Event Store
We made it! Event Store Cloud is now in Early Access. In this post, we will share some information about what we have built and what decisions allowed us to execute at a rapid pace with a small team.
In the latest version of EventStoreDB we brought out a new feature, server-side filtering. This feature allows you to pass a filter when querying EventStoreDB so that it will only return events that you asked for.
CQRS stands for _Command-Query Segregation Principle_. Greg Young described (and named) the pattern thoroughly in 2010, but the idea existed way before that time
EventStorming has been revolutionary in the world of Domain-Driven Design. No technique has enabled domain experts and software engineering teams to collaborate so effectively at building and sharing a rich domain understanding.
Event Sourcing is an alternative way to persist data. In contrast with state-oriented persistence that only keeps the latest version of the entity state, Event Sourcing stores each state mutation as a separate record called an event.
Event Sourcing can bring your business a lot of benefits, but how do you convince senior staff that it's worth it?
Due to the recent increase in popularity of Kubernetes and its excellence for the hosting and orchestration of stateless workloads, we regularly encounter the request to expound upon Event Store’s suitability for deployment via the purported king of cluster schedulers. To summarize, we recommend for reasons we will describe that, to get the most out of your Event Store database deployment, Event Store is deployed via native packages to bare metal systems or isolated virtual machines.
VME Retail have released version 1.0.0 of their Subscription Service, which is intended to make life that little bit easier for delivering events from EventStoreDB to clients. The Subscription Service has been used privately by VME Retail Ltd for a few years in various solutions, and they have decided to open the code up to the rest of the Event Store community.