DBMS > EJDB vs. Google Cloud Bigtable vs. YDB vs. YottaDB

System Properties Comparison EJDB vs. Google Cloud Bigtable vs. YDB vs. YottaDB

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.

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

A fast and solid embedded Key-value store

Primary database model

Document store

Key-value store
Wide column store

Document store
Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

github.com/Softmotions/ejdb

cloud.google.com/bigtable

github.com/ydb-platform/ydb
ydb.tech

yottadb.com

Technical documentation

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

cloud.google.com/bigtable/docs

ydb.tech/en/docs

yottadb.com/resources/documentation

Developer

Softmotions

Google

Yandex

YottaDB, LLC

Initial release

2012

2015

2019

2001

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache 2.0; commercial license available

Open Source

AGPL 3.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

Server operating systems

server-less

hosted

Linux

Docker
Linux

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (YQL)

by using the Octo plugin

APIs and other access methods

in-process shared library

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

RESTful HTTP API (DynamoDB compatible)

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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

Go
Java
JavaScript (Node.js)
PHP
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Active-passive shard replication

yes

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

Transaction concepts

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

Atomic single-row operations

ACID

optimistic locking

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

User concepts

Access control

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

Access rights defined for Yandex Cloud users

Users and groups based on OS-security mechanisms

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's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

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 introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Russian Court Sues Yandex CEO For LGBT Propaganda Case
30 April 2024, VOI.ID

Personal Data Protection Service Initiates Probe into Yandex.Go App’s Data Processing
10 August 2023, Civil Georgia

Data leak from Russian delivery app shows dining habits of the secret police
3 April 2022, The Verge

Yandex code leak: Why hack of ‘Russian Google’s’ ranking factors has spooked the SEO industry
1 February 2023, The Indian Express

Yandex Food Delivery Service Leak Revealed Personal Information of Russia's Secret Police
3 April 2022, Tech Times

provided by Google News

Share this page