Re:Video Streaming with RethinkDB Changefeeds
by StavrosK on Saturday March 21, 2015 @12:11PM
(#9243118)
I read the changefeeds post, but I don't think I understood exactly what they're for. Would clients be talking directly to the database, or would a persistent app worker block on database updates and then send this to the client?
[ Parent
| on HN ]
Re:Video Streaming with RethinkDB Changefeeds
by segphault on Saturday March 21, 2015 @01:09PM
(#9243358)
In a more conventional usage scenario, your application is responsible for picking up updates from the changefeed.
You can see an example here of a node.js app using a changefeed to convey updates to the frontend through Socket.io: http://rethinkdb.com/blog/realtime-cluster-monitoring/
Though, of course, you can also build things other than web apps. Here's a simple IRC bot built with Go that also uses RethinkDB changefeeds: http://rethinkdb.com/blog/go-irc-bot/
Re:Video Streaming with RethinkDB Changefeeds
by StavrosK on Saturday March 21, 2015 @01:59PM
(#9243571)
I see, thanks. So you basically get a blocking message queue for free, which is pretty cool.
Re:Video Streaming with RethinkDB Changefeeds
by atnnn on Saturday March 21, 2015 @12:21PM
(#9243157)
An app usually sit between the database and the user, isolating them from each other. This demo does not isolate the database, it is just a proof of concept.
Re:Video Streaming with RethinkDB Changefeeds
by StavrosK on Saturday March 21, 2015 @12:28PM
(#9243185)
Sorry, I was asking about the way the changefeed feature is meant to be used, not about this demo specifically.
Re:Video Streaming with RethinkDB Changefeeds
by habitue on Saturday March 21, 2015 @01:21PM
(#9243406)
Changefeeds are for getting updates to the results of queries on the database. So for example, getting the top 5 users ordered by their score. The app leaves a connection open to the database, and the database pushes changes to the query results whenever they happen.
The app can then also have a persistent websocket connection or whatever to the client, so you're able to get push architecture all the way from the data source to the client.