DBMS > 4D vs. atoti vs. Google Cloud Datastore vs. Newts vs. SAP HANA

System Properties Comparison 4D vs. atoti vs. Google Cloud Datastore vs. Newts vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

Time Series DBMS based on Cassandra

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

Primary database model

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	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.4d.com

atoti.io

cloud.google.com/datastore

opennms.github.io/newts

www.sap.com/products/hana.html

Technical documentation

developer.4d.com

docs.atoti.io

cloud.google.com/datastore/docs

github.com/OpenNMS/newts/wiki

help.sap.com/hana

Developer

4D, Inc

ActiveViam

Google

OpenNMS Group

SAP

Initial release

1984

2008

2014

2010

Current release

v20, April 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free versions available

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

OS X
Windows

hosted

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

Multidimensional Expressions (MDX)

SQL-like query language (GQL)

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

HTTP REST
Java API

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

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

Java

Server-side scripts

Stored procedures

yes

Python

using Google App Engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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

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

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

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

Users and groups

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

yes

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.