DBMS > Cachelot.io vs. Google Cloud Datastore vs. OpenEdge vs. Percona Server for MongoDB

System Properties Comparison Cachelot.io vs. Google Cloud Datastore vs. OpenEdge vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Application development environment with integrated database management system

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

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

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Website

cachelot.io

cloud.google.com/datastore

www.progress.com/openedge

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

cloud.google.com/datastore/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.percona.com/percona-distribution-for-mongodb

Developer

Google

Progress Software Corporation

Percona

Initial release

2015

2008

1984

2015

Current release

OpenEdge 12.2, March 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Simplified BSD License

commercial

Open Source

GPL Version 2

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

Server operating systems

FreeBSD
Linux
OS X

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

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

SQL-like query language (GQL)

yes

close to SQL 92

APIs and other access methods

Memcached protocol

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

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

Progress proprietary ABL (Advanced Business Language)

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

using Google App Engine

yes

JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

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

via In-Memory Engine

User concepts

Access control

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

Users and groups

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.

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 Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

provided by Google News

What's New in OpenEdge 12.8
15 April 2024, release.nl

Learning to failover
3 April 2017, SDTimes.com

4 sources of latency and how to avoid them
1 November 2017, InfoWorld

provided by Google News

Percona Delivers Open Source In-Memory Storage Engine for Percona Server for MongoDB
20 August 2016, insideBIGDATA

Is database-as-a-service in Percona’s future?
23 May 2022, VentureBeat

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

How to deploy the Percona database performance monitor with Docker
20 September 2022, TechRepublic

provided by Google News

Share this page