postgresql-event-sourcing
Java-Quarkus-Reactive-CQRS-EventSourcing
| postgresql-event-sourcing | Java-Quarkus-Reactive-CQRS-EventSourcing | |
|---|---|---|
| 4 | 1 | |
| 968 | 19 | |
| - | - | |
| 5.3 | 0.0 | |
| 6 months ago | almost 2 years ago | |
| Java | Java | |
| Apache License 2.0 | - |
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.
postgresql-event-sourcing
-
Hitchhiker's Guide to Moving from Relational Data to Events
This is an extremely well documented postgresql event sourcing reference implementation: https://github.com/eugene-khyst/postgresql-event-sourcing
-
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store
Here is the code <https://github.com/eugene-khyst/postgresql-event-sourcing/bl...>
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?
ksqldb-event-souring - Kafka is not for event sourcing, isn't it? Kafka alone is not an event store, but Kafka and ksqlDB together allow building full-featured event stores. This repository provides a sample of event sourced system that uses Kafka and ksqlDB as event store.
gravitee-api-management - Gravitee.io - OpenSource API Management
sirix - SirixDB is an an embeddable, bitemporal, append-only database system and event store, storing immutable lightweight snapshots. It keeps the full history of each resource. Every commit stores a space-efficient snapshot through structural sharing. It is log-structured and never overwrites data. SirixDB uses a novel page-level versioning approach.
Quarkus - Quarkus: Supersonic Subatomic Java.
Java-Spring-CRQS-Eventsourcing-Microservice - Java-Spring-CRQS-Eventsourcing-Microservice
movieland - Full Stack Web App Example including Vue-Nuxt, Spring Boot, Grafana, Loki and Tempo
txid-syncing - Demo of continuous syncing based on txids
sourced - Tiny framework for building models with the event sourcing pattern (events and snapshots).
emmett - Emmett - a Node.js library taking your event-driven applications back to the future!
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
eventstoredb-event-sourcing - EventStoreDB is the database for Event Sourcing. This repository provides a sample of event sourced system that uses EventStoreDB as event store.
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.