Graph databases have been around for more than 15 years, but it was AWS and Microsoft getting in the domain that attracted widespread interest. If they are into this, there must be a reason.
Everyone wants to know more, few can really keep up and provide answers. And as this hitherto niche domain is in the mainstream now, the dynamics are changing dramatically. Besides new entries, existing players keep evolving.
I’ve done the hard work of evaluating solutions, so you don’t have to. An overview of the domain and selection methodology, as presented in Big Data Spain 2018
Boost Fertility New Invention Ups Success Rates.pdf
The year of the graph: do you really need a graph database? How do you choose one?
1. THEYEAR OFTHE GRAPH:
DOYOU REALLY NEED A GRAPH DATABASE?
HOW DOYOU CHOOSE ONE?
The year of the graph: do you really need a graph database?The year of the graph: do you really need a graph database?
2. ABOUT ME
Working with data since 1992
Graph DBs since 2005
Databases
Modeling
Research
Analysis
Consulting
Entrepreneurship
Journalism
3. THE PROBLEMWITH RELATIONAL DBS
Not good at relations!
* Unintuitive model
* Hard to query
* Does not scale
16. REAL GRAPH DATABASES GO ALLTHEWAY
Operational vs. Analytical
* Fully-fledged graph API
* Operations & Analytics
* Future-proof, integrated
Native vs. Non-native
*Designed as a graph database
* Storing data in a native format
* Optimized for graph
21. GRAPH DATABASETYPES: MULTI-MODEL
(DOCUMENT, KEY-VALUE)
* Flexibility
*Tooling
* May not be optimized for graph
* May have to move data around
* Lock-in (cloud vendors)
22. EVALUATION CRITERIA: HOLISTIC, DATA-DRIVEN
Application Development
* Engine & API
* Data Model
* Query Language
DevOps
* Interoperability
* Deployment & Configuration
Advanced Analytics
*Advanced Graph
*Visualization
Vendor Credentials & Support
*Vendor Credentials
* Support & Community
23. EVALUATION CRITERIA:
PERFORMANCE & COST
* Not all vendors participate in benchmarks
* Most benchmarks are not done by 3rd party
* Complex, demanding exercise
* Hard to compare LPG vs RDF
* Not all vendors have public pricing & license info
* Considered, not included as data points
* Informed judgement needs experience, hands-on
24. TAKEAWAY POINTS
* Graph DBs are here to stay
* Different Graph DB models
LPG
RDF
Multi-model
* Each best suited to different use cases
* Evaluation is hard!
25. EVALUATING GRAPH DATABASES IS HARD..
BUT SOMEBODY HASTO DO IT
Impressive work. I’m not aware of another
source that is as comprehensive as this one.
JONATHAN LACEFIELD, SENIOR DIRECTOR
OF PRODUCT MANAGEMENT, DATASTAX
ENTERPRISE SERVER
We did not have the time,
resources, or expertise to
evaluate all options properly. If
we did, our choices would have
been different.
APPLICATIONARCHITECT
26. EVALUATING GRAPH DATABASES:
JUST DOTHE MATH
* 30+ options
* Costs time and money
* Requires expertise
* Lack of proper evaluation ->
Sub-optimal decisions ->
Report cost:
1 Day ofTop-tier consultant
Access to updates, consulting