DBMS > EsgynDB vs. JaguarDB vs. SAP HANA vs. SWC-DB

System Properties Comparison EsgynDB vs. JaguarDB vs. SAP HANA vs. SWC-DB

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

Performant, highly scalable DBMS for AI and IoT applications

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

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Wide column store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Time Series DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#14	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

www.esgyn.cn

www.jaguardb.com

www.sap.com/products/hana.html

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.jaguardb.com/support.html

help.sap.com/hana

Developer

Esgyn

DataJaguar, Inc.

SAP

Alex Kashirin

Initial release

2015

2010

2020

Current release

3.3 July 2023

2.0 SPS07 (April 4, 2023), April 2023

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Open Source

GPL V3

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++

the server part. Clients available in other languages

C++

Server operating systems

Linux

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C++

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication

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

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

rights management via user accounts

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.