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

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

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.

DBMS for structured and unstructured content wrapped with an application server

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Document store
Spatial 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	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.enterprisedb.com

www.geomesa.org

cloud.google.com/spanner

www.searchxml.net/category/products

www.sqlite.org

Technical documentation

www.enterprisedb.com/docs

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

cloud.google.com/spanner/docs

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

Developer

EnterpriseDB

CCRi and others

Google

informationpartners gmbh

Dwayne Richard Hipp

Initial release

2005

2014

2017

2015

2000

Current release

14, December 2021

4.0.5, February 2024

1.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

Open Source

Apache License 2.0

commercial

Open Source

Public Domain

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

Scala

C++

Server operating systems

Linux
Windows

hosted

Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

standard with numerous extensions

yes

Query statements complying to ANSI 2011

yes

SQL-92 is not fully supported

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

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

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

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

depending on storage layer

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.

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes

Transaction concepts

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

ACID

Strict serializable isolation

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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.

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)

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.