SDK Overview
ArcherDB ships five client SDKs over a shared geospatial operation surface:
| SDK | Package | Primary Docs |
|---|---|---|
| Python | archerdb |
src/clients/python/README.md |
| Node.js | archerdb-node |
src/clients/node/README.md |
| Go | github.com/ArcherDB-io/archerdb/src/clients/go |
src/clients/go/README.md |
| Java | com.archerdb:archerdb-java (local install until Central
publish) |
src/clients/java/README.md |
| C | archerdb-c |
src/clients/c/README.md |
Shared Capability Surface
The repo’s parity runner validates the same 14-operation surface across all five SDKs:
- insert
- upsert
- delete
- query-uuid
- query-uuid-batch
- query-radius
- query-polygon
- query-latest
- ping
- status
- topology
- ttl-set
- ttl-extend
- ttl-clear
See Parity Matrix for the current checked-in evidence summary.
Choosing An SDK
- Use Python for scripting, analysis, and operational tooling.
- Use Node.js for web backends and TypeScript-heavy applications.
- Use Go for single-binary services and low-overhead deployments.
- Use Java for JVM services and enterprise application stacks.
- Use C when you need the lowest-level interface and manual control over callbacks, buffers, and threading.
Source Of Truth
The language-specific READMEs under src/clients/ remain
the primary API and usage references. This directory provides the
aggregate index and parity-oriented comparison material the top-level
docs link to.
- Platform Support — what each SDK actually ships and validates per OS/arch
- SDK Comparison Matrix — parity and ergonomics across language clients