DBMS > Derby vs. Google BigQuery vs. JaguarDB vs. Machbase Neo vs. Sphinx

System Properties Comparison Derby vs. Google BigQuery vs. JaguarDB vs. Machbase Neo vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

TimeSeries DBMS for AIoT and BigData

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Time Series DBMS

Search engine

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

db.apache.org/derby

cloud.google.com/bigquery

www.jaguardb.com

machbase.com

sphinxsearch.com

Technical documentation

db.apache.org/derby/manuals/index.html

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

machbase.com/dbms

sphinxsearch.com/docs

Developer

Apache Software Foundation

Google

DataJaguar, Inc.

Machbase

Sphinx Technologies Inc.

Initial release

1997

2010

2015

2013

2001

Current release

10.17.1.0, November 2023

3.3 July 2023

V8.0, August 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

GPL V3.0

commercial

free test version available

Open Source

GPL version 2, commercial licence available

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.

Implementation language

Java

C++

the server part. Clients available in other languages

C++

Server operating systems

All OS with a Java VM

hosted

Linux

Linux
macOS
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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

full-text index on all search fields

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Proprietary protocol

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

simple password-based access control

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.