DBMS > PostGIS vs. Snowflake vs. Sphinx vs. TerarkDB vs. Transbase

System Properties Comparison PostGIS vs. Snowflake vs. Sphinx vs. TerarkDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

Cloud-based data warehousing service for structured and semi-structured data

Open source search engine for searching in data from different sources, e.g. relational databases

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

postgis.net

www.snowflake.com

sphinxsearch.com

github.com/bytedance/terarkdb

www.transaction.de/en/products/transbase.html

Technical documentation

postgis.net/documentation

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.transaction.de/en/products/transbase/features.html

Developer

Snowflake Computing Inc.

Sphinx Technologies Inc.

ByteDance, originally Terark

Transaction Software GmbH

Initial release

2005

2014

2001

2016

1987

Current release

3.4.2, February 2024

3.5.1, February 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL v2.0

commercial

Open Source

GPL version 2, commercial licence available

commercial

restricted open source version available

commercial

free development license

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

C and C++

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

yes

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.

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

CLI Client
JDBC
ODBC

Proprietary protocol

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

yes

based on PostgreSQL

Users with fine-grained authorization concept, user roles and pluggable authentication

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.