DBMS > Amazon DocumentDB vs. EsgynDB vs. Snowflake vs. Solr

System Properties Comparison Amazon DocumentDB vs. EsgynDB vs. Snowflake vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/documentdb

www.esgyn.cn

www.snowflake.com

solr.apache.org

Technical documentation

aws.amazon.com/documentdb/resources

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

Esgyn

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2019

2015

2014

2006

Current release

9.6.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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

C++, Java

Java

Server operating systems

hosted

Linux

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

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

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC/ADO.Net

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Java plugins

Triggers

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

optimistic locking

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.