DBMS > FatDB vs. InterSystems Caché vs. Lovefield vs. Microsoft Azure Table Storage vs. Yaacomo

System Properties Comparison FatDB vs. InterSystems Caché vs. Lovefield vs. Microsoft Azure Table Storage vs. Yaacomo

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.

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A multi-model DBMS and application server

Embeddable relational database for web apps written in pure JavaScript

A Wide Column Store for rapid development using massive semi-structured datasets

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Wide column store

Relational DBMS

Secondary database models

Document store

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

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Website

www.intersystems.com/products/cache

google.github.io/lovefield

azure.microsoft.com/en-us/services/storage/tables

yaacomo.com

Technical documentation

docs.intersystems.com

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

FatCloud

InterSystems

Google

Microsoft

Q2WEB GmbH

Initial release

2012

1997

2014

2012

2009

Current release

2018.1.4, May 2020

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

JavaScript

Server operating systems

Windows

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Android
Linux
Windows

Data scheme

schema-free

depending on used data model

yes

schema-free

yes

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

Via inetgration in SQL Server

yes

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

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

.NET Client API
JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC

Supported programming languages

C#
C++
Java

JavaScript

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights for users, groups and roles

Access rights based on private key authentication or shared access signatures

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.

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

InterSystems
5 March 2019, International Spectrum Magazine

Announcing IBM Spectrum Sentinel: Building a Cyber Resilient Future
24 June 2022, IBM

Associative Data Modeling Demystified – Part1
9 July 2016, Data Science Central

Choosing a Database Technology. A roadmap and process overview | by Shirish Joshi
23 February 2020, Towards Data Science

New Release of MITS Report Expands Database Support, Improves Usability and Integration Capabilities
13 February 2019, International Spectrum Magazine

provided by Google News

How to use Azure Table storage in .Net
10 July 2024, InfoWorld

Working with Azure to Use and Manage Data Lakes
23 July 2024, Simplilearn

Azure Cosmos DB Data Migration tool imports from Azure Table storage
5 May 2015, Microsoft

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

Testing Precompiled Azure Functions Locally with Storage Emulator
8 March 2018, Visual Studio Magazine

provided by Google News

Share this page