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
The privacy of the data has been addressed in the early days even before the internet era. There has never been a lack of legislation. The problem is that the legislation has not been much effective to prevent data breaches nor to enforce the rights of individuals in front of companies or governments. Looking at… Continue reading GDPR, Event Sourcing and immutable events
Event Store is a database to store data as events in data streams It allows to implement CQRS and Event Sourcing. It also allows to exchange messages between components using simple Pub/Sub pattern It’s open source and there is a community edition free to use and a commercial license with support as well This article… Continue reading Data ingestion with Logstash and EventStore
And when I speak of the other division of the intelligible, you will understand me to speak of that other sort of knowledge which reason herself attains by the power of dialectic, using the hypotheses not as first principles, but only as hypotheses — that is to say, as steps and points of departure into… Continue reading Domain Driven Design, Event Sourcing and Micro-Services explained for developers
This post is a quick step by step guide on running a single EventStore https://geteventstore.com/ node on a free EC2 micro Aws instance. You can spin up quite easily this in order to start using the EventStore Web console and play with it for testing. In a real scenario, you must set a larger EC2… Continue reading Run EventStore OSS on an EC2 AWS instance
This is an example of an aggregate written in C# following a functional approach similar to what it is possible to achieve with languages like F#, Scala or Clojure. What it IS NOT in the Domain code example: An AggregateBase class An Aggregate Stateful class What it IS in the Domain code example: An Aggregate… Continue reading Functional Domain Driven Design and Event Sourcing example in C#
“Commands have an intent of asking the system to perform an operation where as events are a recording of the action that occurred…” Greg Young, CQRS Documents Pag. 26 In this post I’d like to state something that I’ve just recalled from a Greg Young’s video. When I started creating an aggregate root I often… Continue reading Domain Driven Design: Commands and Events Handlers different responsibilities
“The magic for a developer is doing something cool that no one else can understand” (myself few minutes ago). The first step into this maze of cool messaging terms and tools left me with the feeling that most of them are not really relevant. After years of studying and practising, all these messaging and service… Continue reading CQRS WITH EVENT SOURCING USING EasynetQ, EVENT STORE, ELASTIC SEARCH, ANGULARJS AND ASP.NET MVC
You must be logged in to post a comment.