3 ms·
Why reinvent the wheel instead of using the state of the art RSocket protocol? Plus it handle backpressure for free, being reactive.
by The_rationalist 6y ago
Why reinvent the wheel instead of using the state of the art RSocket protocol? Plus it handle backpressure for free, being reactive.
- darksaints 6y agoLikewise, we could ask why Netflix reinvented the wheel, when they could have used the state of the art zeromq library.
- The_rationalist 6y agoWhen I considered a real time communication protocol for our app I remember ruling out zeromq but I don't remember why... Maybe they don't offer an API as clean/expressive? https://github.com/rsocket/rsocket/blob/master/Motivations.md https://github.com/rsocket/rsocket/blob/master/Motivations.m... Or was it backpressure? I wonder what are the pros of zeromq vs rsocket
- ofrzeta 6y agoRecently I researched technologies for "real time web", events , reactive frameworks but this is now the first time I came across RSocket. After reading the FAQ I am still not sure about its value propositions. Also I don't understand how "streaming responses and push" is different from the classic pub/sub model that so many websocket frameworks are offering. I tried to avoid socket.io partially due to irrational preconceptions but then learned that it has a lot of features that are needed in many applications. It's also used by many people and has integrations into virtually every server and client framework.