orientdb

It's an "and" rather than an "either-or" :) When the database is open-source, and I spot something that's broken that I know how to fix, I try to fix it. Here's a fix for a severe database query planner correctness bug I contributed to an open-source database called OrientDB: https://github.com/orientechnologies/orientdb/pull/7015 Unfortunately, Microsoft SQL Server, Oracle, and many other databases are not open-source, and I can't hack on their query planners. And even if they were, SQL is an absolutely massive language (the complete spec is 100,000+ pages). The GraphQL compiler query language is tiny in comparison, the spec is maybe 10 pages: https://graphql-compiler.readthedocs.io/en/latest/language_s... It's a lot easier to intelligently map a small language to a big one than it is to optimize the big language outright. In a sense, S

Strange that they have to have such a non-standard license, when they go out of their way to mention Apache 2 several times: https://github.com/dgraph-io/dgraph/blob/master/LICENSE.md Contrast that with Orient, who also have an Enterprise version, and they just straight-up say "Apache 2, no drama" https://github.com/orientechnologies/orientdb/blob/develop/l... We had an absolutely miserable experience trying to get Janus to behave rationally, and thus far have had zero drama with Orient; we skipped dgraph because it does not appear to work with Gremlin, meaning one must use vendor-specific APIs to use dgraph. Their client reminds me of the days before ORM: write a big string literal and send it to the server: https://github.com/dgraph-io/dgraph4j#running-a-query

It's in this bug report: https://github.com/orientechnologies/orientdb/issues/6179 I recognize this was closed (by you, apparently) on the basis that I was using a bug report to ask a question. The intent of the bug report is that if the ETL file doesn't sufficiently describe what to do with the data, you should display a sensible error message, instead of a traceback from deep within the internals of OrientDB. If I've failed to list a primary key somewhere, you should tell me that, not assume that I want the primary key to be "null". But yes, on top of that, my question remains.

Not trolling, but for various reasons I don't want my employer linking these comments to my real account. We spent a lot of time and money trying to get OrientDB working and we ran into so many problems that it was impossible for us to continue with it. It is buggy beyond belief, distributed mode is deeply flawed, transactions are not transactional, it's super easy to hang the database and the explain keyword straight up lies, the backup strategy is non-existent, the documentation incredibly poor and riddled with typos and outright mistakes. When we finally thought we'd got over these issues, we imported our data and the system ground to a halt, just weeks before a major product launch. Luckily we were able to move to Postgres pretty quickly, but choosing OrientDB nearly sank the company, choosing it was an inaffordable mistake. Also, loo

I have not developed with salesforce and this is the first time that I am reading about their database. But it looks to me that you can implement what they are doing with orient db. It has fluid schema, "objects" and an sql like query syntax. https://github.com/orientechnologies/orientdb All of the good stuff is in the wiki :)

Almost all graph databases use gremlin as querying language but I really love orient db's approach of using sql[1] for querying graphs. It feels more natural in my opinion plus it lowers the barrier to entry for people who already know about sql. Some of the things I like about cayley 1. Switchable backends(I wonder if I can configure it to use couchdb as a store) 2. Documentation get right to the point. When I first tried my hand at graph databases I could not understand where to start but cayley's approach is pretty straight forward and it wins plus points from me for including a big dataset :) A question: I see no mention in the docs about running it on multiple nodes (where does it stand with regards to CAP etc) [1](https://github.com/orientechnologies/orientdb/wiki/SQL)

OrientDB. Nothing too fancy though. They have a comparison page (although it might be biased) : https://github.com/orientechnologies/orientdb/wiki/GraphDB-C...

An Update : A lot of people are using orient db as seen from the client list on the official[1] website but there are no posts regrading the "orient db expereince" So I downloaded it and gave it a try last night here are my impressions so far. 1. It has got an awesome documentation for both first time users[2] and those looking for in depth understanding[3] of orient db. 2. It is very easy to pick up. A no brainer installation, a familiar query syntax and a small api make it easy to pick up even if you have never experienced a graph db before. 3. It has clients in popular languages + an http api. I see that there is no client for erlang yet so I am planning to write a small http erlang client for it. 4. The default console client that orient ships with is very easy to use. That is about it for the moment. I can't believe I missed this dat

Baasbox DB is orientdb, which is open source: https://github.com/orientechnologies/orientdb

OrientDB has some great explanations on their github wiki. Here is their thoughts on why references are better than joins: https://github.com/orientechnologies/orientdb/wiki/Tutorial:... And this page gives an overview of relationships in general with OrientDB: https://github.com/orientechnologies/orientdb/wiki/Concepts#... Personally I have found the relational model limiting for performance in certain use cases and limiting in terms of mental overhead in others. I have used MongoDB a lot, however only having embedding to model relationships is also very limiting. The promise of OrientDB is a documunt store with support for embedding (and class inheritance), but also being able to use references rather than joins. What embedding and references have in common is that you have to do more up front work to define your relationships. You can