DBMS > Geode vs. Interbase vs. Snowflake vs. Typesense

System Properties Comparison Geode vs. Interbase vs. Snowflake vs. Typesense

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

Light-weight proven RDBMS

originally from Borland

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

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Key-value store

Relational DBMS

Search engine

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

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

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.76
Rank	#219	Overall
	#14	Search engines

Website

geode.apache.org

www.embarcadero.com/products/interbase

www.snowflake.com

typesense.org

Technical documentation

geode.apache.org/docs

docs.embarcadero.com/products/interbase

docs.snowflake.net/manuals/index.html

typesense.org/docs

Developer

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

Embarcadero

Snowflake Computing Inc.

Initial release

2002

1984

2014

2015

Current release

1.1, February 2017

InterBase 2020, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL V3

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

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Android
iOS
Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

yes

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

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

JavaScript (Node.js)
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes

Cache Event Listeners

yes

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

Multi-source replication

Interbase Change Views

yes

Multi-source replication using RAFT

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

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

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.