DBMS > GBase vs. PostGIS vs. searchxml vs. Sphinx vs. Tkrzw

System Properties Comparison GBase vs. PostGIS vs. searchxml vs. Sphinx vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Spatial extension of PostgreSQL

DBMS for structured and unstructured content wrapped with an application server

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Spatial DBMS

Native XML DBMS
Search engine

Search engine

Key-value store

Secondary database models

Relational DBMS

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.gbase.cn

postgis.net

www.searchxml.net/category/products

sphinxsearch.com

dbmx.net/tkrzw

Technical documentation

postgis.net/documentation

www.searchxml.net/support/handouts

sphinxsearch.com/docs

Developer

General Data Technology Co., Ltd.

informationpartners gmbh

Sphinx Technologies Inc.

Mikio Hirabayashi

Initial release

2004

2005

2015

2001

2020

Current release

GBase 8a, GBase 8s, GBase 8c

3.4.2, February 2024

1.0

3.5.1, February 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, Java, Python

C++

Server operating systems

Linux

Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

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

SQL

Support of SQL

Standard with numerous extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

Proprietary protocol

Supported programming languages

C++

most other programming languages supported via APIs

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

yes

based on PostgreSQL

none

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

sychronisation to multiple collections

none

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

multiple readers, single writer

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

using specific database classes

User concepts

Access control

yes

based on PostgreSQL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Google's Newest Challenger
11 January 2024, Free Press Journal

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018 | WQXR Editorial
22 December 2018, WQXR Radio

provided by Google News

Share this page