DBMS > Apache Drill vs. GeoMesa vs. Vertica

System Properties Comparison Apache Drill vs. GeoMesa vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Document store
Relational DBMS

Spatial DBMS

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	1.95
Rank	#124	Overall
	#22	Document stores
	#58	Relational DBMS

Score	0.80
Rank	#208	Overall
	#4	Spatial DBMS

Score	9.96
Rank	#42	Overall
	#26	Relational DBMS

Website

drill.apache.org

www.geomesa.org

www.vertica.com

Technical documentation

drill.apache.org/docs

www.geomesa.org/documentation/stable/user/index.html

vertica.com/documentation

Developer

Apache Software Foundation

CCRi and others

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2014

2005

Current release

1.20.3, January 2023

5.0.0, May 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache License 2.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

Scala

C++

Server operating systems

Linux
OS X
Windows

Linux

Data scheme

schema-free

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.

Secondary indexes

yes

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

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

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

character-based, interactive, front-end utility

Supported programming languages

C++

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

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

depending on storage layer

User concepts

Access control

Depending on the underlying data source

yes

depending on the DBMS used for storage

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Apache Drill Adds New Data Formats
28 March 2022, iProgrammer

provided by Google News

Don’t Believe the Big Database Hype, Stonebraker Warns
8 July 2024, Datanami

Why HPE Vertica 8 is the best fit for businesses to create an analytics-driven enterprise
16 July 2024, AIM

What’s New in OpenText Vertica
25 July 2023, OpenText

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

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

provided by Google News

Share this page