MarkLogic vs TigerGraph

MarkLogic is a multiple database; TigerGraph is a property graph database. MarkLogic (2001, Proprietary, C++) ranks #37 this month; TigerGraph (2017-09, Proprietary, C++) ranks #19.

Attribute MarkLogic #37 ▲5 Strong TigerGraph #19 ▲3 Strong
At a glance
Rank #37#19
Score 50.057.0
GitHub stars ——
Popularity 51.648.9
Activity 55.358.4
Community 36.062.4
Research 59.261.7
Fundamentals
Description A multi-model NoSQL database with native RDF triple storage, SPARQL support, and semantic reasoning. Combines JSON, XML, and RDF data models with ACID transactions and integrated full-text search.A distributed property graph database (formerly GraphSQL) built for massively parallel processing and graph analytics. Uses the SQL-like GSQL query language and supports ACID transactions. Available in developer, cloud, and enterprise editions.
Vendor Progress SoftwareTigerGraph
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 20012017-09
Status activeactive
License ProprietaryProprietary
Written in C++C++
Query languages SPARQL, XQuery, SQLGSQL
gdotv support yesno

Feature scores — not surveyed for MarkLogic

Feature MarkLogicTigerGraph
Community & Business
Active development —✓
Commercial support —✓
Live community —0.5
Open Source —·
Pricing —·
Trendiness —0.5
Deployment
Containerization —✓
Work as dedicated instance —✓
Work as embedded —✓
Testing in-memory version —0.5
Platform
Operating on Linux —✓
Operating on Windows —0.5
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 —0.5
Developer Experience
Data types defined —✓
Logging/Auditing —0.5
Object-Graph Mapper —·
Reactive programming —·
Documentation up-to-date —0.75
Binary protocol —·
CLI —✓
GUI —✓
Data Model
Multi-database —✓
Graph-native data —✓
REST API —✓
Query Language —✓
Transactions
Granular locking —·
Multiple isolation levels —·
Read committed transaction —0.5
Transaction support —✓
Schema & Security
Constraints —·
Schema support —✓
Secondary indexes —·
Server side procedures —✓
Triggers —·
Authentication —✓
Authorization —✓
Data encryption —✓