DBMS > KeyDB vs. Manticore Search vs. OpenEdge vs. Snowflake

System Properties Comparison KeyDB vs. Manticore Search vs. OpenEdge vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Multi-storage database for search, including full-text search.

Application development environment with integrated database management system

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

manticoresearch.com

www.progress.com/openedge

www.snowflake.com

Technical documentation

docs.keydb.dev

manual.manticoresearch.com

documentation.progress.com/output/ua/OpenEdge_latest

docs.snowflake.net/manuals/index.html

Developer

EQ Alpha Technology Ltd.

Manticore Software

Progress Software Corporation

Snowflake Computing Inc.

Initial release

2019

2017

1984

2014

Current release

6.0, February 2023

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

BSD-3

Open Source

GPL version 2

commercial

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

Linux

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

schema-free

Fixed schema

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

by using the Redis Search module

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

close to SQL 92

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Progress proprietary ABL (Advanced Business Language)

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning

since Version 11.4

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

The original contents of fields are not stored in the Manticore index.

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

simple password-based access control and ACL

Users and groups

Users with fine-grained authorization concept, user roles and pluggable authentication

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.