DBMS > BigchainDB vs. EJDB vs. Geode vs. Lovefield

System Properties Comparison BigchainDB vs. EJDB vs. Geode vs. Lovefield

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store

Key-value store

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

www.bigchaindb.com

github.com/Softmotions/ejdb

geode.apache.org

google.github.io/lovefield

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

geode.apache.org/docs

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

Developer

Softmotions

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Initial release

2016

2012

2002

2014

Current release

1.1, February 2017

2.1.12, February 2017

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GPLv2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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

Python

Java

JavaScript

Server operating systems

Linux

server-less

All OS with a Java VM

the JDK (8 or later) is also required

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

tested with Chrome, Firefox, IE, Safari

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

CLI Client
RESTful HTTP API

in-process shared library

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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 per client and object definable

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

Exploring the 10 BEST Python Libraries for Blockchain Applications
9 September 2023, DataDrivenInvestor

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

ascribe announces scalable blockchain database BigchainDB - CoinReport
13 February 2016, CoinReport

7 blockchain firms join Bosch led GAIA-X consortium for vehicle identity
13 September 2022, Ledger Insights

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page