DBMS > EJDB vs. Fauna vs. Google Cloud Datastore vs. WakandaDB

System Properties Comparison EJDB vs. Fauna vs. Google Cloud Datastore vs. WakandaDB

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Document store

Object oriented DBMS

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

github.com/Softmotions/ejdb

fauna.com

cloud.google.com/datastore

wakanda.github.io

Technical documentation

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

docs.fauna.com

cloud.google.com/datastore/docs

wakanda.github.io/doc

Developer

Softmotions

Fauna, Inc.

Google

Wakanda SAS

Initial release

2012

2014

2008

2012

Current release

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

AGPLv3, extended commercial license 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

C++, JavaScript

Server operating systems

server-less

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, details here

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 (GQL)

APIs and other access methods

in-process shared library

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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.

User concepts

Access control

Identity management, authentication, and access control

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

yes

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 Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Share this page