Performance of Graph and Relational Databases in Complex Queries

Abstract

In developing NoSQL databases, a major motivation is to achieve better efficient query performance compared with relational databases. The graph database is a NoSQL paradigm where navigation is based on links instead of joining tables. Links can be implemented as pointers, and following a pointer is a constant time operation, whereas joining tables is more complicated and slower, even in the presence of foreign keys. Therefore, link-based navigation has been seen as a more efficient query approach than using join operations on tables. Existing studies strongly support this assumption. However, query complexity has received less attention. For example, in enterprise information systems, queries are usually complex so data need to be collected from several tables or by traversing paths of graph nodes of different types. In the present study, we compared the query performance of a graph-based database system (Neo4j) and relational database systems (MySQL and MariaDB). The effect of different efficiency issues (e.g., indexing and optimization) were included in the comparison in order to investigate the most efficient solutions for different query types. The outcome is that although Neo4j is more efficient for simple queries, MariaDB is essentially more efficient when the complexity of queries increases. The study also highlighted how dramatically the efficiency of relational database has grown during the last decade.

The Use of Graph Databases in Systems Biology: A Systematic Review

“…This could be explained by the fact that i) GDBs are still a new technology compared to RDBs, ii) they might be difficult to adopt, and iii) they are less efficient than RDBs for some types of queries (e.g. complex queries with aggregates) or for structured data that are not densely interconnected [93].…”

Modelling Metadata and Data from Censuses and Surveys with Graph Databases

“…In addition, Neo4j also has good performance and simplicity in operation [17]. In addition, Neo4j also outperforms MySQL and MariaDB when running complex queries [18]. Thus research will use Neo4j as the graph database.…”

Routemighty: Route Planning Software Engine for Abnormal Trucks Based on Graph Database Using Neo4j

“…One of the reasons for this was easier query building, flexible data structure, and often also the speed of returning responses. In the work of Kotiranta et al, some queries to the Neo4j graph database exceeded the results obtained by the MySQL and MariaDB databases many times [10]. On the other hand, for more complex queries, modern relational databases often performed better than their graph counterparts.…”