DBMS > jBASE vs. Microsoft SQL Server vs. RavenDB vs. Riak KV

System Properties Comparison jBASE vs. Microsoft SQL Server vs. RavenDB vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A robust multi-value DBMS comprising development tools and middleware

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.microsoft.com/en-us/sql-server

ravendb.net

Technical documentation

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

learn.microsoft.com/en-US/sql/sql-server

ravendb.net/docs

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Rocket Software (formerly Zumasys)

Microsoft

Hibernating Rhinos

OpenSource, formerly Basho Technologies

Initial release

1991

1989

2010

2009

Current release

5.7

SQL Server 2022, November 2022

5.4, July 2022

3.2.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

Server operating systems

AIX
Linux
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

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

restricted

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
Basic
Jabbascript
Java

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

Multi-source replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

yes, using Riak Security

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.