DBMS > EJDB vs. Google Cloud Datastore vs. TimesTen vs. Transbase

System Properties Comparison EJDB vs. Google Cloud Datastore vs. TimesTen vs. Transbase

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

In-Memory RDBMS compatible to Oracle

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/datastore

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

www.transaction.de/en/products/transbase.html

Technical documentation

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

cloud.google.com/datastore/docs

docs.oracle.com/database/timesten-18.1

www.transaction.de/en/products/transbase/features.html

Developer

Softmotions

Google

Oracle, TimesTen Performance Software, HP

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

Transaction Software GmbH

Initial release

2012

2008

1998

1987

Current release

11 Release 2 (11.2.2.8.0)

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

free development 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

C and C++

Server operating systems

server-less

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
macOS
Solaris
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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

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

C
C++
Java
PL/SQL

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

Multi-source replication
Source-replica 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.

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

ACID

yes

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

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

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

The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page