DBMS > Memcached vs. searchxml vs. SQLite vs. Stardog

System Properties Comparison Memcached vs. searchxml vs. SQLite vs. Stardog

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

DBMS for structured and unstructured content wrapped with an application server

Widely used embeddable, in-process RDBMS

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Key-value store

Native XML DBMS
Search engine

Relational DBMS

Graph DBMS
RDF store

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

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

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

www.memcached.org

www.searchxml.net/category/products

www.sqlite.org

www.stardog.com

Technical documentation

github.com/memcached/memcached/wiki

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

docs.stardog.com

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

informationpartners gmbh

Dwayne Richard Hipp

Stardog-Union

Initial release

2003

2015

2000

2010

Current release

1.6.27, May 2024

1.0

3.46.0 (23 May 2024), May 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

Public Domain

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

Windows

server-less

Linux
macOS
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

SQL-92 is not fully supported

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

Proprietary protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

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

C++

most other programming languages supported via APIs

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
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

on the application server

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

sychronisation to multiple collections

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

multiple readers, single writer

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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

Access rights for users and roles

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.