Event Sourcing · Software Architecture · Software Development

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 Architecture · Software Development

Distributed Architecture 01: The Ingestion

neurons are cells that are specialized to pass signals to individual target cells, and synapses are the means by which they do so https://en.wikipedia.org/wiki/Synapse A Distributed Software Architecture is formed by several parts that communicate with each other through messages. The pipes or protocols used to exchange communication are like synapses in our human neural… Continue reading Distributed Architecture 01: The Ingestion

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