Skip to content
TaiDB logo TaiDB logo TaiDB

Other Languages

The Rust crate is the primary API. For other languages, the simplest supported path is a small wrapper around the installed taidb binary. This avoids hidden native build steps and works well for local tools, desktop apps, automation, and batch jobs.

Install the binary once:

Terminal window
cargo install taidb

Run the bridge examples:

Terminal window
node examples/node/cli.mjs
python3 examples/python/cli_bridge.py
go run examples/go/cli_bridge.go
ruby examples/ruby/cli_bridge.rb
php examples/php/cli_bridge.php
sh examples/bash/cli_bridge.sh
javac -d /tmp/taidb-java examples/java/CliBridge.java && java -cp /tmp/taidb-java CliBridge

Or run the full smoke set:

Terminal window
make language-smoke

Pattern

Section titled “Pattern”

Every bridge follows the same shape:

  1. Store the database path in application config.
  2. Call taidb put, taidb get, taidb vector-put, or taidb vector-search.
  3. Check the process exit status.
  4. Keep high-frequency hot paths in Rust or native FFI when process startup overhead matters.

When to use native FFI

Section titled “When to use native FFI”

Use native FFI only when you need lower latency than process spawning can provide and you are ready to ship platform-specific shared libraries. See the Native FFI reference for Python, Go, TypeScript/Deno, and C examples.