Share
BLOG

Graph Day 2016

Tags:
Summary:
A case study at Graph Day recounting a client study we did to see whether their database could be reorganized to offer improved query performance. We looked at graph databases (OrientDB, Titan, Neo4J) because they thought of their data as graph data, and relational (Postgresql) because that’s what their database already implemented.
Screen Shot 2016-01-28 at 4.00.12 PM

Two weeks ago, we had the privilege of presenting a case study at Graph Day. We recounted a client study we did to see whether their database could be reorganized to offer improved query performance. We looked at graph databases (OrientDB, Titan, Neo4J) because they thought of their data as graph data, and relational (Postgresql) because that’s what their database already implemented.

josh presenting

The findings were really interesting: bottom line, the graph data wasn’t as graphy as our client thought. We’re working on other proofs-of-concept where relational data models are a mess compared to graph models. We’ll be back with those later.

Many attendees asked for our slides. We’d love to hear your feedback, and if you have graph database evaluations of your own you’d like help with, do give us a buzz.

Slides

graph database evaluations cover

Subscribe to our quarterly newsletter

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.