rails_event_store
rails_event_store copied to clipboard
RailsEventStore
A Ruby implementation of an Event Store based on Active Record
RubyEventStore::Projection does not yield events in deterministic order when using multiple streams
Given I have some events in my database: ``` {id: 1, data: {...}, timestamp: "2023-01-19Z01:01:01"} on stream "A" {id: 2, data: {...}, timestamp: "2023-01-19Z01:01:02"} on stream "B" {id: 3, data:...
- https://arkency.slack.com/archives/C7B95EW3V/p1669453490523099 - https://arkency.slack.com/archives/C7B95EW3V/p1619529649198000 PR: https://github.com/RailsEventStore/rails_event_store/pull/1463
- [x] make `Repository` possible to be build without `database_url`, for producer purposes - [x] add `Repository#insert_record` or similar to use it in producers - [x] use `Repository#insert_record` in `SidekiqProducer`...
Creating an issue for something to track before 3.0. I'm not sure it makes sense to start working on the code before we decide we want to finally go into...
 Make inspecting an event a pleasant experience for a developer debugging the system. Current iteration of this page is suboptimal: - event data can be very long and pushes...
If it's available, it can be worth it to store commit ID (or "transaction id") in event's metadata, in order to know which events were published in one transaction, as...
We could use railtie server block so that outbox starts automatically when rails application starts in developer environment. https://github.com/rails/rails/commit/868866c1fd7f6c79fd48d90febb1fd02a83380e1
AFAICT this is not referenced anywhere in the gem, and we (currently) don't plan to use it, so it would be nice to not need to install it.
Metadata
Owner
Metadata
A Ruby implementation of an Event Store based on Active Record