DBMS > AllegroGraph vs. Google BigQuery vs. Microsoft Azure AI Search vs. Sphinx vs. Warp 10

System Properties Comparison AllegroGraph vs. Google BigQuery vs. Microsoft Azure AI Search vs. Sphinx vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

Large scale data warehouse service with append-only tables

Search-as-a-service for web and mobile app development

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Spatial DBMS

Vector DBMS

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

Score	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

allegrograph.com

cloud.google.com/bigquery

azure.microsoft.com/en-us/services/search

sphinxsearch.com

www.warp10.io

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

cloud.google.com/bigquery/docs

learn.microsoft.com/en-us/azure/search

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Franz Inc.

Google

Microsoft

Sphinx Technologies Inc.

SenX

Initial release

2004

2010

2015

2001

2015

Current release

8.0, December 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 2.0

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++

Java

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

RDF schemas

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.

bulk load of XML files possible

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API
SPARQL

RESTful HTTP/JSON API

RESTful HTTP API

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

user defined functions

in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

none

Sharding

Implicit feature of the cloud service

Sharding

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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.

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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

Google Cloud Identity & Access Management (IAM)

yes

using Azure authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

News

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

Allegro CL v11 – Now Available! – The Neuro-Symbolic AI Programming Platform
8 January 2024

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.