DBMS > EJDB vs. Google Cloud Datastore vs. InfluxDB vs. SAP HANA

System Properties Comparison EJDB vs. Google Cloud Datastore vs. InfluxDB vs. SAP HANA

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

DBMS for storing time series, events and metrics

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with GEO package

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial 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	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/datastore

www.influxdata.com/products/influxdb-overview

www.sap.com/products/hana.html

Technical documentation

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

cloud.google.com/datastore/docs

docs.influxdata.com/influxdb

help.sap.com/hana

Developer

Softmotions

Google

SAP

Initial release

2012

2008

2013

2010

Current release

2.7.6, April 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

MIT-License; commercial enterprise version available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Server operating systems

server-less

hosted

Linux
OS X

through Homebrew

Appliance or cloud-service

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

Numeric data and Strings

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)

SQL-like query language

yes

APIs and other access methods

in-process shared library

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

HTTP API
JSON over UDP

JDBC
ODBC

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

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

using Google App Engine

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

in enterprise version only

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

selectable replication factor

in enterprise version only

yes

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

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

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

Depending on used storage engine

yes

User concepts

Access control

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

simple rights management via user accounts

yes

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

Efficiency Unleashed: Streamlining Workflows with the InfluxDB Management API
23 May 2024

What is DevRel at InfluxData
21 May 2024

An Introductory Guide to Grafana Alerts
16 May 2024

What to Expect When You’re Expecting InfluxDB: A Guide
14 May 2024

Introduction to Apache Iceberg
9 May 2024

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.