DBMS > Oracle Coherence vs. SAP SQL Anywhere vs. SQLite vs. Vitess

System Properties Comparison Oracle Coherence vs. SAP SQL Anywhere vs. SQLite vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Oracles in-memory data grid solution

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

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	1.90
Rank	#127	Overall
	#21	Key-value stores

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.oracle.com/java/coherence

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

vitess.io

Technical documentation

docs.oracle.com/en/middleware/standalone/coherence

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

vitess.io/docs

Developer

Oracle

SAP

formerly Sybase

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2007

1992

2000

2013

Current release

14.1, August 2023

17, July 2015

3.46.1 (13 August 2024), August 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

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

Java

Server operating systems

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Docker
Linux
macOS

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C++
Java

C
C#
C++
Delphi
Java
JavaScript (Node.js)
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, in C/C++, Java, .Net or Perl

yes

proprietary syntax

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with selectable consistency level

Source-replica replication

Database mirroring

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

configurable

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optionally

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

authentification to access the cache via certificates or http basic authentication

fine grained access rights according to SQL-standard

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.