DBMS > Apache Solr vs. EJDB vs. MySQL

System Properties Comparison Apache Solr vs. EJDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

Primary database model

Search engine

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	32.47
Rank	#24	Overall
	#3	Search engines

Score	0.14
Rank	#331	Overall
	#47	Document stores

Score	1003.76
Rank	#2	Overall
	#2	Relational DBMS

Website

solr.apache.org

github.com/Softmotions/ejdb

www.mysql.com

Technical documentation

solr.apache.org/resources.html

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

Developer

Apache Software Foundation

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2006

2012

1995

Current release

9.6.1, May 2024

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C and C++

Server operating systems

All OS with a Java VM

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

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes

string, integer, double, bool, date, object_id

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

Solr Parallel SQL Interface

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP/JSON API

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java plugins

yes

proprietary syntax

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
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

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

optimistic locking

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or 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.