DBMS > EJDB vs. Google Cloud Datastore vs. Newts vs. SwayDB vs. TimesTen

System Properties Comparison EJDB vs. Google Cloud Datastore vs. Newts vs. SwayDB vs. TimesTen

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

In-Memory RDBMS compatible to Oracle

Primary database model

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

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	0.04
Rank	#373	Overall
	#57	Key-value stores

Score	1.35
Rank	#165	Overall
	#75	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/datastore

opennms.github.io/newts

swaydb.simer.au

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

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

cloud.google.com/datastore/docs

github.com/OpenNMS/newts/wiki

docs.oracle.com/database/timesten-18.1

Developer

Softmotions

Google

OpenNMS Group

Simer Plaha

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2008

2014

2018

1998

Current release

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache 2.0

Open Source

GNU Affero GPL V3.0

commercial

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

Scala

Server operating systems

server-less

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
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)

yes

APIs and other access methods

in-process shared library

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

HTTP REST
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

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

Java
Kotlin
Scala

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

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

none

Multi-source replication
Source-replica replication

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

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

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 is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, netapp.com

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

provided by Google News

Farewell, Froggy: The Age of Ribbit Is Nearing an End
25 May 2013, Mother Jones

provided by Google News

Share this page