DBMS > IBM Db2 vs. RocksDB vs. Solr vs. Teradata Aster

System Properties Comparison IBM Db2 vs. RocksDB vs. Solr vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Common in IBM host environments, 2 different versions for host and Windows/Linux

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A widely used distributed, scalable search engine based on Apache Lucene

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Search engine

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

www.ibm.com/products/db2

rocksdb.org

solr.apache.org

Technical documentation

www.ibm.com/docs/en/db2

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

IBM

Facebook, Inc.

Apache Software Foundation

Teradata

Initial release

1983

host version

2013

2006

2005

Current release

12.1, October 2016

9.2.1, May 2024

9.6.1, May 2024

License

Commercial or Open Source

commercial

free version is available

Open Source

BSD

Open Source

Apache Version 2

commercial

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.

Implementation language

C and C++

C++

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

in Aster File Store

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

yes

APIs and other access methods

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

C++ API
Java API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

Java plugins

R packages

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

yes

optimistic locking

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.