DBMS > Apache Drill vs. EJDB vs. mSQL vs. NSDb vs. OrigoDB

System Properties Comparison Apache Drill vs. EJDB vs. mSQL vs. NSDb vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

drill.apache.org

github.com/Softmotions/ejdb

hughestech.com.au/products/msql

nsdb.io

origodb.com

Technical documentation

drill.apache.org/docs

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

nsdb.io/Architecture

origodb.com/docs

Developer

Apache Software Foundation

Softmotions

Hughes Technologies

Robert Friberg et al

Initial release

2012

1994

2017

2009

under the name LiveDB

Current release

1.20.3, January 2023

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2

commercial

free licenses can be provided

Open Source

Apache Version 2.0

Open Source

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, Scala

Server operating systems

Linux
OS X
Windows

server-less

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
macOS

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

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 be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

in-process shared library

JDBC
ODBC

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Supported programming languages

C++

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

C
C++
Delphi
Java
Perl
PHP
Tcl

Java
Scala

.Net

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

Using Apache Lucene

yes

Write ahead log

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Role based authorization

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

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Using Apache Iceberg for Developing Modern Data Tables
3 October 2023, Open Source For You

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Apache Drill improves big data SQL query engine
31 August 2021, TechTarget

provided by Google News

Make Your MySQL Server More Secure With These 7 Steps - MUO
1 December 2022, MakeUseOf

Writing a Web Service in Perl
9 July 2003, PCQuest

Higher Education PS rules out ghost students before PAC - Zambia
29 November 2018, diggers.news

provided by Google News

Share this page