21–24 of 24 posts
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!
Earlier quoted context omitted.
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.
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...
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!