DBMS > EJDB vs. GBase vs. Google Cloud Bigtable vs. Lovefield

System Properties Comparison EJDB vs. GBase vs. Google Cloud Bigtable vs. Lovefield

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)

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store

Relational DBMS

Key-value store
Wide column store

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

github.com/Softmotions/ejdb

www.gbase.cn

cloud.google.com/bigtable

google.github.io/lovefield

Technical documentation

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

cloud.google.com/bigtable/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Softmotions

General Data Technology Co., Ltd.

Google

Initial release

2012

2004

2015

2014

Current release

GBase 8a, GBase 8s, GBase 8c

2.1.12, February 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

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, Python

JavaScript

Server operating systems

server-less

Linux

hosted

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

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

yes

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

Standard with numerous extensions

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

in-process shared library

ADO.NET
C API
JDBC
ODBC

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

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Share this page