DBMS > EsgynDB vs. EXASOL vs. Google BigQuery vs. Graph Engine vs. Manticore Search

System Properties Comparison EsgynDB vs. EXASOL vs. Google BigQuery vs. Graph Engine vs. Manticore Search

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Graph DBMS
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	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

www.esgyn.cn

www.exasol.com

cloud.google.com/bigquery

www.graphengine.io

manticoresearch.com

Technical documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

manual.manticoresearch.com

Developer

Esgyn

Exasol

Google

Microsoft

Manticore Software

Initial release

2015

2000

2010

2017

Current release

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

GPL version 2

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

.NET and C

C++

Server operating systems

Linux

hosted

.NET

FreeBSD
Linux
macOS
Windows

Data scheme

yes

Fixed schema

Typing

predefined data types such as float or date

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

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.