whichdb
vs

ArcadeDB vs Bitsy

ArcadeDB: Multi-model Java database speaking SQL, Cypher, Gremlin, MongoDB and Redis protocols. Bitsy: Small embeddable Java graph database for TinkerPop: in-memory, ACID, persisted to readable JSON text files.

key differences

  • ArcadeDB is built for larger datasets (≤ 10 TB) than Bitsy (≤ 100 GB).
  • Only ArcadeDB has secondary indexes, full-text search, vector search, geospatial, json.
  • Only Bitsy has in-memory.

choose arcadedb for

  • +Migrating off OrientDB
  • +Mixed graph and document app backends
  • +Embedded multi-model storage in Java
  • +Graph plus vector retrieval

best at · OLTP, Traversal, Vector search

choose bitsy for

  • +Embedded graph storage in desktop or server Java applications
  • +Unit and integration tests for TinkerPop-based code
  • +Small to medium OLTP graphs that need durability without a server

best at · Traversal, Embedded, OLTP

ArcadeDBMulti-model Java database speaking SQL, Cypher, Gremlin, MongoDB and Redis protocols.
BitsySmall embeddable Java graph database for TinkerPop: in-memory, ACID, persisted to readable JSON text files.
overview
Primary model
Graph
Graph
Also supports
Document, Key-Value, Vector, Time-Series
–
Type
Database engine
Embedded library
Status
Active
Active
Developer
Arcade Data Ltd.
LambdaZen
First release
2021
2013
Latest version
26.10.2 (Oct 15, 2026)
3.6.6 (Jun 4, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
13.9
1.4
Rank
#240
#549
GitHub stars
1.2K
151
Stack Overflow questions
22
–
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
Small (≤ 100 GB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Full
Full
Consistency
Strong
Strong
Schema
Flexible
Schemaless
Architecture
Single node, Primary replica, Embedded, Client server
Embedded, In memory
deployment
Self-hosted
✓
—
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
✓
✓
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
✓
Joins
—
—
Secondary indexes
✓
—
Full-text search
✓
—
Vector search
✓
—
Geospatial
✓
—
JSON
✓
—
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
—
✓
Durable persistence
✓
✓
Compression
—
—
Encryption at rest
—
—
Role-based access
✓
—
Time travel
—
—
Branching
—
—
Online schema changes
✓
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
SQL, Cypher, Gremlin, GraphQL, MongoDB query language
Gremlin
Client languages
Java, Any PostgreSQL driver, Python, JavaScript
Java
Best for
OLTP, Traversal, Vector search, Embedded
Traversal, Embedded, OLTP
Add more to this comparisonNot sure either fits? Try smart match

ArcadeDB vs Bitsy: FAQ

What is the difference between ArcadeDB and Bitsy?

ArcadeDB: Multi-model Java database speaking SQL, Cypher, Gremlin, MongoDB and Redis protocols. Bitsy: Small embeddable Java graph database for TinkerPop: in-memory, ACID, persisted to readable JSON text files. ArcadeDB is built for larger datasets (≤ 10 TB) than Bitsy (≤ 100 GB). Only ArcadeDB has secondary indexes, full-text search, vector search, geospatial, json. Only Bitsy has in-memory.

When should I choose ArcadeDB over Bitsy?

Choose ArcadeDB for migrating off OrientDB; mixed graph and document app backends; and embedded multi-model storage in Java. Choose Bitsy for embedded graph storage in desktop or server Java applications; unit and integration tests for TinkerPop-based code; and small to medium OLTP graphs that need durability without a server.

Is ArcadeDB or Bitsy more popular?

ArcadeDB ranks #240 on the WhichDB Score (13.9/100) and Bitsy ranks #549 (1.4/100). Popularity is not fit: check the requirements that matter for your project.

Are ArcadeDB and Bitsy open source?

Yes. ArcadeDB is open source. License: Apache License 2.0. Yes. Bitsy is open source. License: Apache License 2.0.