The fundamental design choice of Kùzu is its embeddability. Unlike traditional graph servers like Neo4j which require a separate server process, Kùzu runs inside your application's process. This "serverless" architecture provides several key benefits:
: Added support for the ignore_pattern option, allowing for more flexible search indexing.
Kùzu is an designed for high-performance analytical workloads, similar in spirit to DuckDB but for graphs. 1. Core Architecture & Features kuzu v0 136
# Query to find users interacting with specific feature categories result = conn.execute(""" MATCH (u:User)-[r:InteractsWith]->(f:Feature) WHERE f.category = 'Recommendation' RETURN u.name, r.weight, f.id """) while result.has_next(): print(result.get_next()) Use code with caution. Ideal Use Cases for Kùzu v0.13.6
Two missing Cypher clauses have been added. The UNWIND clause now works seamlessly with the new LIST type, allowing you to flatten arrays into rows. The CALL {} subquery syntax (with IN TRANSACTIONS ) enables batch processing of large updates without overwhelming memory. The fundamental design choice of Kùzu is its embeddability
import kuzu
Fixed edge-case memory leaks in the Rust bindings, providing a safer environment for systems-level graph applications. 2. Query Optimizer and Cypher Refinements Ideal Use Cases for Kùzu v0
Kùzu v0.13.6 reinforces the database's position as a premier choice for local, high-performance graph analytics. By doubling down on memory efficiency, ingestion speed, and Cypher fidelity, the development team continues to bridge the gap between heavy-duty graph analysis and dead-simple developer ergonomics.
The v0.13.6 release focuses on stabilizing core infrastructure, improving the query planner, and expanding language ecosystem support. Here are the core improvements included in this version: 1. Enhanced Cypher Query Planning