Hi Hamid, I'm using both Neo4j and OrientDB in two different projects. OrientDB has a smaller community on SO (even if it's growing very quickly), but the Community Group is very active, even more than this group for Neo4j:
https://groups.google.com/forum/#!forum/orient-database Hope can help, Don Il giorno sabato 2 maggio 2015 10:18:40 UTC+2, Hamid Gholizadeh ha scritto: > > I am interested to know which one you finally choose, especially in terms > of community support for orientDB, did you find somewhere other than small > stackoverflow community for help? > > On Thursday, May 22, 2014 at 6:53:55 AM UTC-4, Nikita Sushkov wrote: >> >> I already asked this question on stackoverflow, but it seems to be very >> opinionated. So it's better to ask here. >> >> We're starting a new project and looking for an appropriate storage >> solution for our case. Main requirements for the storage are as follows: >> >> - Ability to support highly flexible and connected domain >> - Ability to support queries like "give all children of that item and >> items linked to that children" in ms >> - Full text search >> - Ad hoc analytics >> - Solid read and write performance >> - Scalability (as we want to offer a Saas version of our product) >> >> First of all we eliminated all RDBMS, since we have really flexible >> schema which can also be changed by the customer (add new fields etc.), so >> supporting such solution in any RDBMS can become a nightmare... And we came >> to NoSQL. We evaluated sevaral NoSQL storage engines and chose 3 most >> appropriate (as we think). >> *MongoDB* >> >> Pros: >> >> - Appropriate to store aggregates with flexible structure (as we have >> them) >> - Scalability/Maturity/Support/Community >> - Experience with MongoDB on previous project >> - Drivers, cloud support >> - Analitycs >> - Price (it's free) >> >> Cons: >> >> - No support for relationships (relly important for us as we have a >> lot of connected items) >> - Slow retrieval of connected data (all joins happen in app) >> >> Neo4j: >> >> Pros: >> >> - Support of conencted data in modeling, flexibility >> - Fast retrieval of interconnected data >> - Drivers, cloud support >> - Maturity/Support/Comminity (if we compare with other graph Dbs) >> >> Cons: >> >> - No support for aggregate storage (we would like to have aggregates >> in one vertex than in several) >> - Scalability (as far as I know, now all data is duplicated on other >> servers) >> - Analitics ? >> - Write performance ? (read several blogs where customers complained >> on its write performance) >> - Price (it is not free for commercial software) >> >> OrientDB >> >> Pros: >> >> - It seems that OrientDB has all the features that we need >> (aggregates and graphdb in one solution) >> - Price (looks like is't free) >> >> Cons: >> >> - Immaturity (comparing with others) >> - Really small company behind the technology (In particular one main >> contributor), so questions about support, known issues etc. >> - A lot of features, but do they work pretty well >> >> So now, the main dilemma for as is between Neo4j and OrientDB (MongoDb is >> a third option because its lack of relationships that are really important >> in our case - this post >> <http://longtermlaziness.wordpress.com/2012/08/24/a-post-you-wish-to-read-before-considering-using-mongodb-for-your-next-app/> >> explains >> the pitfalls). I've searched for any benchmarks/comparison of these dbs, >> but all of them are old. Here is a comparison by features >> http://vschart.com/compare/neo4j/vs/orientdb. So now we need an advice >> from people who already used these dbs, what to choose. Thanks in advance. >> > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
