LoginSign Up
← Back to all sparks
T

TypeDB

DEVOPS
Velocity2.5

Strongly typed polymorphic database with a native reasoning engine

typedb.com ↗

Every release is groundwork for clustering, shipped through a hard driver compatibility break.

databasetransactionsclusteringrocksdbbreaking-changesdeveloper-experience
◆Current state
TypeDB is releasing frequently — ten versions between late April and mid-July 2026 — with release notes that explain the reasoning behind each change rather than just listing it. The recent work concentrates on transaction machinery and server operability: a deadlock in commits exceeding the RocksDB write buffer limit, transaction open latency, guarantees that the transaction operator actually closes what it was asked to close, exposed RocksDB memory tuning, and separated listen and advertise addresses. A clustered alpha appeared alongside the community line in May, and 3.11.5 raised the driver compatibility floor, rejecting connections from anything older than 3.11.0.
◆Where it's heading
The distributed story explains most of what looks like unrelated plumbing. Letting callers supply UUIDs for users and credentials exists so cluster members can share identical state instead of each generating its own; splitting listen from advertise address exists so a node can be reachable at an address it does not bind; making transaction close synchronous rather than fire-and-forget matters once another node depends on the result. Single-node correctness fixes are being made in the shape that a clustered deployment will need.
◆Prediction
Expect the clustered line to keep pulling extension points into the community server, and the optional-return warnings introduced in 3.10.3 to escalate into compilation errors as the notes promise. Whether clustering lands in the community edition or only in the enterprise distribution is not stated here.

◆Recent moves

  1. 27d ago

    Deadlock on large commits and a string comparison bug fixed

    Fixes a deadlock on commits larger than the configured RocksDB write buffer limit by dropping the allow_stall parameter, accepting that buffers may temporarily exceed the memory budget. Also corrects string attribute comparison bounds that were discarding valid answers — a silent wrong-results bug, the worst kind for a database.

    View source ↗
  2. 1mo ago

    Pre-created UUIDs for users and synchronous transaction close

    Allows pre-created UUIDs when creating users and credentials, justified in the notes by distributed deployments needing identical state across cluster members, and makes the transaction operator wait for closes to complete rather than firing and forgetting. Both changes are single-node in effect and clustered in motivation.

    View source ↗
  3. 1mo ago

    Candidate for 3.12.0 with RocksDB memory tuning exposed

    The release candidate carrying the same transaction operator changes that shipped in 3.12.0 ten days later, plus exposed RocksDB memory tuning parameters. Little here that the final release does not contain.

    View source ↗
  4. 2mo ago

    Drivers older than 3.11.0 rejected; startup prints connect hints

    Breaks backwards compatibility by rejecting drivers older than 3.11.0, and adds clickable Studio and Console connection hints to server startup output that adapt to the bind address and encryption settings. A hard compatibility floor paired with a small but real first-run improvement.

    View source ↗
  5. 2mo ago

    Candidate introducing the 3.11.0 driver compatibility floor

    The candidate that introduced the 3.11.0 driver compatibility break and the startup connection hints, with content matching the 3.11.5 release two weeks later. A preview rather than a distinct set of changes.

    View source ↗
  6. 3mo ago

    Statistics underflow panics downgraded to logged errors

    Fixes a statistics counting underflow that panicked when schema transactions deleted both types and their instances in the wrong order, and makes the server survive such underflows by logging rather than crashing. Turning a class of panic into a tolerable logged error is the durable part of this release.

    View source ↗