DBMS > BigObject vs. Microsoft Azure SQL Database vs. MySQL vs. Solr

System Properties Comparison BigObject vs. Microsoft Azure SQL Database vs. MySQL vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

bigobject.io

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

solr.apache.org

Technical documentation

docs.bigobject.io

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

solr.apache.org/resources.html

Developer

BigObject, Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

2015

2010

1995

2006

Current release

V12

8.3.0, January 2024

9.5.0, February 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

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

Data scheme

yes

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

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

SQL-like DML and DDL statements

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

Lua

Transact SQL

yes

proprietary syntax

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

yes

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

yes

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.