DBMS > EJDB vs. Google Cloud Datastore vs. Newts vs. XTDB

System Properties Comparison EJDB vs. Google Cloud Datastore vs. Newts vs. XTDB

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)

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

Time Series DBMS based on Cassandra

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Time Series DBMS

Document store

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/Softmotions/ejdb

cloud.google.com/datastore

opennms.github.io/newts

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

cloud.google.com/datastore/docs

github.com/OpenNMS/newts/wiki

www.xtdb.com/docs

Developer

Softmotions

Google

OpenNMS Group

Juxt Ltd.

Initial release

2012

2008

2014

2019

Current release

1.19, September 2021

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache 2.0

Open Source

MIT License

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

Clojure

Server operating systems

server-less

hosted

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, details here

yes

yes, extensible-data-notation format

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)

limited SQL, making use of Apache Calcite

APIs and other access methods

in-process shared library

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

HTTP REST
Java API

HTTP REST
JDBC

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

yes, each node contains all data

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

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 Platform: Professional Data Engineer certification prep
11 June 2024, O'Reilly Media

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
4 June 2024, TechRadar

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

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

provided by Google News

Share this page