DBMS > Elasticsearch vs. Google Cloud Datastore vs. Kyligence Enterprise vs. SAP HANA

System Properties Comparison Elasticsearch vs. Google Cloud Datastore vs. Kyligence Enterprise vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A distributed analytics engine for big data, built on top of Apache Kylin

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

Primary database model

Search engine

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.elastic.co/elasticsearch

cloud.google.com/datastore

kyligence.io/kyligence-enterprise

www.sap.com/products/hana.html

Technical documentation

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

cloud.google.com/datastore/docs

help.sap.com/hana

Developer

Elastic

Google

Kyligence, Inc.

SAP

Initial release

2010

2008

2016

2010

Current release

8.6, January 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Elastic License

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

All OS with a Java VM

hosted

Linux

Appliance or cloud-service

Data scheme

schema-free

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

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (GQL)

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

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

Server-side scripts

Stored procedures

yes

using Google App Engine

SQLScript, R

Triggers

yes

by using the 'percolation' feature

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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

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

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.

Memcached and Redis integration

yes

User concepts

Access control

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.