未加星标

MongoDB vs RethinkDB : Why we had to choose MongoDB

字体大小 | |
[数据库(综合) 所属分类 数据库(综合) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

We keep a small portion of our data in MongoDB. We recently evaluated RethinkDB as a replacement for our Mongo cluster, after reading about how much more robust its storage engine is. Here is our technical analysis of why we had to stick with Mongo:

1 - No POJO library for Java

With Mongo, we use the Spring Data MongoDB library. It takes care of converting plain Java objects to/from the json format that Mongo drivers need. It results in typesafe, high level code and we never have to interact with the low level Mongo driver.

With RethinkDB, we found no such thing. The only way to interact with it was through its Java driver, which forced us to manually convert our objects to/from Maps. This essentially wiped out all the ease of using a document database in the first place. It meant everything that takes a single line with Spring and Mongo would take many, many lines with RethinkDB.

2 - MongoDB Cloud Manager

MongoDB's Cloud Manager service takes care of handling all the administrative tasks of MongoDB. Specifically:

a - Installation

Mongo Cloud installs MongoDB on our private servers. Its the best of both worlds, since we get Mongo inside our virtual network but its managed like a PAAS. We don't have to care about the exact installation steps. While RethinkDB might be easy to install, nothing beats clicking a button in a GUI.

b - Upgrades

For production, the story doesn't end at installation. With RethinkDB, we would have to write custom scripts to upgrade the database whenever a new version was released. We would have to put in effort to understand the upgrade procedure and notes of each release to ensure the update completed with minimal to no downtime.

With MongoCloud, upgrades are fully automated and just requires a few clicks.

c - Backup

A database without a backup is just a cache.

Mongo Cloud takes full care of backups and restore without us needing to do anything manual.

With RethinkDB, we would have to write custom scripts to run its command line backup tool and ensure the script was always working.

Conclusion

RethinkDB might have been a better database engine . However, choosing a database product doesn't stop at the engine. We realized that both our development and administrative burden would increase by an order of magnitude if we switched to RethinkDB. Thus, for now we continue to stick with Mongo.

本文数据库(综合)相关术语:系统安全软件

主题: MongoDBJavaSpring
分页:12
转载请注明
本文标题:MongoDB vs RethinkDB : Why we had to choose MongoDB
本站链接:http://www.codesec.net/view/480263.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 数据库(综合) | 评论(0) | 阅读(54)