DBMS > Apache Kylin vs. EJDB

System Properties Comparison Apache Kylin vs. EJDB

Please select another system to include it in the comparison.

Our visitors often compare Apache Kylin and EJDB with MySQL, Google Cloud Bigtable and SQLite.

Editorial information provided by DB-Engines

Name

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)

Primary database model

Relational DBMS

Document store

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Website

kylin.apache.org

github.com/Softmotions/ejdb

Technical documentation

kylin.apache.org/docs

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

Developer

Apache Software Foundation, originally contributed from eBay Inc

Softmotions

Initial release

2015

2012

Current release

3.1.0, July 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

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

Server operating systems

Linux

server-less

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

in-process shared library

Supported programming languages

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

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

User concepts

Access control

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.

Share this page