Need advice about which tool to choose?Ask the StackShare community!

IronDB

1
11
+ 1
0
Memcached

5.6K
4K
+ 1
469
Add tool

IronDB vs Memcached: What are the differences?

Developers describe IronDB as "A resilient key-value store for the browser". IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted. On the other hand, Memcached is detailed as "High-performance, distributed memory object caching system". Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

IronDB and Memcached belong to "Databases" category of the tech stack.

IronDB and Memcached are both open source tools. It seems that Memcached with 8.99K GitHub stars and 2.6K forks on GitHub has more adoption than IronDB with 5 GitHub stars and 1 GitHub forks.

Decisions about IronDB and Memcached
 This was roughly 4 years ago at this point. We had been using an old iteration of memcache on Windows as the data cache per server for while and had for whatever reason opted to store our session data (to which the application is heavily dependent) in App Fabric. App Fabric had come to EOL and we needed to move away from it. As a quick search showed throughput capacity to be higher and overall features of Redis were better we initially implemented it. The number of changes required were minimal and we were able to migrate away to a more resilient system pretty quickly.
 We hit a snag in that the implementation of the Redis session handler at that point only took a single IP so we had to do use keepalived and HAProxy to display the application consistently between master and slave failovers. This caused issues on occasion of dropped connections to the backend service. We upgraded our client and could put both members into our config files and it stopped timing out. We were all happy in this and it was (for it's own part) a significant upgrade. Generally performance was better for all pages. 
 We found however, that our application was serializing all requests and locking on the thread via session lock for a great many things and this caused us and our users considerable headaches on occasion. We found that the implementation of the couchbase session handler gave us the option of ignoring session write locks and not be required to rewrite dozens of pages to handle the no session requirement as the application was working fine without the need to be threadsafe. Though the maximum throughput was not as good compared to Redis the application performance was considerably better as a result of the change. The multi-master write was a big benefit and the cross data center replication was a nice thing to have as that would allow our users to remain logged in even across DataCenter fail-over events (praying that never happened). Overall we used that for session handling and chose to use couchbase (in a 2nd cluster) to handle memcache requests as that gave us greater capacity to handle larger objects more efficiently. 
 We are, all these years later, looking to move into the newer features of couchbase to give us more and better use of this product that really has been the answer to a bunch of the growing pains we experienced. Since the decision performance has not been on wild rides and stability has never been better. So I sing the praises of couchbase to anyone that will listen.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of IronDB
Pros of Memcached
    Be the first to leave a pro
    • 137
      Fast object cache
    • 128
      High-performance
    • 90
      Stable
    • 65
      Mature
    • 33
      Distributed caching system
    • 11
      Improved response time and throughput
    • 3
      Great for caching HTML
    • 2
      Putta

    Sign up to add or upvote prosMake informed product decisions

    Cons of IronDB
    Cons of Memcached
      Be the first to leave a con
      • 2
        Only caches simple types

      Sign up to add or upvote consMake informed product decisions

      What is IronDB?

      IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted.

      What is Memcached?

      Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use IronDB?
      What companies use Memcached?
        No companies found
        See which teams inside your own company are using IronDB or Memcached.
        Sign up for Private StackShareLearn More

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with IronDB?
        What tools integrate with Memcached?
          No integrations found

          Sign up to get full access to all the tool integrationsMake informed product decisions

          Blog Posts

          Dec 22 2020 at 9:26PM

          Pinterest

          +4
          10
          2329
          Jun 6 2019 at 5:11PM

          AppSignal

          +9
          15
          1141
          +17
          33
          29929
          +47
          49
          69271
          +26
          19
          4615
          +42
          52
          19835
          +25
          7
          2828
          What are some alternatives to IronDB and Memcached?
          InfluxDB
          InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.
          MySQL
          The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
          PostgreSQL
          PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
          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.
          Microsoft SQL Server
          Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.
          See all alternatives