DBMS > Drizzle vs. Lovefield vs. Solr vs. ToroDB

System Properties Comparison Drizzle vs. Lovefield vs. Solr vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Embeddable relational database for web apps written in pure JavaScript

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Search engine

Document store

Secondary database models

Spatial DBMS

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

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

google.github.io/lovefield

solr.apache.org

github.com/torodb/server

Technical documentation

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

solr.apache.org/resources.html

Developer

Drizzle project, originally started by Brian Aker

Google

Apache Software Foundation

8Kdata

Initial release

2008

2014

2006

2016

Current release

7.2.4, September 2012

2.1.12, February 2017

9.5.0, February 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache Version 2

Open Source

AGPL-V3

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++

JavaScript

Java

Server operating systems

FreeBSD
Linux
OS X

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)

All OS with a Java 7 VM

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

via JavaScript builder pattern

Solr Parallel SQL Interface

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

JavaScript

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

Server-side scripts

Stored procedures

Java plugins

Triggers

hooks for callbacks inside the server can be used.

Using read-only observers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

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

Recent citations in the news

Closing Bell: Solar Alliance Energy Inc flat on Tuesday (SOLR)
24 April 2024, The Globe and Mail

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

Closing Bell: Solar Alliance Energy Inc flat on Monday (SOLR)
23 April 2024, The Globe and Mail

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

Long Term Trading Analysis for (SOLR)
28 March 2024, Stock Traders Daily

provided by Google News

Share this page