Running a RethinkDB proxy node
We have our cluster consisting of one SEED Server and a RethinkDB instance to support the cluster. The SEED server is acting as master server (however, there is no such master/child concept in RethinkDB; we are phrasing this for understanding) to perform routing of queries and run various kinds of business logic to determine where the data is stored and where to point the request. This in turn increases the load and dependency on one RethinkDB instance. Refer to the following figure; the proxy node acts as the node to distribute the query across instances in the cluster:
RethinkDB allows us to create a proxy node ...
Get Mastering RethinkDB now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
