postgresql-event-sourcing
thalo
| postgresql-event-sourcing | thalo | |
|---|---|---|
| 4 | 7 | |
| 968 | 625 | |
| - | 0.8% | |
| 5.3 | 8.5 | |
| 6 months ago | 3 months ago | |
| Java | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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...>
thalo
-
Thalo - Event Sourcing runtime for WASM
Thalo is a new Rust library that provides a runtime for WASM-based event sourcing. With Thalo, developers can compile their aggregates and components into WASM modules and use them in the runtime to handle commands and persist events to an event store. The library is built on top of Wasmtime and Message DB, and uses the ESDL schema language to define aggregates. While Thalo is not yet ready for real-world use, it has the potential to make event sourcing more accessible to a wider range of languages that compile to WASM, allowing for a language-agnostic runtime. Give it a try and let us know what you think! https://github.com/thalo-rs/thalo
Over the past couple of months I've rewritten a project of mine from scratch called Thalo. https://github.com/thalo-rs/thalo
- Thalo – Rust event sourcing framework
-
Thalo.rs - Event Sourcing in Rust
Interesting! Thanks for sharing. I can see how macros can be heavy, but yours was pretty light IMO. Comparing with the current example, the current one has basically the same code, plus the edsl code that looks like a header (if Rust ever had C's .h or OCaml's .mli files). Which isn't necessarily a bad thing though.
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.
Airline-Microservices - Airline Microservice is a simple Airline application for online reserving flight ticket. This application based on different software architecture and technologies like .Net Core, CQRS, DDD, Vertical Slice Architecture, Docker, kubernetes, tye, masstransit, RabbitMQ, Grpc, yarp reverse proxy, Identity Server, Redis, SqlServer, Entity Framework Core, Event Sourcing and different level of testing.
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.
eventually-rs - Event Sourcing for Rust
Java-Spring-CRQS-Eventsourcing-Microservice - Java-Spring-CRQS-Eventsourcing-Microservice
PumpkinDB - Immutable Ordered Key-Value Database Engine
txid-syncing - Demo of continuous syncing based on txids
esdl - Event-sourcing Schema Definition Language
emmett - Emmett - a Node.js library taking your event-driven applications back to the future!
esdl-vscode - VSCode Language Syntax for ESDL
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.
Rails Event Store - A Ruby implementation of an Event Store based on Active Record