Hi Michael, As an OrientDB maintainer, I can tell you that SQL is much more optimized than Gremlin, so if you need good performance I strongly suggest you to use SQL. Tinkerpop (and Gremlin) is intended to be a standard, so it allows easier migration from a product to another; this said, TinkerPop also has slightly different extensions on different products, so the migration still requires some effort.
Thanks Luigi Il giorno gio 14 feb 2019 alle ore 23:31 Michael Faughn < m.fau...@prometheuscomputing.com> ha scritto: > I'm trying to determine the feasibility of switching to a graph database > for my company's toolchain. I've already mostly settled on OrientDB as the > most likely candidate. We would likely be looking at writing a Ruby OGM > for OrientDB if we do move forward*. I'm looking for an analysis of the > pros and cons of SQL and Gremlin. My conclusions so far are rudimentary and > amount to, 1) Gremlin is more universal, 2) SQL looks more facile and easy > to get going with. Any links to articles or blogs or forum posts would be > most welcome. Leaving an opinion here would be great too. > > > * Note -- I'm aware of Active-Orient. Having looked at it, I doubt we > would want to go with that. > > -- > > --- > 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 orient-database+unsubscr...@googlegroups.com. > 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
