You could probably piggy back on ActiveRecord::FutureResult to implement this, since the interface would likely be the same.
That being said, my humble opinion after reading this:
- This is a fairly niche need (talking to a DB that has bad latency is generally done as a last resort measure, nobody willingly does this).
- Like
load_async, It’s only applicable if you have independant queries, which further limits the applicability. - It’s quite a lot of extra complexity and code for Active Record (even though a good part could be shared with
load_async) for something that only works with one DB (even though other clients could add support for it too).
Where it could be useful in a more general case is for preloads. We’ve done some testing with using load_async automatically when preloading associations, and the results were mixed, but maybe pipelining would be more interesting there. But again the overwhelming majority of apps talks to databases with a fast LAN connection, so the rountrip is expected to be way under 1ms, so you’d need to pipeline quite a few queries before you see noticeable gains.
All this to say that you should feel free to explore this, but it won’t be easy and the likeliness of it being merged isn’t particularly high.