ArangoDB vs TAO
ArangoDB is a multiple database; TAO is a other database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; TAO (2012-05, Proprietary, C++) is not ranked. They differ on 27 of 46 surveyed features.
| Attribute | ArangoDB | TAO |
|---|---|---|
| At a glance | ||
| Rank | #2 | — Not ranked |
| Score | 76.7 | 29.5 |
| GitHub stars | 14.3k | — |
| Popularity | 89.4 | — |
| Activity | 73.9 | 54.9 |
| Community | 61.2 | 31.5 |
| Research | 82.8 | — |
| Fundamentals | ||
| Description | A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model. Offers both an in-memory storage engine and a RocksDB-based engine for larger datasets. | A distributed graph store built by Meta (Facebook) for serving the social graph at scale. Shards data across MySQL instances with a caching layer, later extended with the RAMP-TAO protocol for geo-distributed atomic visibility. Not available as a standalone product. |
| Vendor | ArangoDB Inc | Meta |
| Model | Multiple | Other |
| Kind | database | database |
| Category | Enterprise | Established |
| First released | 2012-03 | 2012-05 |
| Status | active | active |
| License | BUSL-1.1 | Proprietary |
| Written in | C++ | C++ |
| Query languages | AQL | TAO API |
| gdotv support | no | no |
Feature scores 27 of 46 rows differ
| Feature | ArangoDB | TAO |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | · |
| Commercial support | ✓ | · |
| Live community | 0.5 | · |
| Open Source | ✓ | · |
| Pricing | · | · |
| Trendiness | 0.25 | · |
| 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 | 0.5 | · |
| Transactions | ||
| Granular locking | · | · |
| Multiple isolation levels | · | · |
| Read committed transaction | · | · |
| Transaction support | ✓ | ✓ |
| Schema & Security | ||
| Constraints | ✓ | · |
| Schema support | 0.5 | ✓ |
| Secondary indexes | ✓ | ✓ |
| Server side procedures | 0.5 | ✓ |
| Triggers | · | ✓ |
| Authentication | ✓ | · |
| Authorization | 0.5 | · |
| Data encryption | ✓ | · |
Links
- ArangoDB · website · github · full profile
- TAO · website · full profile