DBMS > Graph Engine vs. Hypertable vs. Spark SQL vs. SQLite vs. Transbase

System Properties Comparison Graph Engine vs. Hypertable vs. Spark SQL vs. SQLite vs. Transbase

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

An open source BigTable implementation based on distributed file systems such as Hadoop

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Graph DBMS
Key-value store

Wide column store

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.graphengine.io

spark.apache.org/sql

www.sqlite.org

www.transaction.de/en/products/transbase.html

Technical documentation

www.graphengine.io/docs/manual

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Hypertable Inc.

Apache Software Foundation

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2010

2009

2014

2000

1987

Current release

0.9.8.11, March 2016

3.5.0 ( 2.13), September 2023

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

GNU version 3. Commercial license available

Open Source

Apache 2.0

Open Source

Public Domain

commercial

free development license

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

C++

Scala

C and C++

Server operating systems

.NET

Linux
OS X
Windows

an inofficial Windows port is available

Linux
OS X
Windows

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

APIs and other access methods

RESTful HTTP API

C++ API
Thrift

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
F#
Visual Basic

C++
Java
Perl
PHP
Python
Ruby

Java
Python
R
Scala

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.