DBMS > EXASOL vs. Google Cloud Datastore vs. Manticore Search vs. OpenEdge vs. Snowflake

System Properties Comparison EXASOL vs. Google Cloud Datastore vs. Manticore Search vs. OpenEdge vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Application development environment with integrated database management system

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.exasol.com

cloud.google.com/datastore

manticoresearch.com

www.progress.com/openedge

www.snowflake.com

Technical documentation

www.exasol.com/resources

cloud.google.com/datastore/docs

manual.manticoresearch.com

documentation.progress.com/output/ua/OpenEdge_latest

docs.snowflake.net/manuals/index.html

Developer

Exasol

Google

Manticore Software

Progress Software Corporation

Snowflake Computing Inc.

Initial release

2000

2008

2017

1984

2014

Current release

6.0, February 2023

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

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

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

schema-free

Fixed schema

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

yes, details here

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like query language

yes

close to SQL 92

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Progress proprietary ABL (Advanced Business Language)

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

user defined functions

yes

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

since Version 11.4

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Synchronous replication based on Galera library

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups

Users with fine-grained authorization concept, user roles and pluggable authentication

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.