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
When we configure a cluster of nodes we must verify a bunch of settings that control how the nodes communicate with each other. Nowadays days our cluster will be probably hosted in some cloud network and therefore we must tune these bunch of config settings in order to have our cluster healthy and happy. In… Continue reading Settings for an healthy Event Store cluster
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
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
Clones can be used to add new nodes to an existing EventStore cluster temporary Imagine that we have a classic 3 nodes cluster up and running for ages. Now someone in the business side of the company is asking to add redundancy over a separate Data Center for security reasons in case of catastrophic disaster.… Continue reading The number of nodes in an EventStore cluster is fixed… no it’s not! (Clones and other node roles)
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
“Kubernetes is an open-source container-orchestration system for automating deployment, scaling and management of containerized applications” The goal of this step by step memo is to get a Kubernetes Cluster formed by a Master and 2 or more nodes up and running on AWS using Kops. A) Install Prerequisites Install Kubernetes-cli using chocolately: choco install kubernetes-cli… Continue reading Set up Kubernetes on AWS
Event Store is a database engine that allow no-sql data to be stored as stream of events. The engine is based on a well know distributed algorithm called Paxos In brief, when a write is sent to an Event Store cluster, the master will write the events and replicate them to the other nodes in… Continue reading Event Store and how to avoid Dirty Reads
