DBMS > 4D vs. Atos Standard Common Repository vs. FileMaker vs. Google BigQuery vs. Ignite

System Properties Comparison 4D vs. Atos Standard Common Repository vs. FileMaker vs. Google BigQuery vs. Ignite

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

Large scale data warehouse service with append-only tables

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store
Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

www.4d.com

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.claris.com/filemaker

cloud.google.com/bigquery

ignite.apache.org

Technical documentation

developer.4d.com

www.claris.com/resources/documentation

cloud.google.com/bigquery/docs

apacheignite.readme.io/docs

Developer

4D, Inc

Atos Convergence Creators

Claris

a subsidiary of Apple

Google

Apache Software Foundation

Initial release

1984

2016

1983

2010

2015

Current release

v20, April 2023

1703

19.4.1, November 2021

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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++, Java, .Net

Server operating systems

OS X
Windows

Linux

iOS

client part only
Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

via plugins

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

Filemaker WebDirect
JDBC
ODBC

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication, warm standby

since Version 14

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

Since BigQuery is designed for querying data

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.

yes

User concepts

Access control

Users and groups

LDAP bind authentication

simple rights management via user accounts and connection to external directory services

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Security Hooks for custom implementations

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.