If MongoDB has served you well so far, then you will immediately feel comfortable with ArangoDB, since it is very similar in look and feel. This is where a multi-model database as ArangoDB shines. It sounds as if your use case is exactly what ArangoDB is designed for: you seem to need different data models (documents and graphs) in the same application and might even want to mix them in a single query. In this way an eventual switch would have a low impact. If you have doubts with the GraphDB to use, my suggestion is to get what is closer to your needs, but then use standards as more as you can. The Community Group (Free channel to ask support) is the most active community in GraphDB market. The OrientDB project is growing every day with new contributors and users. Furthermore OrientDB supports also Gremlin. Furthermore OrientDB supports standards like SQL (with extensions) and the main Java API is the TinkerPop Blueprints, the "JDBC" standard for Graph Databases. You know, OrientDB is FREE for any usage, even commercial. Actually once you invested months to develop your application that use a non standard language or API you're screwed up: pay or migrate the application with huge costs. Tags : mongodb,neo4j,dijkstra,orientdb,arangodbĭisclaimer: I am the author and owner of OrientDB.Īs developer, in general, I don't like companies that hide costs and let you play with their technology for a while and as soon as you're tight with it, start asking for money. Late edit as of 1 : After evaluating responses to my questions and development strategies, I decided to use ArangoDB as their roadmap is more promising for me as they apparently not trying to add tons of hype features that are half baked. PS : I added ArangoDB at title but tbh, hadn't much chance to take a look. Thanks in advance and apologies in advance if questions are a bit ambiguous I expect no more than 1000 vertexes but many edges. Also that database is expected to cache results. But also have to change weights depending on situations like "country B has embargo on country A so any item originating from country A can't pass through B, there is flood at region XYZ so no land transport is possible" etc. Used Database is expected to calculate cheapest route from any vertex to any vertex and traverse it (classic Dijkstra). My first question would be if you have any experience/opinion regarding these databases.Īnd second question would be which Graph Database is better for a shipping simulation. In that case, a logical move might be jumping to OrientDB but it has a small community and tbh didn't find much reviews about it, MongoDB and Neo4J are popular tools widely used, I have concerns if OrientDB is an adventure. OrientDB seems a viable option as there may be also be some opportunities of using one database solution. And for Neo4J, I am not big fan of 12K€ per year "startup friendly" cost although I'll probably not have a DB of millions of vertexes. Point is, I heard some horror stories of MongoDB losing data (though not sure it still does) and I don't have such luxury. I was happy with MongoDB + Neo4J setup but then noticed OrientDB, which apparently acts like both MongoDB and Neo4J (best of both worlds?), they even have VS pages for MongoDB and Neo4J. I will also implement a shipping simulation (which I will explain more below) which is basically a Dijkstra module, I had decided to use a graph database hoping it will make things easier, found Neo4j as it is quite popular. Game engine I prefer uses MongoDB for persistent data world. I am currently on design phase of a MMO browser game, game will include tilemaps for some real time locations (so tile data for each cell) and a general world map.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |