4 ms·

It really is killing it in the Enterprise, and I'm trying to do my part to remove it. I'm at a client that wants to use MongoDB. It's on the approved product li

It really is killing it in the Enterprise, and I'm trying to do my part to remove it. I'm at a client that wants to use MongoDB. It's on the approved product list. They have little to no experience with it. Every chance I get, I advocate ArangoDB. It also is Mongo Done Right. You get joins, graphs and a thoughtful future plan from ArangoDB team. To help bridge the gap I've written an ArangoDB Hadoop connector [1]. Unlike the MongoDB one, you can read and write. I've also added better Clojure support to it: from a driver to a Ragtime migrator. Sadly as it stands Mongo has a better Ops story than ArangoDB. Until that improves, I don't think that ArangoDB will make it into many Fortune 1000's outside of some small prototype style applications. Maybe micro-services in the enterprise will change this, but I don't think a large insurance company wants to support multiple database standards in general, and definitely not within a family. 1 - https://github.com/deusdat/guacaphant https://github.com/deusdat/guacaphant

tracker1 11y ago
You should give RethinkDB a look... it has a great ops interface, and now that it has automatic failover, is probably my first pick... I wanted to like Arango, but they tend to lag behind in node support. I happen to like MongoDB, warts and all.. that said, I would choose other options over it, depending on the need.
- virmundi 11y ago
  I did. At the time (haven't looked lately) RethinkDB didn't have GEO support while ArangoDB. Turns out that I don't really need it right now (different project). I stay because it's a great community. The Devs watch StackOverflow for questions. They are respectful and helpful in the user group. I know that RethinkDB has a good rep in those areas too. It's just that ArangoDB is a good general fit for what I need even now. I guess you could say I came for the GEO, I stayed for the warm hearted underdogs that are the ArangoDB community.
  - tracker1 11y ago
    That's funny, my first production use of MongoDB was because their geo support was better than ElasticSearch, which at the time, I couldn't get working correctly... I'm toying around with RethinkDB today for a hobby projuct, liking it so far.
ownagefool 11y ago
Distributed databases are hard. If you're suggesting UnknownDB as a solution you haven't learnt the lessons of Mongo. I really do hope CAP isn't going to bite you or the otherDB cheerleaders in the arse.

tracker1 11y ago

You should give RethinkDB a look... it has a great ops interface, and now that it has automatic failover, is probably my first pick... I wanted to like Arango, but they tend to lag behind in node support. I happen to like MongoDB, warts and all.. that said, I would choose other options over it, depending on the need.

virmundi 11y ago
I did. At the time (haven't looked lately) RethinkDB didn't have GEO support while ArangoDB. Turns out that I don't really need it right now (different project). I stay because it's a great community. The Devs watch StackOverflow for questions. They are respectful and helpful in the user group. I know that RethinkDB has a good rep in those areas too. It's just that ArangoDB is a good general fit for what I need even now. I guess you could say I came for the GEO, I stayed for the warm hearted underdogs that are the ArangoDB community.
- tracker1 11y ago
  That's funny, my first production use of MongoDB was because their geo support was better than ElasticSearch, which at the time, I couldn't get working correctly... I'm toying around with RethinkDB today for a hobby projuct, liking it so far.

ownagefool 11y ago

Distributed databases are hard. If you're suggesting UnknownDB as a solution you haven't learnt the lessons of Mongo. I really do hope CAP isn't going to bite you or the otherDB cheerleaders in the arse.