postgresql-event-sourcing
emmett
| postgresql-event-sourcing | emmett | |
|---|---|---|
| 4 | 1 | |
| 968 | 117 | |
| - | 14.5% | |
| 5.3 | 9.3 | |
| 6 months ago | 12 days ago | |
| Java | TypeScript | |
| 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...>
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.
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.
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.
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.
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! ⭐ ^^^
Java-Spring-CRQS-Eventsourcing-Microservice - Java-Spring-CRQS-Eventsourcing-Microservice
evtstore - Event Sourcing and CQRS with Node.js and TypeScript
txid-syncing - Demo of continuous syncing based on txids
EventSourcing.JVM - Examples and Tutorials of Event Sourcing in JVM languages
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.
message-db - Microservice native message and event store for Postgres
thalo - An Event Sourcing runtime with WebAssembly & embedded event store
Java-Quarkus-Reactive-CQRS-EventSourcing - Java-Quarkus-Reactive-CQRS-EventSourcing