EventSourcing.JVM
Java-Quarkus-Reactive-CQRS-EventSourcing
EventSourcing.JVM | Java-Quarkus-Reactive-CQRS-EventSourcing | |
---|---|---|
8 | 1 | |
249 | 19 | |
- | - | |
5.8 | 0.0 | |
17 days ago | almost 2 years ago | |
Java | Java | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
EventSourcing.JVM
- Hitchhiker's Guide to Moving from Relational Data to Events
-
Ensuring uniqueness in Marten event store
EventStoreDB is a good choice if you don’t have to use relational DB. You can check my samples, they could help you in investigation: https://github.com/oskardudycz/EventSourcing.JVM
- Introduction to Event Sourcing in Java - Self-Paced Kit
- How to ensure uniqueness in Event Sourcing
- Simple patterns for events schema versioning
-
Event Sourcing with Spring Boot and EventStoreDB
Data is stored using the regular Spring JPA and ends in the Postgres database (can be any other type if preferred), see base class: https://github.com/oskardudycz/EventSourcing.JVM/blob/main/samples/event-sourcing-esdb-simple/src/main/java/io/eventdriven/ecommerce/core/projections/JPAProjection.java
Java-Quarkus-Reactive-CQRS-EventSourcing
-
Java Quarkus CQRS and EventSourcing microservice example 👋💫✨
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.
What are some alternatives?
emmett - Emmett - a Node.js library taking your event-driven applications back to the future!
gravitee-api-management - Gravitee.io - OpenSource API Management
Quarkus - Quarkus: Supersonic Subatomic Java.
movieland - Full Stack Web App Example including Vue-Nuxt, Spring Boot, Grafana, Loki and Tempo
sourced - Tiny framework for building models with the event sourcing pattern (events and snapshots).
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
cqrs-example - Spring Boot CQRS Example (Docker, Apache Kafka, Zookeeper, MYSQL, MongoDB)
being-samples - Sample projects for using the Being library
hidden-gems - Code sample for hidden gems
postgresql-event-sourcing - A reference implementation of an event-sourced system that uses PostgreSQL as an event store built with Spring Boot. Fork the repository and use it as a template for your projects. Or clone the repository and run end-to-end tests to see how everything works together.
zilla - 🦎 A multi-protocol, event-native proxy. Securely interface web apps, IoT clients, & microservices to Apache Kafka® via declaratively defined, stateless APIs.