A library for publishing, consuming, storing and retrieving events. It's your best companion for going with an event-driven architecture for your Rails app.
🐎 If you're into free performance improvements you'll love our latest release:
https://t.co/OQmfuXafXk
In short — there's less SQL queries when reading a batch of events. And also one batch less needed to read a stream.
High five to @pjurewicz93 for delivering this!
In this video we did an introduction to EventSourcing and explained how it differs from snapshot approach.
Also, we talked about temporal tables vs EventSourcing approach and why one could be better than the other.
We'll appreciate feedback!
#eventsourcing@RailsEventStore
@qaztrewqaz Not really. And event can be appended only once. Publish is append + pubsub.
Appended event can be later linked to some other streams but it does not involve pubsub again.
🚀 #RailsEvenStore v2.12.0 has been released!
🆕 Support for PostGIS & Trilogy adapters
🆕 ActiveJob::ConfiguredJob & Sidekiq::Job::Setter are valid event handlers
🐛 Fixed #Rspec publish matcher in combination with in_streams
And more:
https://t.co/gwyVxpjDoo
#RubyOnRails 7.1 will bring new database adapter for #MySQL called Trilogy.
And guess what? #RailsEvenStore's trunk already supports and it will be included in the next release!
Learn more on how we improved code to add new adapter support with ease👇
Discover how the underutilized Value Object pattern can transform your codebase💡
Simplified, cleaner code 🧹
Easier, more focused testing 🎯
Hassle–free feature additions 🪄
🔗 Learn more: https://t.co/fXkvKQJZKJ
#Ruby#ValueObject#CleanCode
Pssst, hey, kid, wanna new #RailsEventStore?
2.11.0 is out!
– PreserveTypes transformation is reliable when stored data shape is different than its original
– You can use OpenStruct for data and metadata OOTB if you're running JSONClient
– Details: https://t.co/wnYpLBMw0F
#RailsEventStore 2.10 is out! In the new version you'll find support for #mysql json columns for event data and metadata.
Also, `JSONClient` has been fixed and now handles the mapper argument correctly.
Read more at https://t.co/4PK2CMooSH
Serializing data with JSON can lead to loss of information about original data types. Unless they are: string, number, boolean, null or structured types like object or array. Why this was a challenge in #RailsEventStore and how we’ve faced it: https://t.co/WUtTDNbS6N
If you're using RES with Postgres (or planning to) this is a must-read.
In RES 2.9.0 we simplified the configuration of RES. We also brought JSONClient to life 👇
https://t.co/U5eI0hHN9J
If you're using EventSourcing, you already have the events in house.
EventSourcing is advertised with the ability to replay events. Rightly so.
One might ask, how to do that using @RailsEventStore?
Rushing to explain!
Nobody expected #RailsEventStore 2.9.0!
Setup can be hard for newcomers, we decided to make it easier than ever by:
– giving https://t.co/MbNkPn3gyk magic skills
– tailoring RailsEventStore::JSONClient for PgSQL with json(b)
– refereshing install docs https://t.co/Gh5Wr86mQl