DBMS > GBase vs. Greenplum vs. Lovefield vs. Vitess

System Properties Comparison GBase vs. Greenplum vs. Lovefield vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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.

Embeddable relational database for web apps written in pure JavaScript

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.gbase.cn

greenplum.org

google.github.io/lovefield

vitess.io

Technical documentation

docs.greenplum.org

github.com/google/lovefield/blob/master/docs/spec_index.md

vitess.io/docs

Developer

General Data Technology Co., Ltd.

Pivotal Software Inc.

Google

The Linux Foundation, PlanetScale

Initial release

2004

2005

2014

2013

Current release

GBase 8a, GBase 8s, GBase 8c

7.0.0, September 2023

2.1.12, February 2017

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, Java, Python

JavaScript

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Docker
Linux
macOS

Data scheme

yes

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.

yes

since Version 4.2

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

yes

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
Java
Perl
Python
R

JavaScript

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

Multi-source replication
Source-replica replication

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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

1. Introducing the Greenplum Database - Data Warehousing with Greenplum [Book]
6 December 2018, oreilly.com

VMware Greenplum on AWS: Parallel Postgres for Enterprise Analytics at Scale | Amazon Web Services
9 September 2019, AWS Blog

RSA: EMC integrates Hadoop with Greenplum database
26 February 2013, DatacenterDynamics

Greenplum 6 ventures outside the analytic box | ZDNET
19 March 2019, ZDNet

Greenplum 6 review: Jack of all trades, master of some
7 November 2019, InfoWorld

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page