this article is currently a work in progress. In this post I’m going to discuss the use of Artificial Intelligence (AI) combined with messaging patterns like Event Sourcing and CQRS. AI components can play different roles in different scenarios like pattern recognition, business insights, future predictions and more. Currently I’m more interested in building an… Continue reading Use Generative AI with Commands and Events
This short note is about dealing with “Connection pending send bytes is too large” error while using a Catch-up subscription and connecting to an EventStore database. That error message can appear in the logs when the server drops a client connection. The reason why that happen is most likely that the server is sending too… Continue reading Connection pending send bytes is too large (EventStore error)
I recently published a project that I had in mind for a very long time. It’s called Linker. Here is the source code. It is published as a nuget package so that you can pull in your own app or you can use the example Console app as starting point. With time I will release… Continue reading Cross Data Center Replication with Linker
This post is a condensed excerpt that I use for a tech talk about scaling distributed systems. Kafka is a message broker and Event Store is a database for stream of events. The roles of these tools has been extended and not always with good results. One can be a good simple ingestion tool while… Continue reading Kafka vs Event Store on scaling processing in a messaging architecture
Here is my view implementing business requirements with DDD, Event Sourcing and CQRS. Ingestion Processing CQRS and Data Distribution Applying the same 3 steps for each new requirements let improves time after time the mechanics of each small bubble while it is living in the aquarium of an Event Driven ecosystem along with bigger legacy… Continue reading Distributed Architecture: 3 Steps
In the ingestion phase data went through the front door to enter our domain. In the domain area we want to process the data in case they mean something for our components, ignore them if not relevant or raise exception if the data are relevant but something is not right. In the previous phase, the… Continue reading Distributed Architecture 02: The Processing
neurons are cells that are specialised to pass signals to individual target cells, and synapses are the means by which they do so Introduction Clients need results… synchronously Scale the ingestion channel Using Single or Multiple Input Streams Discover unstructured data Introduction A Distributed Software Architecture is formed by several parts that communicate with each… Continue reading Distributed Architecture 01: The Ingestion
This is a draft public available to get feedback while I’m writing it. It will change day by day in the next coming weeks. In this guide I will go through an E-Commerce scenario in order to show how to combine Publish Subscribe, Event Sourcing and CQRS to build loosely couple Microservices. Our business requirement… Continue reading Event Sourcing Step-by-step
Note: Replication across clusters and nodes is available with Linker After almost 4 month after I joined the EventStore team I’m going to present my first big egg: GeoReplica. This feature has been in the air for a while and it was referred as Multi Master replication. The GeoReplica is distributed as a fully supported… Continue reading Cross DataCenter replication with EventStore
[EDIT] The new official Event Store Helm Chart is now available [EDIT-EDIT] Unfortunately the EventStore team was not willing to support an official Helm Chart and they discontinued it with a bit of non-sense around the need of a data operator. Having a data operator for Kubernetes it’s a good idea as an addition in… Continue reading Set up an EventStore cluster on Kubernetes
