Alternatives to RocksDB logo

Alternatives to RocksDB

Redis, Cassandra, MongoDB, Badger, and HBase are the most popular alternatives and competitors to RocksDB.
112
269
+ 1
11

What is RocksDB and what are its top alternatives?

RocksDB is an embeddable persistent key-value store for fast storage. RocksDB can also be the foundation for a client-server database but our current focus is on embedded workloads. RocksDB builds on LevelDB to be scalable to run on servers with many CPU cores, to efficiently use fast storage, to support IO-bound, in-memory and write-once workloads, and to be flexible to allow for innovation.
RocksDB is a tool in the Databases category of a tech stack.
RocksDB is an open source tool with 25.3K GitHub stars and 5.8K GitHub forks. Here’s a link to RocksDB's open source repository on GitHub

Top Alternatives to RocksDB

  • 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. ...

  • Cassandra
    Cassandra

    Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL. ...

  • MongoDB
    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • Badger
    Badger

    Domain management you'll enjoy. Domains effectively drive the entire internet, shouldn't they be easier to manage? We thought so, and thus, Badger was born! You shouldn't have to auction off your house and sacrifice your first born to transfer domains, you should be able to press a button that says "Transfer Domain" and be done with it. That is our philosophy, and we think you will appreciate it. Stop letting domain registrars badger you, and start using... Badger! ...

  • HBase
    HBase

    Apache HBase is an open-source, distributed, versioned, column-oriented store modeled after Google' Bigtable: A Distributed Storage System for Structured Data by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, HBase provides Bigtable-like capabilities on top of Apache Hadoop. ...

  • 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. ...

  • Speedb
    Speedb

    Speedb’s Log-Structured Merge (LSM)-based key value store supports petabyte scaling of datasets with billions of objects, while maintaining high performance and low hardware requirements. It is based on a patented compaction method that reduces the write amplification factor (WAF) up to 6X and adds enhancements that eliminate latency issues and IO stalls. ...

  • Symas LMDB
    Symas LMDB

    It is an extraordinarily fast, memory-efficient database which is developed for the OpenLDAP Project. With memory-mapped files, it has the read performance of a pure in-memory database while retaining the persistence of standard disk-based databases. ...

RocksDB alternatives & related posts

Redis logo

Redis

55.2K
42K
3.9K
Open source (BSD licensed), in-memory data structure store
55.2K
42K
+ 1
3.9K
PROS OF REDIS
  • 884
    Performance
  • 541
    Super fast
  • 512
    Ease of use
  • 443
    In-memory cache
  • 323
    Advanced key-value cache
  • 193
    Open source
  • 182
    Easy to deploy
  • 164
    Stable
  • 155
    Free
  • 121
    Fast
  • 42
    High-Performance
  • 40
    High Availability
  • 34
    Data Structures
  • 32
    Very Scalable
  • 24
    Replication
  • 22
    Great community
  • 22
    Pub/Sub
  • 18
    "NoSQL" key-value data store
  • 15
    Hashes
  • 13
    Sets
  • 11
    Sorted Sets
  • 10
    Lists
  • 9
    BSD licensed
  • 9
    NoSQL
  • 8
    Async replication
  • 8
    Bitmaps
  • 8
    Integrates super easy with Sidekiq for Rails background
  • 7
    Open Source
  • 7
    Keys with a limited time-to-live
  • 6
    Lua scripting
  • 6
    Strings
  • 5
    Hyperloglogs
  • 5
    Awesomeness for Free
  • 4
    Feature Rich
  • 4
    Networked
  • 4
    Outstanding performance
  • 4
    Runs server side LUA
  • 4
    Transactions
  • 4
    Written in ANSI C
  • 4
    LRU eviction of keys
  • 3
    Performance & ease of use
  • 3
    Data structure server
  • 2
    Temporarily kept on disk
  • 2
    Channels concept
  • 2
    Simple
  • 2
    Dont save data if no subscribers are found
  • 2
    Object [key/value] size each 500 MB
  • 2
    Automatic failover
  • 2
    Easy to use
  • 2
    Existing Laravel Integration
  • 2
    Scalable
