I am currently at the development stage of an MMO browser, the game will include tilemaps for some places in real time (so there is tile data for each cell) and a general world map. I prefer to use the MongoDB engine for a permanent data world.
I will also be able to implement a delivery simulation (which I will explain below), which is mainly a Dijkstra module, I decided to use a graphical database, hoping that this would simplify the situation, and found Neo4j as it is quite popular.
I was pleased with the setup of MongoDB + Neo4J, but then I noticed OrientDB, which apparently acts like MongoDB and Neo4J (best of both worlds?), They even have VS pages for MongoDB and Neo4J.
Point, I heard some terrible stories that MongoDB lost data (although I’m not sure that it is), and I do not have such luxury. And for Neo4J, I'm not a big fan of 12K € per year of “starting friendly” value, although I probably won't have DB of millions of tops. OrientDB seems to be a viable option, as there may be some possibilities for using a single database solution.
In this case, the logical move may jump to OrientDB, but it has a small community, and tbh did not find many reviews about it, MongoDB and Neo4J are popular widely used tools, I have problems if OrientDB is an adventure.
My first question will be if you have any experience / opinion regarding these databases.
And the second question would be that Graph Database is better for modeling delivery. It is expected that the database used will calculate the cheapest route from any vertex to any vertex and cross it (classic Dijkstra). But you also have to change the scales depending on situations, such as “country B has an embargo on country A, so any element originating from country A cannot pass through B, there is flooding in the XYZ region, therefore land transport is impossible”, etc. d. Also, this database is expected to cache results. I expect no more than 1000 vertices, but many edges.
Thanks in advance and apologize in advance if the questions are a bit ambiguous
PS: I added ArangoDB to the header, but tbh, didn't have much chance to take a look.
Later editing from April 18 to 2016: after evaluating the answers to my questions and development strategies, I decided to use ArangoDB, since their roadmap is more promising for me, since they apparently do not try to add tons of hype features that are half baked.