DBMS > Altibase vs. jBASE vs. Oracle Berkeley DB vs. Snowflake

System Properties Comparison Altibase vs. jBASE vs. Oracle Berkeley DB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

A robust multi-value DBMS comprising development tools and middleware

Widely used in-process key-value store

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

Primary database model

Relational DBMS

Multivalue DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

altibase.com

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

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

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

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Altibase

Rocket Software (formerly Zumasys)

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

1999

1991

1994

2014

Current release

v7.3, 2023, August 2023

5.7

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

commercial license available

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

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

AIX
HP-UX
Linux

AIX
Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

Embedded SQL for jBASE in BASIC

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java

.Net
Basic
Jabbascript
Java

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

user defined functions

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.