The other issue is performance if you look at their GitHub issues.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues?q=is%3Aissue+is%3Aopen+label%3Atp%3Aperformance" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues?q=is%3Aissue+i...</a><p>Particularly concerning is this combination which makes me think I&#x27;ll have to shard like I would with MySQL rather than relying on RethinkDB in certain situations:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;5218" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;5218</a>
<a href="https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;5301" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;5301</a><p>Also crashing on building a secondary index:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;4808" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rethinkdb&#x2F;rethinkdb&#x2F;issues&#x2F;4808</a><p>I mean, don&#x27;t get me wrong, its a hard problem to solve and overall I think the product will work out but it does seem to have some limits on its horizontal scaling and it seems like you are better off stopping somewhere in the 5-9 node range then scaling those vertically then sharding on clusters of nodes.