DBMS > EJDB vs. Google Cloud Bigtable vs. SAP HANA vs. Tibero

System Properties Comparison EJDB vs. Google Cloud Bigtable vs. SAP HANA vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

In-memory, column based data store. Available as appliance or cloud service

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store

Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/bigtable

www.sap.com/products/hana.html

us.tmaxsoft.com/products/tibero

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigtable/docs

help.sap.com/hana

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Softmotions

Google

SAP

TmaxSoft

Initial release

2012

2015

2010

2003

Current release

2.0 SPS07 (April 4, 2023), April 2023

6, April 2015

License

Commercial or Open Source

Open Source

GPLv2

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and Assembler

Server operating systems

server-less

hosted

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

in-process shared library

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

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

SQLScript, R

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

yes

Multi-source replication
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 (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

planned for next version

User concepts

Access control

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

yes

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.