DB-Engines, Informix, and Neo4j: An Origins Story
On March 1st, the database industry monitor DB-Engines published their usual monthly ranking report for the world’s most popular database management systems. For the first time, Neo4j was listed in the top 20. Read on for the full story.
Join the DZone community and get the full member experience.Join For Free
a funny thing happened a little over a month ago.
on march 1st, the database industry monitor db-engines published their usual monthly ranking report for the world’s most popular database management systems. for the first time, neo4j was listed in the top 20.
this is certainly a moment of pride for me as a co-founder, and i look forward to neo4j rapidly working its way towards the top ten. of course, even this step along the way is a huge validation that graphs really are eating the world.
but, this isn’t about our accomplishments. there’s a deeper story underneath the surface, and in order to appreciate it, we’ll need to take a look back to a time before graph databases were a thing.
choosing our first "big four" database
at the top we had a web presentation layer, below that was a relatively unknown app server called silverstream, and at the bottom of our development stack was a relational database called informix.
for those of you who don’t remember informix, it was one of the "big four" databases that emerged as winners of the rdbms wars in the 80s (the other ones, of course, being oracle, db2, and sybase, which was later overtaken by microsoft sql server and subsequently acquired by sap… but, i digress).
this was a very standard architecture in the late 90s and early 2000s. but here’s where we ran into problems.
the challenge of connected data
in any content management system, you’re going to have a lot of connected data, and ours was no exception. the problem was that as an rdbms, informix wasn’t optimized to handle the relationships between all our data.
of course, we tried every tuning trick in the book. we even brought in an armada of informix consultants to helps us optimize our data access, but it was always slow and limited no matter what we tried.
and not only that, but from a developer productivity perspective, we found ourselves constantly bogged down by having to work through the mismatch of our connected domain model and the abstraction exposed to us by our database of choice.
while it was certainly a best-of-breed relational database, informix simply couldn’t handle the connected-data queries we (and our users) asked of it daily.
faced with the challenge of using an rdbms for connected data, we decided to create a new kind of database optimized for connected data: the graph database .
coming back full circle
the story of how we had to define a category for our newly invented product is one for a different day (or a different blog post!), but it’s certainly been a long journey–validated along the way by developers and architects that faced the same issues with connected data in their rdbms.
now, it’s been fifteen years since our first back-of-the-napkin sketch for the idea of a graph database, and as of this month, we’re in the top 20 database management systems used globally.
oh, and by the way, who was the previous holder of the #20 position on db-engines?
that’s right, informix.
Opinions expressed by DZone contributors are their own.