postgresql-event-sourcing
commanded
| postgresql-event-sourcing | commanded | |
|---|---|---|
| 4 | 4 | |
| 968 | 1,791 | |
| - | 0.7% | |
| 5.3 | 7.9 | |
| 6 months ago | 3 months ago | |
| Java | Elixir | |
| Apache License 2.0 | 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.
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...>
commanded
-
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store
This reminds me of Commanded[0] for elixir which also uses Postgresql by default.
[0]https://github.com/commanded/commanded
-
Adding soft delete to a Phoenix Commanded (CQRS) API
So, I lied told a half-truth about aggregates. They are not hydrated in-memory for every command / event. In reality, aggregates are implemented with GenServer each caching their state and being managed under the commanded application's supervision tree (ultimately by a DynamicSupervisor called Commanded.Aggregates.Supervisor, to be specific).
-
Using CQRS in a simple Phoenix API with Commanded
The Commanded hex package is a fabulous CQRS library used by some real companies in production, but it doesn't have a great on-ramp.
-
Phoenix LiveView, but event-sourced
The context: I'm building a cryptocurrency exchange application. I don't have the business chops to run an actual exchange, so this is just for fun. The application is built in Elixir, using the Commanded framework for CQRS/ES goodness, and Phoenix LiveView because it's the hot new thing that I wanted to learn.
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.
ex_admin - ExAdmin is an auto administration package for Elixir and the Phoenix Framework
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.
graphql_parser - Elixir binding for libgraphqlparser
Java-Spring-CRQS-Eventsourcing-Microservice - Java-Spring-CRQS-Eventsourcing-Microservice
plug - Compose web applications with functions
txid-syncing - Demo of continuous syncing based on txids
plug_cloudflare - Parses CloudFlare's CF-Connecting-IP header into Plug.Conn's remote_ip field.
emmett - Emmett - a Node.js library taking your event-driven applications back to the future!
phoenix_live_reload - Provides live-reload functionality for Phoenix
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.
torch - A rapid admin generator for Elixir & Phoenix