DBMS > Derby vs. Memcached vs. Microsoft SQL Server vs. RRDtool

System Properties Comparison Derby vs. Memcached vs. Microsoft SQL Server vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Microsofts flagship relational DBMS

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	5.30
Rank	#66	Overall
	#36	Relational DBMS

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

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	2.14
Rank	#124	Overall
	#10	Time Series DBMS

Website

db.apache.org/derby

www.memcached.org

www.microsoft.com/en-us/sql-server

oss.oetiker.ch/rrdtool

Technical documentation

db.apache.org/derby/manuals/index.html

github.com/memcached/memcached/wiki

learn.microsoft.com/en-US/sql/sql-server

oss.oetiker.ch/rrdtool/doc

Developer

Apache Software Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Tobias Oetiker

Initial release

1997

2003

1989

1999

Current release

10.17.1.0, November 2023

1.6.25, March 2024

SQL Server 2022, November 2022

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

BSD license

commercial

restricted free version is available

Open Source

GPL V2 and FLOSS

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

Java

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

HP-UX
Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

Proprietary protocol

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

in-process shared library
Pipes

Supported programming languages

Java

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

by using the rrdcached daemon

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

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.