DBMS > Derby vs. FatDB vs. KeyDB vs. SiteWhere

System Properties Comparison Derby vs. FatDB vs. KeyDB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Time Series DBMS

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

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

db.apache.org/derby

github.com/Snapchat/KeyDB
keydb.dev

github.com/sitewhere/sitewhere

Technical documentation

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

docs.keydb.dev

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

FatCloud

EQ Alpha Technology Ltd.

SiteWhere

Initial release

1997

2012

2019

2010

Current release

10.17.1.0, November 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

BSD-3

Open Source

Common Public Attribution License Version 1.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

Java

C++

Java

Server operating systems

All OS with a Java VM

Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

yes

Via inetgration in SQL Server

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

Supported programming languages

Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

Lua

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Can implement custom security layer via applications

simple password-based access control and ACL

Users with fine-grained authorization concept

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

Recent citations in the news

JDBC tutorial: Easy installation and setup with Apache Derby
20 December 2019, TheServerSide.com

Top Database Tools for Java Developers in 2023
17 November 2023, TechRepublic

Installing Apache Hive 3.1.2 on Windows 10 | by Hadi Fadlallah
3 May 2020, Towards Data Science

The Arrival of Java 20
21 March 2023, Oracle

No, Citrix did not kill CloudStack
15 September 2014, InfoWorld

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page