New post up over at my personal blog: [url=https://www.wadewinningham.com/2018/03/30/our-journey-from-rails-v1-to-v5/]https://www.wadewinningham.com/2018/03/30/our-journey-from-rails-v1-to-v5/[/url]
New post up over at my personal blog: [url=https://www.wadewinningham.com/2018/02/28/exciting-work-at-a-boring-sounding-place/]https://www.wadewinningham.com/2018/02/28/exciting-work-at-a-boring-sounding-place/[/url]
I’m going to be writing more posts over at [url=https://www.wadewinningham.com]https://www.wadewinningham.com[/url].
First up is [url=https://www.wadewinningham.com/2018/01/16/together-we-create/]https://www.wadewinningham.com/2018/01/16/together-we-create/[/url]
While I’ll do some quick posts here to direct people I’ll eventually just have this site likely redirect over there at some point.
RethinkDB pushes results to your app in real timeTypically, you’d need a separate Publish-Subscribe system in place to do this. With RethinkDB, you can start a query and request to get changes. Your app will automatically receive any changed data related to your query after that. If you want something that’s closer to current Publish-Subscribe methods, RethinkDB has you covered there, too, with their repubsub library.
It’s insanely easy to clusterThis is right from their docs.
First, start RethinkDB on the first machine:
$ rethinkdb --bind all
Then start RethinkDB on the second machine:
$ rethinkdb --join IP_OF_FIRST_MACHINE:29015 --bind all
You now have a RethinkDB cluster!That’s it.