OrientDB

OrientDB is a multi-model NoSQL database that combines graph and document data models in a single engine. It's aimed at teams that would otherwise run several databases side by side and want fewer moving parts, while keeping data consistent.

The pitch is simple: one operational database that can replace a relational DBMS for many workloads, without giving up the flexibility of schemaless documents or the relationship modeling of a graph.

What you get:

• Graph Editor to visualize, interact with and modify your data
• Studio Query to run queries and see results right away
• Command-line console to manage and query databases from a terminal

Speed is a core design goal. Relationships are stored as physical links between records, so there are no joins. Reads and writes are both fast, and RAM use is better than in many comparable systems.

Traversal is where this design pays off. OrientDB walks parts of a tree or graph, or all of it, in milliseconds. Traversal speed doesn't slow down as the database grows.

If you're comparing options in the graph databases category, OrientDB is a fit when you need documents and graphs together. It's also worth weighing against Neo4j, which focuses on the graph model alone. Memgraph and FalkorDB are other graph-focused tools to check.