Sunday, August 11, 2019
I used that gem in the past, but I am not in New York City.
-- Just a little of caveat, you are pretty much locked in.
A lot of features of the gem deliberately designed to lock you in.
Take the event linking features for an example. Under the hood, the gem exploits relations of the relational database.
Once you use that feature you are pretty much locked in with a relational database, the choice to scale via sharding is gone too.
(You can shard a relational database, only if you can make a clean cut of relationships, not leaving a single relationship cross a shard boundary. You are forfeiting this choice once you start using "link_to_stream")
And no other tool would work with the data you have because no one else would implement it that way.
Instead of linking the event to the new stream you can simply build a table from multiple streams of events.
And it will work the same way, only this does not lock you in with the gem and leaving the choice open.
Last but not least CQRS can be done without event-sourcing if you use the gem you are forfeit the choice for not storing an event.
There is more than one way to implement the CQRS, and the way suggested by this gem is not a good one IMHO.
But we are Ruby as a community, just because I don't agree with someone doesn't mean it is totally bad.
I just dissatisfied with the choice I made, to use the gem in the past.
And I will simply go my way. (That's how it works.)
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/fcb65ab4-144e-4787-8a88-aff29cd4ad58%40googlegroups.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment