3 ms·
While I'm sure someone, somewhere in the world has it, it would be an odd use case where the "heavyweightness" of the run-time configuration interface actually
by jerf 11y ago
While I'm sure someone, somewhere in the world has it, it would be an odd use case where the "heavyweightness" of the run-time configuration interface actually matters to anyone.
And, well, actually, if I had to bet, I'd bet Redis is actually lighter weight than an HTTP request, honestly. HTTP is really quite inefficient for small requests, and requires a massive pile of code to deal with endless, endless corner cases than an application-specific protocol doesn't.
- 15155 11y ago> I'd bet Redis is actually lighter weight than an HTTP request It is. Here's a cool, non-relevant example of one implementing a Redis clone in Haskell (on HN a month or so ago): https://honza.ca/2015/09/building-a-redis-clone-in-haskell https://honza.ca/2015/09/building-a-redis-clone-in-haskell The relevant portion is where they parse the protocol, not bad at all (especially compared to HTTP)
- derefr 11y agoI wouldn't compare Redis pub/sub on a persistent Redis socket to straight HTTP requests; it's more like an HTTP Server-Sent-Event stream, which looks pretty similar at the protocol level.