DBMS > Geode vs. jBASE vs. Microsoft SQL Server vs. SQLite

System Properties Comparison Geode vs. jBASE vs. Microsoft SQL Server vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A robust multi-value DBMS comprising development tools and middleware

Microsofts flagship relational DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

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

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

www.sqlite.org

Technical documentation

geode.apache.org/docs

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

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

www.sqlite.org/docs.html

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Rocket Software (formerly Zumasys)

Microsoft

Dwayne Richard Hipp

Initial release

2002

1991

1989

2000

Current release

1.1, February 2017

5.7

SQL Server 2022, November 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

Public Domain

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Linux
Windows

Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (OQL)

Embedded SQL for jBASE in BASIC

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Basic
Jabbascript
Java

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

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

Server-side scripts

Stored procedures

user defined functions

yes

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

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 per client and object definable

Access rights can be defined down to the item level

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.