DBMS > 4D vs. Atos Standard Common Repository vs. Google Cloud Spanner vs. searchxml

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Google Cloud Spanner vs. searchxml

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Native XML DBMS
Search engine

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	2.89
Rank	#105	Overall
	#53	Relational DBMS

Score	0.01
Rank	#386	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

www.4d.com

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

cloud.google.com/spanner

www.searchxml.net/category/products

Technical documentation

developer.4d.com

cloud.google.com/spanner/docs

www.searchxml.net/support/handouts

Developer

4D, Inc

Atos Convergence Creators

Google

informationpartners gmbh

Initial release

1984

2016

2017

2015

Current release

v20, April 2023

1703

1.0

License

Commercial or Open Source

commercial

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

C++

Server operating systems

OS X
Windows

Linux

hosted

Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

yes

Query statements complying to ANSI 2011

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

Go
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication with 3 replicas for regional instances.

yes

sychronisation to multiple collections

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

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Strict serializable isolation

multiple readers, single writer

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)

Domain, group and role-based access control at the document level and for application services

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 Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

Google Cloud Spanner competes directly with Amazon DynamoDB
12 October 2023, Techzine Europe

provided by Google News

Share this page