emmett
EventSourcing.JVM
| emmett | EventSourcing.JVM | |
|---|---|---|
| 1 | 8 | |
| 119 | 249 | |
| 16.0% | - | |
| 9.3 | 5.8 | |
| 17 days ago | 11 days ago | |
| TypeScript | 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.
emmett
-
Ensuring uniqueness in Marten event store
I thought about that, and my current conclusion is that maintaining two codebases would be a no-go without having some sponsorship. The option that I come up with is: - exposing Marten methods through some HTTP/gRPC protocol and packing into "server". - Projection could be defined with some web assembly to enable multiple languages to define them. Have you tried Axon? It supports Postgres, but of course, it's a bit different idea and foundations than Marten. Some of those crazy ideas I'm going to test with Emmett https://github.com/oskardudycz/emmett. But it'll be based on Node.js and TypeScript.
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
What are some alternatives?
booster - Software development framework specialized in building highly scalable microservices with CQRS and Event-Sourcing. It uses the semantics of the code to build a fully working GraphQL API that supports real-time subscriptions.
Java-Quarkus-Reactive-CQRS-EventSourcing - Java-Quarkus-Reactive-CQRS-EventSourcing
ddd-hexagonal-cqrs-es-eda - Complete working example of using Domain Driven Design (DDD), Hexagonal Architecture, CQRS, Event Sourcing (ES), Event Driven Architecture (EDA), Behaviour Driven Development (BDD) using TypeScript and NestJS. Like what you see? Don't forget to star! ⭐ ^^^
evtstore - Event Sourcing and CQRS with Node.js and TypeScript
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.