DBMS > EsgynDB vs. LevelDB vs. NSDb vs. SAP HANA

System Properties Comparison EsgynDB vs. LevelDB vs. NSDb vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.esgyn.cn

github.com/google/leveldb

nsdb.io

www.sap.com/products/hana.html

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

nsdb.io/Architecture

help.sap.com/hana

Developer

Esgyn

Google

SAP

Initial release

2015

2011

2017

2010

Current release

1.23, February 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

C++

Java, Scala

Server operating systems

Linux

Illumos
Linux
OS X
Windows

Linux
macOS

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Java
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

none

yes

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

Using Apache Lucene

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.