StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. In-Memory Databases
  4. In Memory Databases
  5. KeyDB vs SummitDB

KeyDB vs SummitDB

OverviewComparisonAlternatives

Overview

SummitDB
SummitDB
Stacks4
Followers13
Votes0
GitHub Stars1.4K
Forks77
KeyDB
KeyDB
Stacks37
Followers62
Votes5

KeyDB vs SummitDB: What are the differences?

Introduction:

KeyDB is a high-performance fork of Redis, while SummitDB is a distributed key-value store focused on high performance and scalability.

1. **Architecture**: KeyDB is a single-threaded architecture based on Redis, whereas SummitDB employs a multi-threaded architecture for improved performance under heavy workloads.
2. **Consistency**: KeyDB ensures eventual consistency, while SummitDB provides strong consistency for data operations.
3. **Replication**: KeyDB supports synchronous and asynchronous replication, whereas SummitDB offers multi-master replication for high availability and durability.
4. **Partitioning**: KeyDB supports sharding for horizontal scalability, whereas SummitDB uses distributed partitioning and consistent hashing for load balancing.
5. **Data Handling**: KeyDB leverages in-memory data storage with optional disk persistence, while SummitDB achieves high throughput through efficient disk-based storage and caching mechanisms.
6. **Concurrency Control**: KeyDB employs optimistic concurrency control strategies, while SummitDB uses locking mechanisms to ensure data integrity in distributed environments.

In Summary, KeyDB and SummitDB differ in their architecture, consistency models, replication methods, partitioning strategies, data handling approaches, and concurrency control mechanisms, making them suitable for different use cases based on performance and scalability requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

SummitDB
SummitDB
KeyDB
KeyDB

SummitDB is an in-memory, NoSQL key/value database. It persists to disk, uses the Raft consensus algorithm, is ACID compliant, and built on a transactional and strongly-consistent model. It supports custom indexes, geospatial data, JSON documents, and user-defined JS scripting.

KeyDB is a fully open source database that aims to make use of all hardware resources. KeyDB makes it possible to breach boundaries often dictated by price and complexity.

-
Active Replication; FLASH storage support; direct backup to AWS S3; MultiMaster; Multithreaded
Statistics
GitHub Stars
1.4K
GitHub Stars
-
GitHub Forks
77
GitHub Forks
-
Stacks
4
Stacks
37
Followers
13
Followers
62
Votes
0
Votes
5
Pros & Cons
No community feedback yet
Pros
  • 3
    Performance
  • 2
    Active Replication

What are some alternatives to SummitDB, KeyDB?

Redis

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

Hazelcast

Hazelcast

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

Aerospike

Aerospike

Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.

MemSQL

MemSQL

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

Apache Ignite

Apache Ignite

It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale

SAP HANA

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

VoltDB

VoltDB

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

Tarantool

Tarantool

It is designed to give you the flexibility, scalability, and performance that you want, as well as the reliability and manageability that you need in mission-critical applications

Azure Redis Cache

Azure Redis Cache

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.

LokiJS

LokiJS

LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase