DBMS > eXtremeDB vs. Google Cloud Datastore vs. Quasardb vs. SAP HANA

System Properties Comparison eXtremeDB vs. Google Cloud Datastore vs. Quasardb vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Natively in-memory DBMS with options for persistency, high-availability and clustering

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

Distributed, high-performance timeseries database

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

Primary database model

Relational DBMS
Time Series DBMS

Document store

Time Series DBMS

Relational DBMS

Secondary database models

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.80
Rank	#214	Overall
	#99	Relational DBMS
	#18	Time Series DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.mcobject.com

cloud.google.com/datastore

quasar.ai

www.sap.com/products/hana.html

Technical documentation

www.mcobject.com/docs/extremedb.htm

cloud.google.com/datastore/docs

doc.quasar.ai/master

help.sap.com/hana

Developer

McObject

Google

quasardb

SAP

Initial release

2001

2008

2009

2010

Current release

8.2, 2021

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C and C++

C++

Server operating systems

AIX
HP-UX
Linux
macOS
Solaris
Windows

hosted

BSD
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

integer and binary

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.

support of XML interfaces available

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

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

HTTP API

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
Lua
Python
Scala

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

using Google App Engine

SQLScript, R

Triggers

yes

by defining events

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning / sharding

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication using Paxos

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

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

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

Optimistic (MVCC) and pessimistic (locking) strategies available

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

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

Cryptographically strong user authentication and audit trail

yes

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» more

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.