DBMS > EJDB vs. Fauna vs. Google BigQuery vs. Hazelcast

System Properties Comparison EJDB vs. Fauna vs. Google BigQuery vs. Hazelcast

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)

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Primary database model

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.52
Rank	#153	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Website

github.com/Softmotions/ejdb

fauna.com

cloud.google.com/bigquery

hazelcast.com

Technical documentation

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

docs.fauna.com

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

Developer

Softmotions

Fauna, Inc.

Google

Hazelcast

Initial release

2012

2014

2010

2008

Current release

5.3.6, November 2023

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache Version 2; commercial licenses available

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

Scala

Java

Server operating systems

server-less

hosted

All OS with a Java VM

Data scheme

schema-free

yes

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

in-process shared library

RESTful HTTP API

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

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

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Replicated Map

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

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

Identity management, authentication, and access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control

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.