4 ms·
Excited for this! We've been hoping to switch at least part of our infrastructure to Rethink, but were waiting for 2.0. Are real benchmarks on the way with thi
by cstigler 12y ago
Excited for this! We've been hoping to switch at least part of our infrastructure to Rethink, but were waiting for 2.0.
Are real benchmarks on the way with this release also? That's one critical thing we've been waiting to see. We want to see how it compares in common load scenarios to Mongo, Postgres, etc
- danielmewes 12y agoNot sure if we will have benchmarks available at launch, but they should follow soon after.
- tinco 12y agoI'm using RethinkDB for a new project I've been working on for the past few months, but I'm curious, why would you move existing infrastructure to RethinkDB? Is there a feature of RethinkDB that's good enough to motivate you to go through that process?
- neumino 12y agoI can think of these three right now: - changefeeds if you want to push data to your clients - joins (if you are on a system without them - like Mongo) - human-readable query language (if you are using SQL)
- cstigler 12y agoExactly. Joins and changefeeds being the big ones. We won't switch over everything, at least to start, but there are a few places where switching a collection to RethinkDB could give us huge efficiency/simplicity gains just using joins. And it shouldn't be too hard to switch single collections over by using Compose.io's Transporters to backfill into Mongo.