DBMS > Drizzle vs. PostGIS vs. Vertica

System Properties Comparison Drizzle vs. PostGIS vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spatial extension of PostgreSQL

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Column oriented

Secondary database models

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	19.44
Rank	#29	Overall
	#1	Spatial DBMS

Score	9.53
Rank	#42	Overall
	#26	Relational DBMS

Website

postgis.net

www.vertica.com

Technical documentation

postgis.net/documentation

vertica.com/documentation

Developer

Drizzle project, originally started by Brian Aker

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2008

2005

Current release

7.2.4, September 2012

3.4.2, February 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL v2.0

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

Data scheme

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

Secondary indexes

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

with proprietary extensions

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

JDBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

C
C++
Java
PHP

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

hooks for callbacks inside the server can be used.

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

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

Concurrency

Support for concurrent manipulation of data

yes

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

based on PostgreSQL

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

New browser-based query editor for OpenText Core Analytics Database accelerates and simplifies querying your data
25 November 2024, blogs.opentext.com

Vertica on Kubernetes
20 June 2024, blogs.opentext.com

Querying a Vertica data source in Amazon Athena using the Athena Federated Query SDK
11 February 2021, AWS Blog

Solving Big Data Challenges with Data Science at Uber
20 March 2019, Uber

VAST links arms with Vertica for fast analytics
19 April 2022, Blocks and Files

provided by Google News

Share this page