CONS OF REDIS
  • 15
    Cannot query objects directly
  • 3
    No secondary indexes for non-numeric data types
  • 1
    No WAL

related Redis posts

Robert Zuber

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.

See more

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.

See more
Cassandra logo

Cassandra

3.4K
3.4K
504
A partitioned row store. Rows are organized into tables with a required primary key.
3.4K
3.4K
+ 1
504
PROS OF CASSANDRA
  • 118
    Distributed
  • 97
    High performance
  • 81
    High availability
  • 74
    Easy scalability
  • 52
    Replication
  • 26
    Reliable
  • 26
    Multi datacenter deployments
  • 10
    Schema optional
  • 9
    OLTP
  • 8
    Open source
  • 2
    Workload separation (via MDC)
  • 1
    Fast
CONS OF CASSANDRA
  • 3
    Reliability of replication
  • 1
    Size
  • 1
    Updates

related Cassandra posts

Thierry Schellenbach
Shared insights
on
RedisRedisCassandraCassandraRocksDBRocksDB
at

1.0 of Stream leveraged Cassandra for storing the feed. Cassandra is a common choice for building feeds. Instagram, for instance started, out with Redis but eventually switched to Cassandra to handle their rapid usage growth. Cassandra can handle write heavy workloads very efficiently.

Cassandra is a great tool that allows you to scale write capacity simply by adding more nodes, though it is also very complex. This complexity made it hard to diagnose performance fluctuations. Even though we had years of experience with running Cassandra, it still felt like a bit of a black box. When building Stream 2.0 we decided to go for a different approach and build Keevo. Keevo is our in-house key-value store built upon RocksDB, gRPC and Raft.

RocksDB is a highly performant embeddable database library developed and maintained by Facebook’s data engineering team. RocksDB started as a fork of Google’s LevelDB that introduced several performance improvements for SSD. Nowadays RocksDB is a project on its own and is under active development. It is written in C++ and it’s fast. Have a look at how this benchmark handles 7 million QPS. In terms of technology it’s much more simple than Cassandra.

This translates into reduced maintenance overhead, improved performance and, most importantly, more consistent performance. It’s interesting to note that LinkedIn also uses RocksDB for their feed.

#InMemoryDatabases #DataStores #Databases

See more
Umair Iftikhar
Technical Architect at ERP Studio · | 3 upvotes · 371.9K views

Developing a solution that collects Telemetry Data from different devices, nearly 1000 devices minimum and maximum 12000. Each device is sending 2 packets in 1 second. This is time-series data, and this data definition and different reports are saved on PostgreSQL. Like Building information, maintenance records, etc. I want to know about the best solution. This data is required for Math and ML to run different algorithms. Also, data is raw without definitions and information stored in PostgreSQL. Initially, I went with TimescaleDB due to PostgreSQL support, but to increase in sites, I started facing many issues with timescale DB in terms of flexibility of storing data.

My major requirement is also the replication of the database for reporting and different purposes. You may also suggest other options other than Druid and Cassandra. But an open source solution is appreciated.

See more
MongoDB logo

MongoDB

85.5K
73.3K
4.1K
The database for giant ideas
85.5K
73.3K
+ 1
4.1K
PROS OF MONGODB
  • 828
    Document-oriented storage
  • 594
    No sql
  • 553
    Ease of use
  • 464
    Fast
  • 410
    High performance
  • 257
    Free
  • 218
    Open source
  • 180
    Flexible
  • 145
    Replication & high availability
  • 112
    Easy to maintain
  • 42
    Querying
  • 39
    Easy scalability
  • 38
    Auto-sharding
  • 37
    High availability
  • 31
    Map/reduce
  • 27
    Document database
  • 25
    Easy setup
  • 25
    Full index support
  • 16
    Reliable
  • 15
    Fast in-place updates
  • 14
    Agile programming, flexible, fast
  • 12
    No database migrations
  • 8
    Easy integration with Node.Js
  • 8
    Enterprise
  • 6
    Enterprise Support
  • 5
    Great NoSQL DB
  • 4
    Support for many languages through different drivers
  • 3
    Drivers support is good
  • 3
    Aggregation Framework
  • 3
    Schemaless
  • 2
    Fast
  • 2
    Managed service
  • 2
    Easy to Scale
  • 2
    Awesome
  • 2
    Consistent
  • 1
    Good GUI
  • 1
    Acid Compliant
