ArcadeDB vs FlockDB
ArcadeDB is a multiple database; FlockDB is a other database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #9 this month; FlockDB (2010-04, Apache-2.0, Scala) ranks #76.
| Attribute | ArcadeDB | FlockDB |
|---|---|---|
| At a glance | ||
| Rank | #9 | #76 |
| Score | 65.4 | 41.7 |
| GitHub stars | 1.2k | 3.3k |
| Popularity | 54.7 | 48.2 |
| Activity | 76.8 | 36.9 |
| Community | 59.0 | 34.7 |
| Research | 74.7 | 50.0 |
| Fundamentals | ||
| Description | A multi-model database inspired by OrientDB, supporting graphs, documents, key-value, time-series, and search. Uses RAFT-based replication for high availability. | A distributed graph database built by Twitter for storing adjacency lists, optimized for wide and shallow social graphs like follower relationships. Supports set arithmetic queries but intentionally avoids multi-hop graph traversal. |
| Vendor | ArcadeDB | Twitter (now X) |
| Model | Multiple | Other |
| Kind | database | database |
| Category | Growing | Established |
| First released | 2021-09 | 2010-04 |
| Status | active | inactive — Archived and unmaintained since 2017. Twitter is no longer responding to issues or PRs. |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Java | Scala |
| Query languages | SQL, openCypher, Gremlin, GraphQL | Thrift API |
| gdotv support | yes | no |
Feature scores — not surveyed for FlockDB
| Feature | ArcadeDB | FlockDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | — |
| Commercial support | ✓ | — |
| Live community | ✓ | — |
| Open Source | ✓ | — |
| Pricing | ✓ | — |
| Trendiness | · | — |
| Deployment | ||
| Containerization | ✓ | — |
| Work as dedicated instance | ✓ | — |
| Work as embedded | ✓ | — |
| Testing in-memory version | · | — |
| Platform | ||
| Operating on Linux | ✓ | — |
| Operating on Windows | ✓ | — |
| SaaS offering | · | — |
| Operations | ||
| Automatic updates | ✓ | — |
| Client side caching | · | — |
| Data versioning support | · | — |
| Live backups | ✓ | — |
| Distribution | ||
| Cluster Re-balancing | · | — |
| Data Distribution | · | — |
| High-Availability | ✓ | — |
| Query Distribution | · | — |
| Replication support | ✓ | — |
| Developer Experience | ||
| Data types defined | ✓ | — |
| Logging/Auditing | ✓ | — |
| Object-Graph Mapper | · | — |
| Reactive programming | ✓ | — |
| Documentation up-to-date | ✓ | — |
| Binary protocol | ✓ | — |
| CLI | ✓ | — |
| GUI | ✓ | — |
| Data Model | ||
| Multi-database | ✓ | — |
| Graph-native data | ✓ | — |
| REST API | ✓ | — |
| Query Language | ✓ | — |
| Transactions | ||
| Granular locking | · | — |
| Multiple isolation levels | ✓ | — |
| Read committed transaction | ✓ | — |
| Transaction support | ✓ | — |
| Schema & Security | ||
| Constraints | ✓ | — |
| Schema support | ✓ | — |
| Secondary indexes | ✓ | — |
| Server side procedures | ✓ | — |
| Triggers | ✓ | — |
| Authentication | ✓ | — |
| Authorization | ✓ | — |
| Data encryption | ✓ | — |
Links
- ArcadeDB · website · github · full profile
- FlockDB · website · github · full profile