DBMS > Amazon CloudSearch vs. FatDB vs. GraphDB vs. SQLite

System Properties Comparison Amazon CloudSearch vs. FatDB vs. GraphDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	3.32
Rank	#91	Overall
	#6	Graph DBMS
	#4	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/cloudsearch

www.ontotext.com

www.sqlite.org

Technical documentation

docs.aws.amazon.com/cloudsearch

graphdb.ontotext.com/documentation

www.sqlite.org/docs.html

Social network pages

Developer

Amazon

FatCloud

Ontotext

Dwayne Richard Hipp

Initial release

2012

2000

Current release

10.4, October 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

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

Server operating systems

hosted

Windows

All OS with a Java VM
Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

schema-free and OWL/RDFS-schema support; RDF shapes

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
Clojure
Java
JavaScript (Node.js)
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

via applications

well-defined plugin interfaces; JavaScript server-side extensibility

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

selectable replication factor

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Foreign keys

Referential integrity

yes

Constraint checking

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

authentication via encrypted signatures

Can implement custom security layer via applications

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

A Triple Store RAG Retriever
29 May 2024

Integrating GraphDB with Relational Database Systems
23 May 2024

Understanding the Graph Center of Excellence
17 May 2024

Migrating From LPG to RDF Graph Model
8 May 2024

Case study: Policy Enforcement Automation With Semantics
2 May 2024

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.