DBMS > Cachelot.io vs. PostGIS vs. searchxml vs. Sequoiadb vs. TimescaleDB

System Properties Comparison Cachelot.io vs. PostGIS vs. searchxml vs. Sequoiadb vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

Spatial extension of PostgreSQL

DBMS for structured and unstructured content wrapped with an application server

NewSQL database with distributed OLTP and SQL

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Key-value store

Spatial DBMS

Native XML DBMS
Search engine

Document store
Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

cachelot.io

postgis.net

www.searchxml.net/category/products

www.sequoiadb.com

www.timescale.com

Technical documentation

postgis.net/documentation

www.searchxml.net/support/handouts

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.timescale.com

Developer

informationpartners gmbh

Sequoiadb Ltd.

Timescale

Initial release

2015

2005

2015

2013

2017

Current release

3.4.2, February 2024

1.0

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

GPL v2.0

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

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

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

Memcached protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

proprietary protocol using JSON

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

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

C++

most other programming languages supported via APIs

.Net
C++
Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

yes

sychronisation to multiple collections

Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

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

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

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.

User concepts

Access control

yes

based on PostgreSQL

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

simple password-based access control

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.

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

Recent citations in the news

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, businesswire.com

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page