DBMS > EDB Postgres vs. GeoMesa vs. Google Cloud Spanner vs. Redis vs. searchxml

System Properties Comparison EDB Postgres vs. GeoMesa vs. Google Cloud Spanner vs. Redis vs. searchxml

Editorial information provided by DB-Engines

Name

Description

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

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.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

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

Native XML DBMS
Search engine

Secondary database models

Document store
Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

www.enterprisedb.com

www.geomesa.org

cloud.google.com/spanner

redis.com
redis.io

www.searchxml.net/category/products

Technical documentation

www.enterprisedb.com/docs

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/spanner/docs

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

www.searchxml.net/support/handouts

Developer

EnterpriseDB

CCRi and others

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

informationpartners gmbh

Initial release

2005

2014

2017

2009

2015

Current release

14, December 2021

4.0.5, February 2024

7.2.4, January 2024

1.0

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

Open Source

Apache License 2.0

commercial

Open Source

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

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.

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

Implementation language

Scala

C++

Server operating systems

Linux
Windows

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

yes

standard with numerous extensions

yes

Query statements complying to ANSI 2011

with RediSQL module

APIs and other access methods

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

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

Go
Java
JavaScript (Node.js)
Python

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

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

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

yes

on the application server

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

depending on storage layer

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

Atomic execution of command blocks and scripts and optimistic locking

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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.

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

Domain, group and role-based access control at the document level and for application services

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.