DBMS > EsgynDB vs. FatDB vs. Google Cloud Bigtable vs. MarkLogic

System Properties Comparison EsgynDB vs. FatDB vs. Google Cloud Bigtable vs. MarkLogic

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Operational and transactional Enterprise NoSQL database

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store
Wide column store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Website

www.esgyn.cn

cloud.google.com/bigtable

www.progress.com/marklogic

Technical documentation

cloud.google.com/bigtable/docs

www.progress.com/marklogic/documentation

Developer

Esgyn

FatCloud

Google

MarkLogic Corp.

Initial release

2015

2012

2015

2001

Current release

11.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is 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

C++, Java

C++

Server operating systems

Linux

Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

Schema can be enforced

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

Via inetgration in SQL Server

yes

SQL92

APIs and other access methods

ADO.NET
JDBC
ODBC

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

yes

via XQuery or JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

can act as a resource manager in an XA/JTA transaction

Concurrency

Support for concurrent manipulation of data

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, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

Role-based access control at the document and subdocument levels

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

AI can make logistics data as valuable as intelligence or operational data for mission success
17 April 2024, Breaking Defense

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, release.nl

Intelligence for multi-domain warfighters can now be sourced from logistics operations
13 May 2024, Breaking Defense

provided by Google News

Share this page