DBMS > Amazon Neptune vs. Atos Standard Common Repository vs. ClickHouse vs. Elasticsearch vs. Lovefield

System Properties Comparison Amazon Neptune vs. Atos Standard Common Repository vs. ClickHouse vs. Elasticsearch vs. Lovefield

Editorial information provided by DB-Engines

Name

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

Description

Fast, reliable graph database built for the cloud

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS
Vector DBMS

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

aws.amazon.com/neptune

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

clickhouse.com

www.elastic.co/elasticsearch

google.github.io/lovefield

Technical documentation

aws.amazon.com/neptune/developer-resources

clickhouse.com/docs

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Amazon

Atos Convergence Creators

Clickhouse Inc.

Elastic

Google

Initial release

2017

2016

2010

2014

Current release

1703

v24.4.2.141-stable, June 2024

8.6, January 2023

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Elastic License

Open Source

Apache 2.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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

Java

C++

Java

JavaScript

Server operating systems

hosted

Linux

FreeBSD
Linux
macOS

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

LDAP

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages with LDAP bindings

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

Memcached and Redis integration

yes

using MemoryDB

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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.