What are some alternatives to SummitDB?

What is SummitDB and what are its top alternatives?

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.

SummitDB is a tool in the In-Memory Databases category of a tech stack.

SummitDB is an open source tool with 1.3K GitHub stars and 79 GitHub forks. Here’s a link to SummitDB's open source repository on GitHub

Top Alternatives to SummitDB

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
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 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. ...
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. ...
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
It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale ...
NCache
NCache is an open source distributed cache for .NET & .NET Core (Apache 2.0) by Alachisoft. NCache provides an extremely fast and linearly scalable distributed cache that caches application data and reduces expensive database trips. ...
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. ...

SummitDB alternatives & related posts

Redis

47.9K

36.2K

3.9K

Open source (BSD licensed), in-memory data structure store

Stacks47.9K

Followers36.2K

+ 1

Votes3.9K

PROS OF REDIS

879
Performance
536
Super fast
511
Ease of use
441
In-memory cache
321
Advanced key-value cache
190
Open source
179
Easy to deploy
163
Stable
152
Free
120
Fast
40
High-Performance
39
High Availability
34
Data Structures
32
Very Scalable
23
Replication
20
Great community
19
Pub/Sub
17
"NoSQL" key-value data store
14
Hashes
12
Sets
10
Sorted Sets
9
Lists
8
BSD licensed
8
NoSQL
7
Async replication
7
Integrates super easy with Sidekiq for Rails background
7
Bitmaps
6
Open Source
6
Keys with a limited time-to-live
5
Strings
5
Lua scripting
4
Awesomeness for Free!
4
Hyperloglogs
3
outstanding performance
3
Runs server side LUA
3
Networked
3
LRU eviction of keys
3
Written in ANSI C
3
Feature Rich
3
Transactions
2
Data structure server
2
Performance & ease of use
1
Existing Laravel Integration
1
Automatic failover
1
Easy to use
1
Object [key/value] size each 500 MB
1
Simple
1
Channels concept
1
Scalable
1
Temporarily kept on disk
1
Dont save data if no subscribers are found
0
Jk

CONS OF REDIS

14
Cannot query objects directly
2
No secondary indexes for non-numeric data types
1
No WAL

COMPARE

Compare Redis vs SummitDB

related Redis posts

Robert Zuber

CTO at CircleCI · Jul 24, 2019 | 24 upvotes · 2M views

Shared insights

We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

Update: How CircleCI Processes Over 30 Million Builds Per Month - CircleCI Tech Stack

Bryam Rodriguez

Feb 5, 2020 | 20 upvotes · 1.5M views

Shared insights

react-testing-library

Bit

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.