DBMS > Greenplum vs. jBASE vs. PlanetScale vs. SQLite

System Properties Comparison Greenplum vs. jBASE vs. PlanetScale vs. SQLite

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.

A robust multi-value DBMS comprising development tools and middleware

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

greenplum.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

planetscale.com

www.sqlite.org

Technical documentation

docs.greenplum.org

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

planetscale.com/docs

www.sqlite.org/docs.html

Developer

Pivotal Software Inc.

Rocket Software (formerly Zumasys)

PlanetScale

Dwayne Richard Hipp

Initial release

2005

1991

2020

2000

Current release

7.0.0, September 2023

5.7

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Server operating systems

Linux

AIX
Linux
Windows

Docker
Linux
macOS

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
Java
Perl
Python
R

.Net
Basic
Jabbascript
Java

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

none

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

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

via file-system locks

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

Access rights can be defined down to the item level

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.