DBMS > Lovefield vs. Solr vs. Splunk vs. Tkrzw

System Properties Comparison Lovefield vs. Solr vs. Splunk vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

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

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Search engine

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	86.45
Rank	#14	Overall
	#2	Search engines

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

Website

google.github.io/lovefield

solr.apache.org

www.splunk.com

dbmx.net/tkrzw

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

solr.apache.org/resources.html

docs.splunk.com/Documentation/Splunk

Developer

Google

Apache Software Foundation

Splunk Inc.

Mikio Hirabayashi

Initial release

2014

2006

2003

2020

Current release

2.1.12, February 2017

9.6.0, April 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0

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

JavaScript

Java

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

All OS with a Java VM

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

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

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

yes

schema-free

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

Solr Parallel SQL Interface

Splunk Search Processing Language for search commands

APIs and other access methods

Java API
RESTful HTTP/JSON API

HTTP REST

Supported programming languages

JavaScript

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

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Java plugins

yes

Triggers

Using read-only observers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

using specific database classes

User concepts

Access control

yes

Access rights for users and roles

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

Elasticsearch replaced Solr as the most popular search engine
12 January 2016, Paul Andlinger

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

SOLR-led walkout demands better conditions for Compass workers
27 February 2024, Daily Northwestern

(SOLR) Technical Pivots with Risk Controls
28 April 2024, Stock Traders Daily

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

SOLR hosts teach-in of labor movements at Northwestern
28 January 2024, Daily Northwestern

Top 5 stock gainers and losers: SOLR.V, GRSL.V, ANON.C
21 November 2023, Equity.Guru

provided by Google News

Share this page