Paweł Pacana

I keep forgetting why we haven't merged this. My biggest fear is that this PR sets a new default for new installs and we don't have enough data points from...

Does it assume you always append one event, as in the examples? If it allows many events, does it group them by streams and executes multiple appends — one per...

Thank you for reporting this. I agree than [current Broker implementation](https://github.com/RailsEventStore/rails_event_store/blob/e2c67b5ffe285fe7ce36b1a2833ac73f6c007f45/ruby_event_store/lib/ruby_event_store/broker.rb#L10-L13) is a bit too tied to in-process event handling, which at the moment [prevents dispatching without any subscriber](https://github.com/RailsEventStore/rails_event_store/blob/e2c67b5ffe285fe7ce36b1a2833ac73f6c007f45/ruby_event_store/lib/ruby_event_store/spec/broker_lint.rb#L9-L13). I...

One workaround, until the issue is addressed, is to leverage [subscribe_to_all_events](https://railseventstore.org/docs/v2/subscribe/#subscribe-for-all-event-types). Either by having an empty subscriber of `->{}` to fool Broker and make it route all published events through...

Hi Bert, thank you for bringing this topic. The `RubyEventStore::Projection.from_stream(%w[])` API is quite problematic at the moment. In RES there's global stream (ordered by global id) and there are named...

Let's scope this to reshaping currently available information. It's good to know now what me may add in the future. Thus plan where we can easily expand without changing too...

Presented image is one of possible directions. I'm afraid that stream names and event ids are far too long to be put in the sidebar.

Good catch! JSONClient should definitely be mentioned in the mapping serialization page. Can you please make the necessary adjustment? I'll happily accept the PR.

https://dev.mysql.com/blog-archive/mysql-8-0-1-using-skip-locked-and-nowait-to-handle-hot-rows/

https://github.com/RailsEventStore/rails_event_store/discussions/1147