DBMS > Faircom EDGE vs. Memcached vs. SQLite vs. Vitess

System Properties Comparison Faircom EDGE vs. Memcached vs. SQLite vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

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

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.faircom.com/products/faircom-edge

www.memcached.org

www.sqlite.org

vitess.io

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

github.com/memcached/memcached/wiki

www.sqlite.org/docs.html

vitess.io/docs

Developer

FairCom Corporation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

1979

2003

2000

2013

Current release

V3, October 2020

1.6.29, June 2024

3.46.1 (13 August 2024), August 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

BSD license

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

ANSI C, C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

FreeBSD
Linux
OS X
Unix
Windows

server-less

Docker
Linux
macOS

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

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

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

Repcached, a Memcached patch, provides this functionallity

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

yes

table locks or row locks depending on storage engine

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 user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or 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.