DBMS > Google BigQuery vs. LMDB vs. OpenEdge vs. TigerGraph vs. TimescaleDB

System Properties Comparison Google BigQuery vs. LMDB vs. OpenEdge vs. TigerGraph vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Application development environment with integrated database management system

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

cloud.google.com/bigquery

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

www.progress.com/openedge

www.tigergraph.com

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

www.lmdb.tech/doc

documentation.progress.com/output/ua/OpenEdge_latest

docs.tigergraph.com

docs.timescale.com

Developer

Google

Symas

Progress Software Corporation

Timescale

Initial release

2010

2011

1984

2017

Current release

0.9.32, January 2024

OpenEdge 12.2, March 2020

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

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

Server operating systems

hosted

Linux
Unix
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language (GSQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
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

Progress proprietary ABL (Advanced Business Language)

C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

since Version 11.4

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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)

Users and groups

Role-based access control

fine grained access rights according to SQL-standard

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.