CONS OF MONGODB
  • 6
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 1
    Proprietary query language

related MongoDB posts

Jeyabalaji Subramanian

Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

Based on the above criteria, we selected the following tools to perform the end to end data replication:

We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

See more
Robert Zuber

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.

See more
Badger logo

Badger

12
28
0
A new way of registering and managing your domains.
12
28
+ 1
0
PROS OF BADGER
    Be the first to leave a pro
    CONS OF BADGER
      Be the first to leave a con

      related Badger posts

      HBase logo

      HBase

      434
      476
      15
      The Hadoop database, a distributed, scalable, big data store
      434
      476
      + 1
      15
      PROS OF HBASE
      • 9
        Performance
      • 5
        OLTP
      • 1
        Fast Point Queries
      CONS OF HBASE
        Be the first to leave a con

        related HBase posts

        I am researching different querying solutions to handle ~1 trillion records of data (in the realm of a petabyte). The data is mostly textual. I have identified a few options: Milvus, HBase, RocksDB, and Elasticsearch. I was wondering if there is a good way to compare the performance of these options (or if anyone has already done something like this). I want to be able to compare the speed of ingesting and querying textual data from these tools. Does anyone have information on this or know where I can find some? Thanks in advance!

        See more

        Hi, I'm building a machine learning pipelines to store image bytes and image vectors in the backend.

        So, when users query for the random access image data (key), we return the image bytes and perform machine learning model operations on it.

        I'm currently considering going with Amazon S3 (in the future, maybe add Redis caching layer) as the backend system to store the information (s3 buckets with sharded prefixes).

        As the latency of S3 is 100-200ms (get/put) and it has a high throughput of 3500 puts/sec and 5500 gets/sec for a given bucker/prefix. In the future I need to reduce the latency, I can add Redis cache.

        Also, s3 costs are way fewer than HBase (on Amazon EC2 instances with 3x replication factor)

        I have not personally used HBase before, so can someone help me if I'm making the right choice here? I'm not aware of Hbase latencies and I have learned that the MOB feature on Hbase has to be turned on if we have store image bytes on of the column families as the avg image bytes are 240Kb.

        See more
        Aerospike logo

        Aerospike

        174
        262
        48
        Flash-optimized in-memory open source NoSQL database
        174
        262
        + 1
        48
        PROS OF AEROSPIKE
        • 16
          Ram and/or ssd persistence
        • 12
          Easy clustering support
        • 5
          Easy setup
        • 4
          Acid
        • 3
          Scale
        • 3
          Performance better than Redis
        • 3
          Petabyte Scale
        • 2
          Ease of use
        CONS OF AEROSPIKE
          Be the first to leave a con

          related Aerospike posts

          Speedb logo

          Speedb

          6
          8
          0
          An embeddable, high performance key-value store
          6
          8
          + 1
          0
          PROS OF SPEEDB
            Be the first to leave a pro
            CONS OF SPEEDB
              Be the first to leave a con

              related Speedb posts

              Symas LMDB logo

              Symas LMDB

              16
              33
              0
              A memory-efficient database
              16
              33
              + 1
              0
              PROS OF SYMAS LMDB
                Be the first to leave a pro
                CONS OF SYMAS LMDB
                  Be the first to leave a con

                  related Symas LMDB posts