Render realtime RethinkDB results in React

Re:Render realtime RethinkDB results in React by curiousjorge on Saturday July 04, 2015 @03:28PM (#9831318)

> This is similar to solutions like Meteor, Parse, and Firebase. Rather than writing database queries in the backend and exposing API endpoints to the frontend, these solutions allow the frontend to directly access the data layer (secured by a permission system) using the same query API that backend services have access to.

This is a Meteor.js killer right here folks!

[ Parent | on HN ]

Re:Render realtime RethinkDB results in React by imslavko on Saturday July 04, 2015 @11:37PM (#9832411)

I think it explicitly says that it uses the same idea as Meteor's:

> Rather than writing database queries in the backend and exposing API endpoints to the frontend, these solutions allow the frontend to directly access the data layer (secured by a permission system) using the same query API that backend services have access to.

[ Parent | on HN ]

Re:Render realtime RethinkDB results in React by curiousjorge on Sunday July 05, 2015 @01:39AM (#9832592)

I don't think so because in Meteor.js you rely on iron-router and need to painsteakingly define and manage who can do what, and subscribing to new documents coming in the wire?

[ Parent | on HN ]

Re:Render realtime RethinkDB results in React by imslavko on Monday July 06, 2015 @03:31AM (#9837401)

The concept of subscriptions is completely separate from the router you use. At some point you would need to define who can subscribe to what documents, in any system with private data. It is called ACL.

[ Parent | on HN ]