DBMS > Apache Impala vs. EJDB vs. Manticore Search vs. Snowflake vs. STSdb

System Properties Comparison Apache Impala vs. EJDB vs. Manticore Search vs. Snowflake vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Multi-storage database for search, including full-text search.

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Document store

Time Series DBMS

using the Manticore Columnar Library

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

impala.apache.org

github.com/Softmotions/ejdb

manticoresearch.com

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

impala.apache.org/impala-docs.html

github.com/Softmotions/ejdb/blob/master/README.md

manual.manticoresearch.com

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Softmotions

Manticore Software

Snowflake Computing Inc.

STS Soft SC

Initial release

2013

2012

2017

2014

2011

Current release

4.1.0, June 2022

6.0, February 2023

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2

Open Source

GPL version 2

commercial

Open Source

GPLv2, commercial license available

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++

Server operating systems

Linux

server-less

FreeBSD
Linux
macOS
Windows

hosted

Windows

Data scheme

yes

schema-free

Fixed schema

yes

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

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

primitive types and user defined types (classes)

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

in-process shared library

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Synchronous replication based on Galera library

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.