Event Sourcing · Software Architecture

Kafka vs Event Store on scaling processing in a messaging architecture

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

Domain Driven Design · Event Sourcing · Software Architecture

Distributed Architecture 02: The Processing

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

Software Development

Persistent Subscriptions Status in Event Store UI

Given that you are using Event Store Persistent SubscriptionsWhen your clients publish messages to streamsThen the UI shows a Red flag even if the messages are handled The setting MinimumCheckPointCountOf https://eventstore.org/docs/dotnet-api/competing-consumers/index.html#persistent-subscription-settings can determine the ‘Status # of msgs’ on the Persistent Subscriptions UI View. The default value of this setting is 10. When a checkpoint… Continue reading Persistent Subscriptions Status in Event Store UI

Event Sourcing · Software Development

Set up an EventStore cluster on Kubernetes

[EDIT] The new official Event Store Helm Chart is now available This is my step by step memo on setting up an EventStore cluster with persistent volumes on Kubernetes hosted in AWS. The open-source, functional database with Complex Event Processing This guide assumes that you already have a Kubernetes Cluster up and running and you have… Continue reading Set up an EventStore cluster on Kubernetes