DBMS > Kdb vs. OpenSearch vs. searchxml vs. TerarkDB

System Properties Comparison Kdb vs. OpenSearch vs. searchxml vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

DBMS for structured and unstructured content wrapped with an application server

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Time Series DBMS
Vector DBMS

Search engine

Native XML DBMS
Search engine

Key-value store

Secondary database models

Relational DBMS

Vector DBMS

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

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

kx.com

github.com/opensearch-project
opensearch.org

www.searchxml.net/category/products

github.com/bytedance/terarkdb

Technical documentation

code.kx.com

opensearch.org/docs/latest

www.searchxml.net/support/handouts

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Kx Systems, a division of First Derivatives plc

Amazon Web Services

informationpartners gmbh

ByteDance, originally Terark

Initial release

2000

kdb was released 2000, kdb+ in 2003

2021

2015

2016

Current release

3.6, May 2018

2.5.0, January 2023

1.0

License

Commercial or Open Source

commercial

free 32-bit version

Open Source

Apache Version 2.0

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

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
OS X
Solaris
Windows

All OS with a Java VM

Windows

Data scheme

yes

schema-free

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

schema-free

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

table attribute 'grouped'

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (q)

SQL-like query language

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

Java API
RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

C++ API
Java API

Supported programming languages

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C++

most other programming languages supported via APIs

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

Triggers

yes

with views

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

multiple readers, single writer

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.

yes

User concepts

Access control

rights management via user accounts

Domain, group and role-based access control at the document level and for application services

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

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

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

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

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

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

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

The OpenSearch Project offers open source software licensed under Apache License...
» 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.