https://github.com/Pragmatists/eventsourcing-java-example

A simplified (in memory) example of Event Sourcing implementation for banking domain.
https://github.com/Pragmatists/eventsourcing-java-example

ddd ddd-sample event-sourcing

Last synced: 2 months ago
JSON representation

A simplified (in memory) example of Event Sourcing implementation for banking domain.

• Host: GitHub
• URL: https://github.com/Pragmatists/eventsourcing-java-example
• Owner: Pragmatists
• Created: 2017-03-29T18:27:11.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2017-05-16T12:16:16.000Z (over 7 years ago)
• Last Synced: 2024-05-07T02:32:36.012Z (8 months ago)
• Topics: ddd, ddd-sample, event-sourcing
• Language: Java
• Homepage:
• Size: 628 KB
• Stars: 95
• Watchers: 11
• Forks: 42
• Open Issues: 4
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-ccamel - Pragmatists/eventsourcing-java-example - A simplified (in memory) example of Event Sourcing implementation for banking domain. (Java)

README

        
# Event sourcing example in Java

A simplified (in memory) example of Event Sourcing implementation in Java for banking domain.

Repository is splitted into exercises adding step by step more functionality towards good design of event sourcing with CQRS.

You can play around and try to implement exercises or You can check out solution branches.

## Step 1 - In memory iplementation of event sourcing

![alt tag](https://raw.githubusercontent.com/michal-lipski/eventsourcing-example/master/event_store_exercise_1.png)

- Provide simple in-memory implementation of Event Store

- Make all test passing using event sourcing

#### soultion

 - branch [exercise_1_solution](https://github.com/michal-lipski/eventsourcing-example/tree/excercise_1_solution)

## Step 1a (optional) - Unit of work pattern

- Implement [Unit of Work](https://martinfowler.com/eaaCatalog/unitOfWork.html) pattern where events are stored outside of aggregate

#### soultion

 - WIP

## Step 1b (optional) - Projections

- Implement Projections on Account to get number of transactions performed on account

- eventStore.store() method shoud accept Event playload instead of domain Events

- what should be api of eventStream()?

#### soultion

 - WIP

 

## Step 2 (optional) - Optimistic locking

- add optimistic locking

#### soultion

 - WIP

 

## Step 3 - new Aggregate extraction

![alt tag](https://raw.githubusercontent.com/michal-lipski/eventsourcing-example/master/event_store_exercise_2.png)

- Refactor to move all money transfer related stuff to separate aggregate

- New aggregate will be also using Event Store

#### soultion

 - WIP

 

## Step 4 - adding CQRS

![alt tag](https://raw.githubusercontent.com/michal-lipski/eventsourcing-example/master/event_store_exercise_3.png)

- Apply CQRS rule and separate the command and reading side

- Solution will use Eventual Consistency approach

#### soultion

 - WIP

 

## Step 5

- Provide additional (not transient) implementation of Event Store. (https://geteventstore.com/)

#### soultion

 - WIP