DBMS > AlaSQL vs. Coveo vs. Dgraph vs. MySQL vs. TerminusDB

System Properties Comparison AlaSQL vs. Coveo vs. Dgraph vs. MySQL vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Distributed and scalable native Graph DBMS

Widely used open source RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Relational DBMS

Search engine

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

docs.coveo.com

dgraph.io/docs

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Andrey Gershun & Mathias R. Wulff

Coveo

Dgraph Labs, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2014

2012

2016

1995

2018

Current release

8.4.0, April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

JavaScript

C and C++

Prolog, Rust

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

JavaScript API

RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript

C#
Java
JavaScript
Python

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

only for local storage and DOM-storage

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

granular access controls, API key management, content filters

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.