DBMS > Axibase vs. OpenSearch vs. Vertica

System Properties Comparison Axibase vs. OpenSearch vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

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

Time Series DBMS

Search engine

Relational DBMS

Column oriented

Secondary database models

Vector DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	15.65
Rank	#38	Overall
	#4	Search engines

Score	11.40
Rank	#43	Overall
	#27	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/opensearch-project
opensearch.org

www.vertica.com

Technical documentation

opensearch.org/docs/latest

vertica.com/documentation

Developer

Axibase Corporation

Amazon Web Services

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2013

2021

2005

Current release

15585

2.5.0, January 2023

12.0.3, January 2023

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache Version 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

C++

Server operating systems

Linux

All OS with a Java VM

Linux

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

short, integer, long, float, double, decimal, string

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

All search fields are automatically indexed

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

SQL

Support of SQL

SQL-like query language

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

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

Java API
RESTful HTTP/JSON API

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

character-based, interactive, front-end utility

Supported programming languages

Go
Java
PHP
Python
R
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

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

Server-side scripts

Stored procedures

yes

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

by using the 'percolation' feature

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

Cost-based models and subscription-based models are both available. One license is...
» more

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.