sourced VS Java-Quarkus-Reactive-CQRS-EventSourcing

This is an event sourcing library in Typescript that also relies on the repository pattern: https://github.com/cloudnativeentrepreneur/sourced. Using the same models you could use a server side repo, such as https://github.com/CloudNativeEntrepreneur/sourced-repo-typeorm to persist to sql dbs, or the mongo repo implementation: https://github.com/mateodelnorte/sourced-repo-mongo, or even use localstorage if you were working in a browser: https://github.com/CloudNativeEntrepreneur/sourced-repo-svelte-local-storage-store all without changing the model the repository serves.

Source code you can find in GitHub repository. The main idea of this project is the implementation of Event Sourcing and CQRS using Java, Quarkus with reactive Vertx, Postgresql and Kafka. Previously have written same articles where implemented the same microservice using Go and EventStoreDB, and Spring,as written before, repeat here, think EventStoreDB is the best choice for event sourcing, but in real life at some projects we usually have business restrictions and for example usage of the EventStoreDB can be not allowed, in this case, think postgres and kafka is good alternative for implementing our own event store. Didn't write in this article about Event Sourcing and CQRS patterns, the best place to read is microservices.io,blog and documentation of this article is very good too, and as written in the previous article, highly recommend Alexey Zimarev "Hands-on Domain-Driven Design with .NET Core" book and also his blog.