At its core, Kuzu breaks away from traditional server-client Graph Database Management Systems (GDBMS). Instead of executing queries across network protocols, Kuzu runs entirely in-process inside your application code. Version 0.12.0 introduces several fundamental architectural updates:
When upgrading to 0.12.0, you simply load a database file created in v0.11.x or older. Kuzu is currently in a rapid development phase where storage formats often change. kuzu v0 120
import kuzu # 1. Initialize an on-disk database and connection db = kuzu.Database('./my_graph_db') conn = kuzu.Connection(db) # 2. Define the schema conn.execute("CREATE NODE TABLE User(name STRING, age INT64, PRIMARY KEY (name))") conn.execute("CREATE REL TABLE Follows(FROM User TO User)") # 3. Insert some data conn.execute("CREATE (:User name: 'Alice', age: 30)") conn.execute("CREATE (:User name: 'Bob', age: 25)") conn.execute("CREATE (:User name: 'Charlie', age: 35)") conn.execute("MATCH (a:User name: 'Alice'), (b:User name: 'Bob') CREATE (a)-[:Follows]->(b)") conn.execute("MATCH (b:User name: 'Bob'), (c:User name: 'Charlie') CREATE (b)-[:Follows]->(c)") # 4. Execute a multi-hop query result = conn.execute("MATCH (a:User)-[:Follows]->()-[:Follows]->(c:User) RETURN a.name, c.name") while result.has_next(): print(result.get_next()) Use code with caution. 💡 Use Cases for Kùzu v0.12.0 At its core, Kuzu breaks away from traditional
: Improved asynchronous query execution handles high-concurrency Node environments smoothly. Kuzu is currently in a rapid development phase
In internal benchmarks (such as the standard LDBC Social Network Benchmark), Kuzu consistently punches above its weight class, outperforming server-based graph databases in pure query execution time—largely because it spends exactly 0 milliseconds on network serialization/deserialization.