Show HN: Rxdb – A fast, reactive, client-side database
github.comPast submissions: https://hn.algolia.com/?query=rxdb&sort=byPopularity&prefix&...
Interesting to see the "growth hacking" works/doesn't work. It's the right place, very eye-catchy headlines, alas, very week comments and upvotes.
Also interesting to see "Local JavaScript-Database" as the most succesful headline and the current one " Show HN: Rxdb – A fast, reactive, client-side database " as the second best.
Weak "title" performers, "The poor man's Firebase", "An observable database in JavaScript", "ClientSide DB for Browsers, Node, electron, cordova, reactNative and every js-vm"
Past 20 submissions in the last 4 months by 2 multi-accounts + 2 "normals"! Interesting to see the different spins.
It's only spamming if you get caught. Otherwise it's growth hacking.
Most perfect definition of growth hacking I ever saw. Made my day.
How is access control handled? For instance, what if the data itself encodes access control, how do I prevent the data being sent over to the client-side inadvertently?
This is the problem Meteor had. They had this complex allow/deny configuration to see if the client has permission to run a query but it was impossible to get around all the edge cases. They started recommending not using it and instead call controllers that then would check server-side if the user has permission or not and return the data to sync to the client. Then every query client side is considered to have full read access to the data in it.
How does it compare to pouchdb and why would you chose rxdb instead of pouch?
RxDB relies on PouchDB. It mentions it in its README <https://github.com/pubkey/rxdb/blob/master/README.md#feature... and in its package.json <https://github.com/pubkey/rxdb/blob/master/package.json#L64>
It appears to interop with pouchdb, but is more tailored to clientside consumption with Rx.js.