Live data from Hacker News

Advancing the realtime web

rethinkdb.com

1–10 of 51 posts

Re: Advancing the realtime web

#2
The article talks about mobile app feeds, and I understand how I could build a system rpc server for mobile and desktop apps. How would this work for web apps? The headline says "real-time web!"

Compare this solution to push it all the way through the web stack: http://engineering.imvu.com/2014/12/27/the-real-time-web-in-...

Re: Advancing the realtime web

#3
post #2

The article talks about mobile app feeds, and I understand how I could build a system rpc server for mobile and desktop apps. How would this work for web apps? The headline says "real-time web!" Compare this solution to push it all the way through the web stack: http://engineering.imvu.com/2014/12/27/the-real-time-web-in-...

The basic architecture is browser web server database.

When the web browser connects to the web server, the web server opens a database feed. When the database pushes changes to the web server, the web server pushes them to the browser via socket.io.

Re: Advancing the realtime web

#5
> A few community members have been working on a RethinkDB integration with Meteor and Volt, and we expect robust integrations to become available in the coming months.

If I'm understanding correctly, RethinkDB could be a drop in replacement for mongodb? What are the benefits to this replacement in the context of Meteor?

Re: Advancing the realtime web

#6
Happen to be using the streaming API and I have to say it's fantastic.

I hide all my realtime streams behind a "/realtime" endpoint and watching specific tables for changes couldn't be easier (just the changes command, which produces an infinite sequence).

Generally as simple as: r.db('db').table('table').changes().run(conn) (depending on your language it might look a little different).

Then again I'm pretty sold on RethinkDB so my opinion should probably come with a large-ish grain of salt.

Re: Advancing the realtime web

#7

> A few community members have been working on a RethinkDB integration with Meteor and Volt, and we expect robust integrations to become available in the coming months. If I'm understanding correctly, RethinkDB could be a drop in replacement for mongodb? What are the benefits to this replacement in the context of Meteor?

For one thing, you're not tied to Mongo. Generally more choices is good.

As for real reasons: - ReQL, functional, composable, and declarative, is very nice to use

- Changefeeds

- (v1.16) Arbitrary query watching with changefeeds

- Ease of sharding/load-balancing

- (v1.16) dynamic server management through queries

- Awesome web admin API

- Actually saving stuff to disk (couldn't resist)

This video on the highlights of rethinkdb is old but still relevant: https://www.youtube.com/watch?x-yt-ts=1422327029&x-yt-cl=848...

Re: Advancing the realtime web

#8

Would love to see this as an option to mongodb on meteor

Supposedly someone was working on this -- I share the sentiments and thought about starting something as a weekend project but I saw this talk:

https://www.youtube.com/watch?v=YLu_ROrA0YY

backed by this repo: https://github.com/andrewreedy/rethink-livedata

The project is a year old... I'm not sure if it's still in progress (seems not) and I'm not sure if the RDB team themselves are pursuing getting together with meteor

Re: Advancing the realtime web

#9

> A few community members have been working on a RethinkDB integration with Meteor and Volt, and we expect robust integrations to become available in the coming months. If I'm understanding correctly, RethinkDB could be a drop in replacement for mongodb? What are the benefits to this replacement in the context of Meteor?

If you're a meteor user you probably wouldn't notice the differences early on because livequery does a phenomenal job abstracting all the hard work away. However, we anticipate two advantages in the later stages of app development.

Firstly, as the app scales, livequery has to work harder and harder. I don't know how good its scalability is at the moment, but I think it would be very hard to approach the scalability of the feeds built into the database.

Secondly, as we build feed support into more and more queries, you'll be able to get functionality unavailable in livequery, which will allow building more sophisticated realtime experiences than currently possible.

We're going to find out how all these components work together in practice in the next few months. I'm really looking forward to that!

Re: Advancing the realtime web

#10
Could someone elaborate on the use-cases that rethinkdb tries to solve?

As a DB newb, what are the advantages of rethinkdb vs. other NoSQL DBs like Mongo. Why and where would I use rethink instead of an SQL DB like postgres?

Post reply on HN