DBMS > Cachelot.io vs. Faircom DB vs. Snowflake vs. Yanza

System Properties Comparison Cachelot.io vs. Faircom DB vs. Snowflake vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

In-memory caching system

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

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

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cachelot.io

www.faircom.com/products/faircom-db

www.snowflake.com

yanza.com

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.snowflake.net/manuals/index.html

Developer

FairCom Corporation

Snowflake Computing Inc.

Yanza

Initial release

2015

1979

2014

2015

Current release

V13, July 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

commercial

Restricted, free version available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

ANSI C, C++

Server operating systems

FreeBSD
Linux
OS X

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Windows

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

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

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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 with proprietary extensions

yes

APIs and other access methods

Memcached protocol

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

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

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

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.