3 ms·
I'm very excited about this. I've been eying HTTP EventSource for a while now, but there hasn't been a good solution for the backend broker. Kafka is overkill
by luhn 9y ago
I'm very excited about this. I've been eying HTTP EventSource for a while now, but there hasn't been a good solution for the backend broker. Kafka is overkill and Amazon Kinesis' pricing isn't viable if you have lots of topics. This fills the need perfectly and Redis is already part of my stack.
- hakanito 9y agoJust wanted to chip in and say HTTP EventSource has been really nice to work with, we've been using it in production for 1+ year
- bonkabonka 9y agoWhich polyfill do use for IE/Edge?
- rakoo 9y agoI don't know if you've ever looked at it, but CouchDB has had an EventSource endpoint for a long time now (http://docs.couchdb.org/en/2.1.0/api/database/changes.html?highlight=eventsource#db-changes http://docs.couchdb.org/en/2.1.0/api/database/changes.html?h...). CouchDB is extremely easy to install, use and maintain, and there's a number of public providers out there if you don't want to host everything yourself. As a more generic solution, there's also pushpin (http://pushpin.org/ http://pushpin.org/), which is the backend of fanout (https://fanout.io/ https://fanout.io/), so that may also be a nice addition to your stack if you want a more direct redis->clients link
- baileymiller182 9y agoCheck out nchan.io, an nginx module that does everything you need to connected EventSource to redis backed pub/sub.
- denkmoon 9y ago+1, good to see other developers out there using EventSource and nchan. We've been happily using both in production for almost a year now.