DBMS > 4D vs. InfinityDB vs. JaguarDB vs. Netezza vs. Snowflake

System Properties Comparison 4D vs. InfinityDB vs. JaguarDB vs. Netezza vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A Java embedded Key-Value Store which extends the Java Map interface

Performant, highly scalable DBMS for AI and IoT applications

Data warehouse and analytics appliance part of IBM PureSystems

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

Primary database model

Relational DBMS

Key-value store

Key-value store
Vector DBMS

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.4d.com

boilerbay.com

www.jaguardb.com

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

developer.4d.com

boilerbay.com/infinitydb/manual

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

4D, Inc

Boiler Bay Inc.

DataJaguar, Inc.

IBM

Snowflake Computing Inc.

Initial release

1984

2002

2015

2000

2014

Current release

v20, April 2023

4.0

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.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

Server operating systems

OS X
Windows

All OS with a Java VM

Linux

included in appliance

hosted

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

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

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

close to SQL 92

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

JDBC
ODBC

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

Java

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

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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.

User concepts

Access control

Users and groups

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.