Leaving MongoDB and Joining OrientDB | Hacker News Reader

Leaving MongoDB and Joining OrientDB

dataandco.expertly.io

69 pointslvca22 comments

Maybe I'm not too informed but who is this? Looking at his linked in he seems to be a sales person/business development person just moving to a new position.

Is he well known in the big data community and/or built any of the big data tools widely used? Just curious for more background than what sounds like a pretty common occurrence at startups.

I'm very curious how far OrientDB has made it. I remember using them ~1.5 years ago, and it was plagued with bugs, and data loss issues. Maybe they'll be able to take some of the knowledge from the MongoDB folks, and use it to bolster their storage engine.

Tomorrow post - moving from orientdb to someotherdb. Stay tuned folks!

See our magazine - bikeshedding for the inexperienced, on sale now!

Your ideas are intriguing to me and I wish to subscribe to your newsletter.

Engine improved a lot in the last few years and it's now deployed in production by thousands of users. Give it a try again and you'll change your mind ;-) Cheers, Luca

I'm currently using it in a project and I'm overall pretty impressed. I started using it with the 2.0 release candidates, and have no experience with earlier versions. With that exposure I've been very happy and I'm looking forward to the work the team's doing to make the DB available as a turnkey on various cloud services.

Leaving one of the most successful startups in history isn’t easy.

Interesting sentence. Isn't it a bit early to say that MongoDB is "successful"?

Overstating their success and awesomeness is just MongoDB's normal mantra. You get used to it.

Can these kind of comments stop? Please?

This has been trumpeted pretty much constantly on HN, and even if it's true, does it matter? Is anyone seriously evaluating their database on the basis of marketing copy? I suppose if you do, you can't be surprised if you have a bad time.

While an old trope, MongoDB's awesomeness drove a lot of attention to it. To some degree this led to management picking it for awesomeness value (yes, even in stogie enterprises like Insurance or Government Fraud). I think many on HN are partially riding a MEME and partially reacting viscerally to a technically mediocre product getting as far as it had (this is HN after all).

They're valued at 1.6 billon. Pretty successful if you ask me.

http://blogs.wsj.com/digits/2015/01/14/big-data-startup-mong...

If they are not publicly traded, this value is meaningless.

They just need to find a greater fool.

It must be an interesting time for OrientDB.

Aurlieus, the creators of TitanDB was recently acquired by DataStax and promptly dropped support of TitanDB[1]. That's left a bit hole in the market for a genuinely scalable, open source GraphDB (Neo4J has an open source "community edition").

OrientDB is one of the prime candidates left. I'd note that Wikidata recently chose BlazeGraph for their query interface[1], which is an option I'd never heard of before.

[1] http://www.datastax.com/2015/02/datastax-acquires-aurelius-t...

[1] https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...

Interesting, OrientDB seems to have really grown lately. It is advertising itself in the same way I talk about my own javascript based opensource database project (http://github.com/amark/gun), multi-model, relational/document, graph, multi-master, etc. Obviously Orient is much more mature than mine (not production ready or stable). Maybe I should give OrientDB a try, and see if it stands up to its claims!

Great work, keep it up.

I was very excited about OrientDB when I first tried it a couple of months ago. What's not to love about a graph DB that is faster and freer than Neo4J?

I ran into several seemingly independent DB corruption issues.

When I read through the OrientDB community forum I saw many reports of issues which should scare you if you use OrientDB as your sole persistence point. It seemed that many of these issues were rapidly fixed but without a link to a bug report or an explanation of the issue. This didn't give me confidence in the development process for the DB.

There is copious OrientDB documentation and it looks beautiful and professional, but in my opinion the documentation at times does not answer fundamental questions. I don't like to be a stickler for grammar, but often enough the grammar in the documentation was bad enough that it confused me.

It also seemed that the OrientDB is missing some of the advanced indexing functionality that Neo4J gets from integrating Lucene.

I'm planning to give OrientDB another try in a year or so.

Thanks. Keep us posted and feel free to reach out if you need help.

Yeah, could we talk? Give me an email: mark@gunDB.io, I've been talking to the RethinkDB guys, Firebase, Dropbox Datastore, Meteor, etc. Would love to chat with you guys too.

Email just sent. Let's talk.

huh, haven't gotten it yet. Sorry, could you try: aquiva (AT) g(oogle)Mail dot com? Thanks.

Not sure this is beneficial advertising for OrientDB

Care to elaborate?

Reply on news.ycombinator.com