DBMS > 4D vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. SiteWhere

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Time Series DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Website

www.4d.com

atos.net/en/convergence-creators/portfolio/standard-common-repository

cloud.google.com/datastore

github.com/sitewhere/sitewhere

Technical documentation

developer.4d.com

cloud.google.com/datastore/docs

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Atos Convergence Creators

Google

SiteWhere

Initial release

1984

2016

2008

2010

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

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

Server operating systems

OS X
Windows

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

optional

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

SQL-like query language (GQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

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

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication using Paxos

selectable replication factor

based on HBase

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 configuration

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

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

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

LDAP bind authentication

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

Users with fine-grained authorization concept

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

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

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

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

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page