DBMS > Apache Kylin vs. EJDB vs. Google BigQuery vs. GraphDB

System Properties Comparison Apache Kylin vs. EJDB vs. Google BigQuery vs. GraphDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

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.

Primary database model

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Website

kylin.apache.org

github.com/Softmotions/ejdb

cloud.google.com/bigquery

www.ontotext.com

Technical documentation

kylin.apache.org/docs

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

graphdb.ontotext.com/documentation

Social network pages

Developer

Apache Software Foundation, originally contributed from eBay Inc

Softmotions

Google

Ontotext

Initial release

2015

2012

2010

2000

Current release

3.1.0, July 2020

10.4, October 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

Some plugins of GraphDB Workbench are open sourced

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

Linux

server-less

hosted

All OS with a Java VM
Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

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

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

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

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

in-process shared library

RESTful HTTP/JSON API

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

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

well-defined plugin interfaces; JavaScript server-side extensibility

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Constraint checking

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

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.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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.

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

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

Okay, RAG… We Have a Problem
26 April 2024

Scaling Understanding with the Help of Feedback Loops, Knowledge Graphs and NLP
19 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.