DBMS > FileMaker vs. GridDB vs. Sphinx vs. SQLite vs. VelocityDB

System Properties Comparison FileMaker vs. GridDB vs. Sphinx vs. SQLite vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

www.claris.com/filemaker

Technical documentation

www.claris.com/resources/documentation

docs.griddb.net

sphinxsearch.com/docs

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

Claris

a subsidiary of Apple

Toshiba Corporation

Sphinx Technologies Inc.

Dwayne Richard Hipp

VelocityDB Inc

Initial release

1983

2013

2001

2000

2011

Current release

19.4.1, November 2021

5.1, August 2022

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

7.x

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

commercial

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++

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Any that supports .NET

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

via plugins

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

PHP

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Access rights for users can be defined per database

Based on Windows Authentication

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.