DBMS > Dgraph vs. EsgynDB vs. Google Cloud Bigtable vs. Manticore Search vs. SQLite

System Properties Comparison Dgraph vs. EsgynDB vs. Google Cloud Bigtable vs. Manticore Search vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Multi-storage database for search, including full-text search.

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS

Relational DBMS

Key-value store
Wide column store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

dgraph.io

www.esgyn.cn

cloud.google.com/bigtable

manticoresearch.com

www.sqlite.org

Technical documentation

dgraph.io/docs

cloud.google.com/bigtable/docs

manual.manticoresearch.com

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

Esgyn

Google

Manticore Software

Dwayne Richard Hipp

Initial release

2016

2015

2017

2000

Current release

6.0, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL version 2

Open Source

Public Domain

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.

Implementation language

C++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

FreeBSD
Linux
macOS
Windows

server-less

Data scheme

schema-free

yes

schema-free

Fixed schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

not rigid because of 'dynamic typing' concept.

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

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

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.