DBMS > EsgynDB vs. Google Cloud Bigtable vs. InterSystems Caché vs. SQLite vs. Trafodion

System Properties Comparison EsgynDB vs. Google Cloud Bigtable vs. InterSystems Caché vs. SQLite vs. Trafodion

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

A multi-model DBMS and application server

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store
Wide column store

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

Document store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/bigtable

www.intersystems.com/products/cache

www.sqlite.org

trafodion.apache.org

Technical documentation

cloud.google.com/bigtable/docs

docs.intersystems.com

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

Esgyn

Google

InterSystems

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2015

1997

2000

2014

Current release

2018.1.4, May 2020

3.45.3 (15 April 2024), April 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

Apache 2.0

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

Server operating systems

Linux

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

yes

schema-free

depending on used data model

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

.NET Client API
JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

C#
C++
Java

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

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

Source-replica replication

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

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

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

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.