JiraSample-EventSourcing

Learn & understand EventSourcing by creating a simple Jira like demo application

This project

• Provides 2 set of APIs: Read/command & Write, in turn 2 different set of read & write db
• JiraSample.Api uses
  • Events to capture each actions performed on domain entity(Jira Item in this case)
  • Stores the events on MongoDb based EventStore.
  • Publishes events to Kafka
• JiraSample.Query.Api
  • Uses projections to provide different set of read options.
  • Subscribes to events of Kafka
  • Stores read projections on MS Sql
• It also uses Clean Architecture on both read & write side.
• This project showcases few important concepts:
  • Event Sourcing
  • Event Driven Architecture
  • Choreography microservice pattern
  • Clean Architecture
  • Domain Driven Design

---

ToDo List:

• How to run Guide
  • Run docker compose up -d in root folder to run all the services
  • Web UI can be accessed at http://localhost:5005/
  • Auth, Command and query service can be found at ports 5004, 5002 & 5003
• Docker Support (one docker compose to run all dependencies) [Done]
• Add a frontend ui for demo purpose [InProgress]
  • Basic Crud based Ui is done
  • Proper css, layout, navbar etc to be added
  • logout to be added
• Add
  • Authentication [Created a demo auth/identity service which stores user/token in in-memory db] [done]
  • Mapping(Mapster)
  • Db Migration & seeding logic
  • Unit tests
• Improve
  • Exception Handling
  • Validation logic
• Fix
  • Parent - Child(ren) Mapping
  • option-config in respective dependency classes