DBMS > 4D vs. Apache IoTDB vs. Memcached vs. Percona Server for MySQL vs. Snowflake

System Properties Comparison 4D vs. Apache IoTDB vs. Memcached vs. Percona Server for MySQL vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

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

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.4d.com

iotdb.apache.org

www.memcached.org

www.percona.com/software/mysql-database/percona-server

www.snowflake.com

Technical documentation

developer.4d.com

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

github.com/memcached/memcached/wiki

www.percona.com/downloads/Percona-Server-LATEST

docs.snowflake.net/manuals/index.html

Developer

4D, Inc

Apache Software Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Percona

Snowflake Computing Inc.

Initial release

1984

2018

2003

2008

2014

Current release

v20, April 2023

1.1.0, April 2023

1.6.25, March 2024

8.0.36-28, 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD license

Open Source

GPL version 2

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

OS X
Windows

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
OS X
Unix
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
Native API

Proprietary protocol

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

C
C#
C++
Go
Java
Python
Scala

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

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

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

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

Users and groups

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.