DBMS > 4D vs. Greenplum vs. Postgres-XL vs. Snowflake vs. TimesTen

System Properties Comparison 4D vs. Greenplum vs. Postgres-XL vs. Snowflake vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

In-Memory RDBMS compatible to Oracle

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	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	1.35
Rank	#165	Overall
	#75	Relational DBMS

Website

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

developer.4d.com

docs.greenplum.org

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

docs.oracle.com/database/timesten-18.1

Developer

4D, Inc

Pivotal Software Inc.

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

1984

2005

2014

since 2012, originally named StormDB

2014

1998

Current release

v20, April 2023

7.0.0, September 2023

10 R1, October 2018

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Mozilla public license

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

Server operating systems

OS X
Windows

Linux

Linux
macOS

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

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

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

yes

XML type, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

distributed, parallel query execution

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

4D proprietary IDE
PHP

C
Java
Perl
Python
R

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

user defined functions

PL/SQL

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

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

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

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

fine grained access rights according to SQL-standard

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.