dmarcelino
Re:OrientDB 2.2 Released – Open-Source Graph Database
on Monday May 23, 2016 @01:32PM (#11755370)
A 3rd GraphDB vendor, ArangoDB, did benchmark both of them. You can find the results on their blog at https://www.arangodb.com/2015/10/benchmark-postgresql-mongod...
Re:Two years after LASIK eye surgery
on Friday July 24, 2015 @10:32AM (#9942224)
I had LASIK done some 10 years ago and I experience the same halos. It's quite annoying and disturbing. Not only that, the positive effects of the operation are not permanent. 3 years ago my vision worsen and I had my eyes checked discovering my myopia was back with 0.5 dioptres. The worst part was that the doctor said it was usual for people operated with LASIK to experience the same 7/8 years after the operation. My advice is don't do it, the short term improvements are not worth the long term issues.
BTW, have you ever noticed that many ophthalmologists wear glasses? I wonder why...
Re:Native multi-model can compete with pure document and graph databases
on Friday June 12, 2015 @08:57AM (#9705543)
They've added a graph including OrientDB at https://www.arangodb.com/2015/06/performance-comparison-betw...
Re:Native multi-model can compete with pure document and graph databases
on Monday June 08, 2015 @06:05AM (#9678100)
Given that the posted article is about ArangoDB I don't want steal their spotlight by turning this into an OrientDB discussion. Send me an e-mail with your questions and I'll be happy to answer them.
Re:Native multi-model can compete with pure document and graph databases
on Friday June 05, 2015 @12:37PM (#9666441)
I've been using OrientDB for the last 7 months and as such I've been following @lvca and @phpnode (OrientDB node.js driver creator/maintainer) work closely. I have great respect and admiration for both and for what they've achieved!
@lvca, I find your comment distasteful and it's not the first time I see you trying to shutdown people who criticise OrientDB (https://news.ycombinator.com/item?id=9253488) when you should really be thanking them for exposing the issues they face (a lot of people don't go public). It would be more productive to engage @phpnode, @anonwarnings and others, listen to them, raise issues in the bug tracker and address them. Accusing people of trolling or flaming doesn't benefit OrientDB or its users at all...
Unfortunately I haven't tried ArangoDB so I can't make any comparisons with OrientDB but I hope both succeed!
I haven't (yet) experienced something likes this, but in my 5 month experience with OrientDB I do get the impression that the team prefers to add new features over fixing bugs. If you consider OrientDB is a database that's quite troublesome... A DB should be rock solid and all bugs should be dealt with swiftly.