Sparksee vs TypeDB

Sparksee is a property graph database; TypeDB is a other database. Sparksee (2008, Proprietary, C++) ranks #98 this month; TypeDB (2016, MPL-2.0, Rust) ranks #9. They differ on 26 of 46 surveyed features.

Attribute Sparksee #98 ▲20 Growing TypeDB #9 ▲3 Strong
At a glance
Rank #98#9
Score 38.363.6
GitHub stars 4.4k
Popularity 26.168.7
Activity 31.977.7
Community 35.366.4
Research 49.849.6
Fundamentals
Description A property graph database (formerly DEX) that stores graphs as labelled multigraphs using bitmap data structures for compact representation. Supports ACID transactions and offers free licenses for evaluation and research use.A polymorphic database that natively models inheritance hierarchies, dependencies, and conceptual schemas using its TypeQL query language. Supports clustering for scalability and a cloud-agnostic deployment model.
Vendor Sparsity TechnologiesVaticle
Model Property GraphOther
Kind databasedatabase
Category EstablishedGrowing
First released 20082016
Status activeactive
License ProprietaryMPL-2.0
Written in C++Rust
Query languages openCypherTypeQL
gdotv support nono

Feature scores 26 of 46 rows differ

Feature SparkseeTypeDB
Community & Business
Active development ·
Commercial support
Live community ·
Open Source ·
Pricing ·
Trendiness 0.5
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 0.5
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 0.5
Read committed transaction ·
Transaction support
Schema & Security
Constraints
Schema support
Secondary indexes
Server side procedures ··
Triggers ·
Authentication ·
Authorization ·
Data encryption ·