DBMS > Elasticsearch vs. IBM Cloudant vs. Netezza vs. Snowflake

System Properties Comparison Elasticsearch vs. IBM Cloudant vs. Netezza vs. Snowflake

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

Database as a Service offering based on Apache CouchDB

Data warehouse and analytics appliance part of IBM PureSystems

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Search engine

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.elastic.co/elasticsearch

www.ibm.com/products/cloudant

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

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

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Elastic

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Snowflake Computing Inc.

Initial release

2010

2000

2014

Current release

8.6, January 2023

License

Commercial or Open Source

Open Source

Elastic License

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

Erlang

Server operating systems

All OS with a Java VM

hosted

Linux

included in appliance

hosted

Data scheme

schema-free

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

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

similar concept for controling cloud resources

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
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

User concepts

Access control

Access rights for users can be defined per database

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable 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.