DBMS > Kinetica vs. Manticore Search vs. Memcached vs. SAP SQL Anywhere vs. SQLite

System Properties Comparison Kinetica vs. Manticore Search vs. Memcached vs. SAP SQL Anywhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

GPU-accelerated database for real-time analysis of large and streaming datasets

Open source search engine for searching in data from different sources. Forked of and compatible with Sphinx.

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.76
Rank	#193	Overall
	#97	Relational DBMS

Score	0.04
Rank	#318	Overall
	#15	Search engines

Score	25.97
Rank	#28	Overall
	#4	Key-value stores

Score	6.30
Rank	#61	Overall
	#35	Relational DBMS

Score	121.89
Rank	#9	Overall
	#6	Relational DBMS

Website

www.kinetica.com

manticoresearch.com

www.memcached.org

www.sap.com/products/sql-anywhere.html

www.sqlite.org

Technical documentation

www.kinetica.com/docs

docs.manticoresearch.com/latest/html
github.com/manticoresoftware/manticoresearch

github.com/memcached/memcached/wiki

help.sap.com/sql-anywhere

www.sqlite.org/docs.html

Developer

Kinetica

Manticore Software

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

formerly Sybase

Dwayne Richard Hipp

Initial release

2012

2017

2003

1992

2000

Current release

6.0

1.6.9, November 2020

17, July 2015

3.34.0 (December 1, 2020), December 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

BSD license

commercial

Open Source

Public Domain

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

C++

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris
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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
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

Server-side scripts

Stored procedures

user defined functions

yes, in C/C++, Java, .Net or Perl

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

Durability

Support for making data persistent

yes

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

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.