DBMS > AgensGraph vs. dBASE vs. Google BigQuery vs. Splice Machine vs. Splunk

System Properties Comparison AgensGraph vs. dBASE vs. Google BigQuery vs. Splice Machine vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Large scale data warehouse service with append-only tables

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Analytics Platform for Big Data

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

bitnine.net/agensgraph

www.dbase.com

cloud.google.com/bigquery

splicemachine.com

www.splunk.com

Technical documentation

bitnine.net/documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

splicemachine.com/how-it-works

docs.splunk.com/Documentation/Splunk

Developer

Bitnine Global Inc.

Asthon Tate

Google

Splice Machine

Splunk Inc.

Initial release

2016

1979

2010

2014

2003

Current release

2.1, December 2018

dBASE 2019, 2019

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL 3.0, commercial license available

commercial

Limited free edition and free developer edition available

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
OS X
Windows

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux
OS X
Solaris
Windows

Data scheme

depending on used data model

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

Cypher Query Language
JDBC

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

HTTP REST

Supported programming languages

C
Java
JavaScript
Python

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

yes

Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

not for dBase internal data, but IDE does support transactions when accessing external DBMS

Since BigQuery is designed for querying data

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

Access rights for users and roles

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.