What Is A Graph Database?
A Graph Database Management System (DBMS) is a database system optimised for managing highly-related data. An obvious example is the Facebook social network of people and their activities. But relationships between things are a key part of any data management - and the more data we store, the greater the number and nature of relationships we need to make sense of.
"But isn't that what Relational Databases like Oracle and MySQL are for?" you might ask. The truth is that these products aren't relational stores at all - they're a collection of flat tables with a relational query language (SQL) tacked on. So when it comes to working with highly-related data, a Graph DBMS can be thousands of times faster.
What's more, the Relational DBMS puts a straight-jacket over your database. You need to create a "schema" to define your data and its relationships and that schema makes it impossible to adapt to your changing data needs without complete re-engineering.
There is a better way. A good Graph DBMS is a faster, more flexible and future-proof way to manage more data.
Traditionally, however, Graph Database implimentations have had problems that limit their usefulness...
- Storing data in a graph can be slower than other forms of database storage. This makes them less-suited to high-throughput and transaction-processing tasks.
- They can impose unnecessary structural complexity. Sometimes simpler structures are easier to manage and provide better performance.
- They're difficult to query. Generally the tools available for working with a Graph DBMS are poor.
- Their flexibility provides too much freedom for Enterprise data stores with tight rules and many different uses.
GraphBase is the first Graph DBMS to properly address each of these issues with its graph-focused query and transaction models, its rich tool set, its support for hybrid data stores, and its many other Enterprise-focused features.