- Setup of a replica set: is it easier/faster than with Mongo (which I find complicated)?
- Sharding: Easier than with Mongo?
- Rethink's query language: Is it really better than Mongo's after you used it for some time?
Happy to hear more insights if you know more noteworthy stuff and please no bashing of any of them. Just try to make an educated decision.
Nice! Also the writes? Mongo wants the writes to the primary only.
Think of this like Maslowe's hierarchy of needs. Sharding and replication are up at the top with self-actualization stuff like job satisfaction and feeling love toward animals. Meanwhile Mongo is missing the real basic stuff, like actually keeping your data, which is down with food, water, and shelter. You might think you care about replication, but you don't care about replication when both your database servers run out of memory at the same time.
Sorry, but this is just not true for many years now. Mongo has its warts but reading old stuff again and again feels strange and like pure hate. If your claims have some recent sources I am happy to hear them.
Reolication/clustering is real easy to set up.
Sharding is easy.
Scaling is easy.
I cant comment on query language vs mongo or rethink, since my experience with them is too limited.
Correctness isn't the primary focus, so unless you are willing to lose some stuff, don't use elasticsearch as your primary database.
https://www.quora.com/Why-shouldnt-I-use-Elasticsearch-as-my...
It you do not need to push to the client, I'd use Postgres. It just works. For replication and sharding better wait for 10 though.
As for progress, it slowed down to non-existent during the handover period, and now seems to be picking up.
not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.
To me focus on stability is the most important thing in a database so this makes me happy as an ops person, get it stable first and then if needed add more features. though i think rethinkdb is already quite feature complete.
side note: the node driver in npm still hasn't been re-published with the license type in the package.json, so doesn't show the license. Only noting as this can cause issues in some organizations.
