DBMS > Infobright vs. Memcached vs. SQLite vs. TimescaleDB

System Properties Comparison Infobright vs. Memcached vs. SQLite vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

In-memory key-value store, originally intended for caching

Widely used embeddable, in-process RDBMS

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

Primary database model

Secondary database models

Relational DBMS

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

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.memcached.org

www.sqlite.org

www.timescale.com

Technical documentation

github.com/memcached/memcached/wiki

www.sqlite.org/docs.html

docs.timescale.com

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Dwayne Richard Hipp

Timescale

Initial release

2005

2003

2000

2017

Current release

1.6.29, June 2024

3.46.1 (13 August 2024), August 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

BSD license

Open Source

Public Domain

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

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Unix
Windows

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes

using SASL (Simple Authentication and Security Layer) protocol

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.