DBMS > Google BigQuery vs. JaguarDB vs. Sphinx vs. Sqrrl

System Properties Comparison Google BigQuery vs. JaguarDB vs. Sphinx vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

cloud.google.com/bigquery

www.jaguardb.com

sphinxsearch.com

sqrrl.com

Technical documentation

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

sphinxsearch.com/docs

Developer

Google

DataJaguar, Inc.

Sphinx Technologies Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2010

2015

2001

2012

Current release

3.3 July 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

GPL version 2, commercial licence available

commercial

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

C++

the server part. Clients available in other languages

C++

Java

Server operating systems

hosted

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic updates per row, document, or graph entity

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.

yes

In-memory capabilities

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.