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

System Properties Comparison Apache Kylin 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

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.14
Rank	#171	Overall
	#77	Relational DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Website

kylin.apache.org

github.com/Softmotions/ejdb

manticoresearch.com

Technical documentation

kylin.apache.org/docs

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

manual.manticoresearch.com

Developer

Apache Software Foundation, originally contributed from eBay Inc

Softmotions

FatCloud

Manticore Software

Initial release

2015

2012

2017

Current release

3.1.0, July 2020

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Java

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

ANSI SQL for queries (using Apache Calcite)

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

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

via applications

user defined functions

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

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

Overhauling Apache Kylin for the cloud
18 November 2021, InfoWorld

Migrating from ClickHouse to Apache Doris: Boosting OLAP Performance
9 October 2023, hackernoon.com

eBay’s Kylin Becomes a Top-Level Apache Open Source Project
9 December 2015, eBay Inc.

Distributed OLAPer Kyligence accelerates core engine, adds real-time data support
10 August 2021, Blocks & Files

How Kyligence Cloud uses Amazon EMR Serverless to simplify OLAP
9 November 2022, AWS Blog

provided by Google News

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

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

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

Highlighting in Search Results
24 May 2020, hackernoon.com

40 Stories To Learn About Elasticsearch
27 April 2023, hackernoon.com

provided by Google News

Share this page