DBMS > Elasticsearch vs. Google Cloud Datastore vs. NSDb vs. RocksDB

System Properties Comparison Elasticsearch vs. Google Cloud Datastore vs. NSDb vs. RocksDB

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.elastic.co/elasticsearch

cloud.google.com/datastore

nsdb.io

rocksdb.org

Technical documentation

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

cloud.google.com/datastore/docs

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

Developer

Elastic

Google

Facebook, Inc.

Initial release

2010

2008

2017

2013

Current release

8.6, January 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

Apache Version 2.0

Open Source

BSD

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

Java, Scala

C++

Server operating systems

All OS with a Java VM

hosted

Linux
macOS

Linux

Data scheme

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

gRPC
HTTP REST
WebSocket

C++ API
Java API

Supported programming languages

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

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

Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

yes

by using the 'percolation' feature

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

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

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.

Eventual 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

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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)

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.