Re:Scientist: A Ruby library for carefully refactoring criti...
by jauco on Sunday November 10, 2019 @01:06PM
(#21499220)
There’s goreplay[0]. But once you start using that you quickly find that many parts of your app use random data (such as uuids) or clock data (timestamps etc) getting these synced between prod and replay or ignored on replay is quite a hassle.
Re:Scientist: A Ruby library for carefully refactoring criti...
by dyeje on Sunday November 10, 2019 @09:52AM
(#21498130)
They wrote a good blog post about using this gem back in 2016: https://github.blog/2016-02-03-scientist/
Re:Scientist: A Ruby library for carefully refactoring criti...
by FrancoisBosun on Sunday November 10, 2019 @09:10AM
(#21497997)
Maybe because of the large increase in complexity?
Re:Scientist: A Ruby library for carefully refactoring criti...
by hamandcheese on Sunday November 10, 2019 @03:24PM
(#21499969)
Another possibility might be to do the side effects in a transaction that gets rolled back?
I always feel that it would be great to be able to do this with code that has side-effects (eg. anything that changes the database) but I've never seen a general purpose solution for this. The README mentions using a write replica, but how do you deal with data drifting in case of bad writes?