DBMS > 4D vs. Amazon CloudSearch vs. Atos Standard Common Repository vs. SAP HANA vs. Splunk

System Properties Comparison 4D vs. Amazon CloudSearch vs. Atos Standard Common Repository vs. SAP HANA vs. Splunk

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

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

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

Analytics Platform for Big Data

Primary database model

Relational DBMS

Search engine

Document store
Key-value store

Relational DBMS

Search engine

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

Score	1.87
Rank	#140	Overall
	#12	Search engines

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

www.4d.com

aws.amazon.com/cloudsearch

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

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/cloudsearch

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

4D, Inc

Amazon

Atos Convergence Creators

SAP

Splunk Inc.

Initial release

1984

2012

2016

2010

2003

Current release

v20, April 2023

1703

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

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

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

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

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

close to SQL 92

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

HTTP API

LDAP

JDBC
ODBC

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

automatic partitioning across Amazon Search Instance as required

Sharding

cell division

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

managed transparently by AWS

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

authentication via encrypted signatures

LDAP bind authentication

yes

Access rights for users and roles

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.