DBMS > jBASE vs. Machbase Neo vs. Microsoft SQL Server vs. PlanetScale

System Properties Comparison jBASE vs. Machbase Neo vs. Microsoft SQL Server vs. PlanetScale

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

TimeSeries DBMS for AIoT and BigData

Microsofts flagship relational DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Multivalue DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

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

machbase.com

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

planetscale.com

Technical documentation

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

machbase.com/dbms

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

planetscale.com/docs

Developer

Rocket Software (formerly Zumasys)

Machbase

Microsoft

PlanetScale

Initial release

1991

2013

1989

2020

Current release

5.7

V8.0, August 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

free test version available

commercial

restricted free version is 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++

Server operating systems

AIX
Linux
Windows

Linux
macOS
Windows

Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

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

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Basic
Jabbascript
Java

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

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

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes, but depending on the SQL-Server Edition

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

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

volatile and lookup table

yes

User concepts

Access control

Access rights can be defined down to the item level

simple password-based access control

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.