DBMS > Drizzle vs. Lovefield vs. Solr vs. SQLite

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

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.

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

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

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

google.github.io/lovefield

solr.apache.org

www.sqlite.org

Technical documentation

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

solr.apache.org/resources.html

www.sqlite.org/docs.html

Developer

Drizzle project, originally started by Brian Aker

Google

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2008

2014

2006

2000

Current release

7.2.4, September 2012

2.1.12, February 2017

9.5.0, February 2024

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache Version 2

Open Source

Public Domain

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)

server-less

Data scheme

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

via JavaScript builder pattern

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

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

Java plugins

Triggers

hooks for callbacks inside the server can be used.

Using read-only observers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.