DBMS > Blueflood vs. EJDB vs. Google Cloud Bigtable vs. Percona Server for MongoDB

System Properties Comparison Blueflood vs. EJDB vs. Google Cloud Bigtable vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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 drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Time Series DBMS

Document store

Key-value store
Wide column store

Document store

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.60
Rank	#246	Overall
	#39	Document stores

Website

blueflood.io

github.com/Softmotions/ejdb

cloud.google.com/bigtable

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

github.com/rax-maas/blueflood/wiki

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

cloud.google.com/bigtable/docs

docs.percona.com/percona-distribution-for-mongodb

Developer

Rackspace

Softmotions

Google

Percona

Initial release

2013

2012

2015

Current release

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

commercial

Open Source

GPL Version 2

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

Java

C++

Server operating systems

Linux
OS X

server-less

hosted

Linux

Data scheme

predefined scheme

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

APIs and other access methods

HTTP REST

in-process shared library

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

proprietary protocol using JSON

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
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

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

via In-Memory Engine

User concepts

Access control

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

Access rights for users and roles

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

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google 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

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

Google Launches Cloud Bigtable, A Highly Scalable And Performant NoSQL Database
6 May 2015, TechCrunch

provided by Google News

There are lots of ways to put a database in the cloud – here's what to consider
15 September 2023, The Register

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

The Case Against the Server Side Public License (SSPL)
11 October 2022, The New Stack

Supercharge your Amazon RDS for MySQL deployment with ProxySQL and Percona Monitoring and Management ...
12 October 2018, AWS Blog

provided by Google News

Share this page