DBMS > Microsoft Azure AI Search vs. Riak TS vs. Solr vs. SQLite

System Properties Comparison Microsoft Azure AI Search vs. Riak TS vs. Solr vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Search-as-a-service for web and mobile app development

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Vector DBMS

Spatial DBMS

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

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

azure.microsoft.com/en-us/services/search

solr.apache.org

www.sqlite.org

Technical documentation

learn.microsoft.com/en-us/azure/search

www.tiot.jp/riak-docs/riak/ts/latest

solr.apache.org/resources.html

www.sqlite.org/docs.html

Developer

Microsoft

Open Source, formerly Basho Technologies

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2015

2006

2000

Current release

3.0.0, September 2022

9.6.0, April 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

Java

Server operating systems

hosted

Linux
OS X

All OS with a Java VM

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

server-less

Data scheme

yes

schema-free

yes

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

yes

dynamic column types

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes

not rigid because of 'dynamic typing' concept.

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

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes, limited

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Java
JavaScript
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Erlang

Java plugins

Triggers

yes

pre-commit hooks and post-commit hooks

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes

using Azure authentication

yes

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.