DBMS > Geode vs. JaguarDB vs. Lovefield vs. Netezza vs. Snowflake

System Properties Comparison Geode vs. JaguarDB vs. Lovefield vs. Netezza vs. Snowflake

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

Performant, highly scalable DBMS for AI and IoT applications

Embeddable relational database for web apps written in pure JavaScript

Data warehouse and analytics appliance part of IBM PureSystems

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

Primary database model

Key-value store

Key-value store
Vector DBMS

Relational DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

geode.apache.org

www.jaguardb.com

google.github.io/lovefield

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

geode.apache.org/docs

www.jaguardb.com/support.html

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.snowflake.net/manuals/index.html

Developer

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

DataJaguar, Inc.

Google

IBM

Snowflake Computing Inc.

Initial release

2002

2015

2014

2000

2014

Current release

1.1, February 2017

3.3 July 2023

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL V3.0

Open Source

Apache 2.0

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

Java

C++

the server part. Clients available in other languages

JavaScript

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

included in appliance

hosted

Data scheme

schema-free

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

Access rights per client and object definable

rights management via user accounts

Users with fine-grained authorization concept

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.