redis-rb

Thanks Mitchell (big fan, btw!). Indeed!https://github.com/hashicorp/vagrant/blob/main/lib/vagrant/a... Yes, it's not a new pattern by any means, and there's many ways to "halt" the pipeline as you say. For example ActiveRecord stops callback chains if any callback throws ":halt". Other examples are Redis.rb's pipelining API https://github.com/redis/redis-rb?tab=readme-ov-file#pipelin... Or more generally any builder-style pattern that composes a set of operations for later execution, including again ActiveRecord's query chaining. In my article I tried to show a specific implementation using the Railway pattern (where the result must only respond to "#continue?() => Boolean")

You're right the general client doesn't have the stack support yet. https://github.com/redis/redis-rb. But, each capability (like Graph) has its own dedicated client. Which capability do you care about? e.g. for JSON you can use https://github.com/vachhanihpavan/rejson-rb.

you might be running into max connection issues because your library is leaving stale connections. i know this is the case for ruby & php. check if you have timeout set. see this github issue for ruby: https://github.com/redis/redis-rb/issues/524

Keep in mind that part of what makes reading code beneficial is that it's not necessarily easy- in fact, it's often rather hard! The benefit is developing a set of "mental heuristics" to figure out what parts of a codebase are useful, so that when you have to dig through someone else's code you can figure it out just a little bit faster. That said, here are a couple suggestions. I'm not sure what you use other than C# (and Javascript?) so I'm just gonna link things from several languages. redis-rb [1] is the 'official' Ruby client for redis. (For that matter, I've always heard that redis itself [2] is a good example of C code.) React's source [3] is rather difficult to figure out, but the team recently released a codebase overview [4] which might help. Alternatively, preact [5] is relatively straightforward, and IMO is a good example of s

I'm not the best person to answer about bootstrap on our team, but I'll ask my colleague to add a comment about this later. Redis is fantastic. Perhaps I should also mention we use ohm as an ORM, which is very neat. I wouldn't dream managing our particular app without it. But it's not exactly fire-and-forget. Firstly, modelling your data is very important, or you can end up with lots of stuff taking precious memory. Secondly, whilst performance is great, it's still not 'transparent' like accessing a variable in memory. If you have lots of small redis queries, they do add up eventually. This is getting very detailed, but you might want to check out this as an example (specific to the ruby version it seems): https://github.com/redis/redis-rb/issues/283 Hope this helps, but feel free to get in contact.