DBMS > Apache Impala vs. EJDB vs. FatDB vs. Manticore Search

System Properties Comparison Apache Impala vs. EJDB vs. FatDB vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Analytic DBMS for Hadoop

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Primary database model

Relational DBMS

Document store

Document store
Key-value store

Search engine

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	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	0.23
Rank	#317	Overall
	#21	Search engines

Website

impala.apache.org

github.com/Softmotions/ejdb

manticoresearch.com

Technical documentation

impala.apache.org/impala-docs.html

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

manual.manticoresearch.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Softmotions

FatCloud

Manticore Software

Initial release

2013

2012

2017

Current release

4.1.0, June 2022

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2

commercial

Open Source

GPL version 2

Cloud-based only

Only available as a cloud service

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

Windows

FreeBSD
Linux
macOS
Windows

Data scheme

yes

schema-free

Fixed schema

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

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

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

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like DML and DDL statements

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

JDBC
ODBC

in-process shared library

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

via applications

user defined functions

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

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.

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

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera Bringing Impala to AWS Cloud
28 November 2017, Datanami

Apache Doris just 'graduated': Why care about this SQL data warehouse
24 June 2022, InfoWorld

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

provided by Google News

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

TF-IDF in a nutshell. Understanding TF-IDF evolution in 5… | by Sergey Nikolaev
13 April 2020, Towards Data Science

provided by Google News

Share this page