DBMS > FileMaker vs. Ignite vs. PostGIS vs. SiteWhere vs. SQLite

System Properties Comparison FileMaker vs. Ignite vs. PostGIS vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

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.

Spatial extension of PostgreSQL

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.claris.com/filemaker

ignite.apache.org

postgis.net

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

www.claris.com/resources/documentation

apacheignite.readme.io/docs

postgis.net/documentation

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Claris

a subsidiary of Apple

Apache Software Foundation

SiteWhere

Dwayne Richard Hipp

Initial release

1983

2015

2005

2010

2000

Current release

19.4.1, November 2021

Apache Ignite 2.6

3.4.2, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

Common Public Attribution License Version 1.0

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.

Implementation language

C++, Java, .Net

Java

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

server-less

Data scheme

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

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

yes

SQL-92 is not fully supported

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

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

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

PHP

C#
C++
Java
PHP
Python
Ruby
Scala

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

yes

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

user defined functions

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

yes (replicated cache)

yes

based on PostgreSQL

selectable replication factor

based on HBase

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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

Security Hooks for custom implementations

yes

based on PostgreSQL

Users with fine-grained authorization concept

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.