DBMS > Greenplum vs. Manticore Search vs. SingleStore vs. Snowflake

System Properties Comparison Greenplum vs. Manticore Search vs. SingleStore vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.greenplum.org

manual.manticoresearch.com

docs.singlestore.com

docs.snowflake.net/manuals/index.html

Developer

Pivotal Software Inc.

Manticore Software

SingleStore Inc.

Snowflake Computing Inc.

Initial release

2005

2017

2013

2014

Current release

7.0.0, September 2023

6.0, February 2023

8.5, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2

commercial

free developer edition available

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

C++, Go

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

Linux

64 bit version required

hosted

Data scheme

yes

Fixed schema

yes

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

Typing

predefined data types such as float or date

yes

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.

yes

since Version 4.2

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

yes

but no triggers and foreign keys

yes

APIs and other access methods

JDBC
ODBC

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

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

user defined functions

Triggers

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

Sharding

hash partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication based on Galera library

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

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

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups and roles

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.