DBMS > Google Cloud Datastore vs. GraphDB vs. Kinetica vs. searchxml vs. SQLite

System Properties Comparison Google Cloud Datastore vs. GraphDB vs. Kinetica vs. searchxml vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.

Fully vectorized database across both GPUs and CPUs

DBMS for structured and unstructured content wrapped with an application server

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Graph DBMS
RDF store

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/datastore

www.ontotext.com

www.kinetica.com

www.searchxml.net/category/products

www.sqlite.org

Technical documentation

cloud.google.com/datastore/docs

graphdb.ontotext.com/documentation

docs.kinetica.com

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

Social network pages

Developer

Google

Ontotext

Kinetica

informationpartners gmbh

Dwayne Richard Hipp

Initial release

2008

2000

2012

2015

2000

Current release

10.4, October 2023

7.1, August 2021

1.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

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

C++

Server operating systems

hosted

All OS with a Java VM
Linux
OS X
Windows

Linux

Windows

server-less

Data scheme

schema-free

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

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes, details here

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

Secondary indexes

yes

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

yes

SQL

Support of SQL

SQL-like query language (GQL)

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

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

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

using Google App Engine

well-defined plugin interfaces; JavaScript server-side extensibility

user defined functions

yes

on the application server

Triggers

Callbacks using the Google Apps Engine

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication

Source-replica replication

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Constraint checking

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

multiple readers, single writer

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Access rights for users and roles on table level

Domain, group and role-based access control at the document level and for application services

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

Case study: Policy Enforcement Automation With Semantics
2 May 2024

Okay, RAG… We Have a Problem
26 April 2024

Scaling Understanding with the Help of Feedback Loops, Knowledge Graphs and NLP
19 April 2024

How Knowledge Graphs Power Data Mesh and Data Fabric
10 April 2024

Building Smarter Financial Services: The Role of Semantic Technologies, Knowledge Graphs and Generative AI
3 April 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.