DBMS > Google Cloud Bigtable vs. Oracle Berkeley DB vs. Redis vs. TDengine

System Properties Comparison Google Cloud Bigtable vs. Oracle Berkeley DB vs. Redis vs. TDengine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Widely used in-process key-value store

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Time Series DBMS and big data platform

Primary database model

Key-value store
Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Time Series DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Relational DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

cloud.google.com/bigtable

www.oracle.com/database/technologies/related/berkeleydb.html

redis.com
redis.io

github.com/taosdata/TDengine
tdengine.com

Technical documentation

cloud.google.com/bigtable/docs

docs.oracle.com/cd/E17076_05/html/index.html

docs.redis.com/latest/index.html
redis.io/docs

docs.tdengine.com

Developer

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

TDEngine, previously Taos Data

Initial release

2015

1994

2009

2019

Current release

18.1.40, May 2020

7.2.4, January 2024

3.0, August 2022

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

AGPL V3, also commercial editions 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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

with RediSQL module

Standard SQL with extensions for time-series applications

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
RESTful HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

only for the SQL API

publish/subscribe channels provide some trigger functionality; RedisGears

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

Can Typical Time-Series Databases Replace Data Historians?
8 May 2024

TDengine 3.3.0.0 Release Notes
7 May 2024

How to Unlock Value from Industrial Data with AI and ML Technology
6 May 2024

Compare InfluxDB vs. TDengine
19 April 2024

Why We Need the Next Generation Data Historian
15 April 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.