![]() OrientDB seems like a logical choice to replace SQL databases or for Java developers (for graphs and JSON documents). New features and bug fixes are being done, all the time. (I haven't needed to reach out to the ArangoDB people, yet, since I have been able to figure out everything myself, so far).īoth OrientDB and ArangoDB are in a state of flux. The OrientDB team, also seems VERY responsive to requests. ![]() Otherwise, I really liked OrientDB, at the time I evaluated it I was actually hoping to stick with it. (In ArangoDB, I actually like coding in JavaScript, mixing a bit of AQL in, when needed). AQL (ArangoDB), after you get used to it, does seem to be designed for key-value pair queries, graphs, and documents, but it's query-only. (My personal preference leans toward native C/C++.) ArangoDB seems very light-weight and responsive all the time, including startup.Īgain, documentation was hard-to-find and inconsistent, as of OrientDB 1.5/1.6, but it does seem to have improved since then.įinally, in my experience, eSQL (OrientDB) does not seem like a logical choice for JSON Documents or for Graphs. ![]() I have mixed feelings about using the Java JVM for OrientDB, as opposed to native C/C++ used by ArangoDB. This should be easier (versions 1.2 through 1.6). Oddly, the /etc/init.d/ scripts seemed broken on the Linux version of OrientDB - they don't stop the database and are odd to configure. " when it worked in 1.2 / 1.3 was much easier). This can be determined programatically, of course. You can do JSON REST Bulk inserts which are very fast, but I find that creating graph relationships that way in OrientDB is challenging, unless you know the ID (#:#) of a vertex. Because of this, I don't find that the eSQL stuff is very useful for more than simple queries. " when you add graph relationships to existing data). In OrientDB, "CREATE VERTEX" has a very different syntax than "INSERT INTO" (and "CREATE EDGE" is very different than "UPDATE. (I have never crashed ArangoDB, including performing 150M JSON bulk imports). Bulk inserts will cause an out-of-memory crash, as of version 1.4+. " for graphs, unless you are doing things 1 record at a time. (I also considered Neo4J but could not afford it, in production, so it unfortunately never got a fair evaluation).Īs I mentioned earlier, in OrientDB, be careful using the eSQL syntax "INSERT INTO" and "UPDATE. I prefer ArangoDB over OrientDB, after a multi-month evaluation of both. Databases, of course, are complex software, with a long list of pros and cons.
0 Comments
Leave a Reply. |