Hi Nikita, You can mix both models if needed. Lvc@
On 22 May 2014 16:05, Nikita Sushkov <[email protected]> wrote: > Hi Luca, > > Thank you for your response. Maybe now I have more particular question:can > my storage be document and graph at the same time (aggregates as vertexes) > or I should choose between these two models? > > четверг, 22 мая 2014 г., 15:25:35 UTC+4 пользователь Lvc@ написал: >> >> Hi Nikita, >> I agree with your big-picture about differences between such 3 products, >> just my thoughts about OrientDB cons on "*Immaturity (comparing with >> others) and Really small company behind the technology (In particular one >> main contributor), so questions about support, known issues etc.*" >> >> We've many clients in production, some of the clients are enlisted here: >> http://www.orientechnologies.com/customers/. The gap with Neo4J is not >> so big in terms of users/clients (considering also that Neo4J is a 10 year >> old company), and against MongoDB we're much smaller, but all the NoSQL >> company are much smaller than MongoDB in terms of selling numbers and >> company size... >> >> OrientDB is not (anymore) an one-man project since more than 2 years ago. >> We've a strong development team and about 40 contributors that help us to >> improve OrientDB every day: >> >> https://github.com/orientechnologies/orientdb/graphs/contributors >> >> For the rest, users here (we're about 1,800) worked with both Neo4J and >> MongoDB and they can give a more objective point of view than mine ;-) >> >> Lvc@ >> >> >> On 22 May 2014 12:56, Nikita Sushkov <[email protected]> wrote: >> >>> 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 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 "OrientDB" 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. >>> >> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" 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. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
