DBMS > Google BigQuery vs. GraphDB vs. IBM Db2 warehouse vs. LMDB

System Properties Comparison Google BigQuery vs. GraphDB vs. IBM Db2 warehouse vs. LMDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Cloud-based data warehousing service

A high performant, light-weight, embedded key-value database library

Primary database model

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	2.76
Rank	#99	Overall
	#8	Graph DBMS
	#4	RDF stores

Score	1.26
Rank	#162	Overall
	#73	Relational DBMS

Score	1.94
Rank	#120	Overall
	#20	Key-value stores

Website

cloud.google.com/bigquery

www.ontotext.com

www.ibm.com/products/db2/warehouse

www.symas.com/symas-embedded-database-lmdb

Technical documentation

cloud.google.com/bigquery/docs

graphdb.ontotext.com/documentation

www.lmdb.tech/doc

Social network pages

Developer

Google

Ontotext

IBM

Symas

Initial release

2010

2000

2014

2011

Current release

10.4, October 2023

0.9.32, January 2024

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

Open Source

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

Server operating systems

hosted

All OS with a Java VM
Linux
OS X
Windows

hosted

Linux
Unix
Windows

Data scheme

yes

schema-free and OWL/RDFS-schema support; RDF shapes

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.

Import/export of XML data possible

Secondary indexes

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

yes

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

APIs and other access methods

RESTful HTTP/JSON API

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

.NET Client API
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

well-defined plugin interfaces; JavaScript server-side extensibility

PL/SQL, SQL PL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

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

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

Google Cloud Identity & Access Management (IAM)

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

GraphDB in Action: Using Semantics To Push The Envelope Of Software Engineering, Machine Learning, and E-Health Domains
11 September 2024

Accelerating End-to-end Knowledge Graph Solutions with Ontotext’s LinkedLifeData Inventory: The Case of Target Discovery
30 August 2024

Using Entity Linking to Turn Your Graph into a Knowledge Graph
23 August 2024

Considerations to Creating a Graph Center of Excellence: 5 Elements to Ensure Success
22 August 2024

The Power of Knowledge Graphs – A Chat with Perfect Memory and Ontotext
16 August 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.