Messing around with backpressure ideas with RxJS: https://gist.github.com/mattpodwysocki/9491326 … Thoughts?
-
-
@strmpnk well, going to the Ruby world with Rx.rb, I wonder what kind of uptake I might find...
1 reply 0 retweets 0 likes -
Replying to @mattpodwysocki
@mattpodwysocki @strmpnk So many more elegant ways to deal with back pressure if you can leverage semantics...1 reply 0 retweets 0 likes -
Replying to @darachennis
@mattpodwysocki @strmpnk For example, if I only ever need to distribute the latest value.. then any queue depth > 1 is wasteful, coalesce.1 reply 0 retweets 0 likes -
Replying to @darachennis
@darachennis @strmpnk I'd agree, we have merge and switch to turn off later notifications, so no queue sizes1 reply 0 retweets 0 likes -
Replying to @mattpodwysocki
@darachennis @strmpnk that said, I'd love your help coming up with more algorithms outside of this naive one, and windowed one1 reply 0 retweets 0 likes -
Replying to @mattpodwysocki
@mattpodwysocki @strmpnk The most useful by far is a pairwise slide with some current/prior predicate check...2 replies 0 retweets 0 likes
@mattpodwysocki @strmpnk Philosophically, there's nothing cheaper than the messages we never distribute. They're free.. forever!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.