DBMS > Coveo vs. GigaSpaces vs. Postgres-XL vs. SQLite

System Properties Comparison Coveo vs. GigaSpaces vs. Postgres-XL vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Secondary database models

Graph DBMS
Search engine

Document store
Spatial DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

docs.coveo.com

docs.gigaspaces.com/latest/landing.html

www.postgres-xl.org/documentation

www.sqlite.org/docs.html

Developer

Coveo

Gigaspaces Technologies

Dwayne Richard Hipp

Initial release

2012

2000

2014

since 2012, originally named StormDB

2000

Current release

15.5, September 2020

10 R1, October 2018

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

Mozilla public license

Open Source

Public Domain

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

Server operating systems

hosted

Linux
macOS
Solaris
Windows

Linux
macOS

server-less

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

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.

XML can be used for describing objects metadata

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

distributed, parallel query execution

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Java
JavaScript
Python

.Net
C++
Java
Python
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

user defined functions

Triggers

yes

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

MVCC

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

granular access controls, API key management, content filters

Role-based access control

fine grained access rights according to SQL-standard

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.