TypeDB vs Apache Arrow Rust

TypeDB is in active feature development across the 3.12.x–3.13.x range, shipping minor versions every few weeks. The major capability addition this period is the `given` stage in 3.12.0—a batch parameterized query primitive that lets a single query run over multiple input rows, eliminating network round-trips, preventing TypeQL injection, and skipping repeated compilation overhead. Alongside that, 3.12.0 added `@doc` and `@meta` schema annotations and exposed RocksDB memory controls for production tuning. Subsequent releases have focused on schema management (type renaming in 3.12.2) and memory reliability (commit eviction, eager key cleanup in 3.13.0).

TypeDB is building toward production-scale distributed deployments: clustered database import/export, UUID assignment for distributed user creation, and per-component memory limits are all infrastructure features that matter at scale. The three-stage query cache (parse, translate, compile) and the `given` stage reduce the per-query overhead that made TypeDB feel expensive at volume. Schema evolution tooling (type renaming, doc/meta annotations) is maturing, suggesting teams running TypeDB in production can now make schema changes without teardown.

The clustering foundation being laid (import/export, UUIDs, metrics extensions API) is likely ahead of a TypeDB Cluster stability release or formal cluster documentation. The `given` stage will probably appear prominently in driver README updates and benchmarks next.