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. Databases
  4. Databases
  5. Kafka vs Memcached

Kafka vs Memcached

OverviewDecisionsComparisonAlternatives

Overview

Memcached
Memcached
Stacks7.9K
Followers5.7K
Votes473
GitHub Stars14.0K
Forks3.3K
Kafka
Kafka
Stacks24.2K
Followers22.3K
Votes607
GitHub Stars31.2K
Forks14.8K

Kafka vs Memcached: What are the differences?

Introduction

In this article, we will explore the key differences between Kafka and Memcached. Kafka and Memcached are both popular distributed data processing systems, but they serve different purposes and have distinct features.

  1. Scalability and Persistence: Kafka is designed to handle large amounts of data and provide fault-tolerant distributed messaging at scale. It is a distributed streaming platform that can handle terabytes of data in real-time. On the other hand, Memcached is an in-memory caching system that allows applications to store and retrieve data in memory quickly. While Kafka is highly scalable and supports persistent storage, Memcached is primarily focused on fast in-memory caching and does not offer persistence.

  2. Data Processing Paradigm: Kafka follows the publish-subscribe model, where producers publish messages to topics, and consumers subscribe to these topics to receive the messages. It allows for real-time data streaming and supports both stream processing and batch processing. Memcached, on the other hand, is not designed for data processing. It serves as a key-value store, where applications can store and retrieve data based on keys.

  3. Message Storage: Kafka maintains a log-based storage system that guarantees ordered, durable, and fault-tolerant message storage. It stores messages on disk and allows for replaying and reprocessing of messages. Memcached, being an in-memory caching system, stores data in memory and does not provide durable storage. If the system restarts or crashes, the data stored in Memcached is lost.

  4. Data Persistence: Kafka stores messages on disk, ensuring that data is persisted even in the case of failures. It supports fault tolerance, replication, and data durability. Memcached, being an in-memory caching system, does not provide data persistence and relies on external systems for data storage.

  5. Data Eviction: Kafka does not have built-in data eviction mechanisms. Once messages are stored in Kafka, they are retained until a configurable retention period or size limit is reached. On the other hand, Memcached implements a caching strategy that evicts data based on a set of predefined policies. When the cache is full, the least recently used (LRU) items are removed to make space for new data.

  6. Data Access: Kafka provides a unified log-based abstraction for both data producers and consumers. It allows consumers to pull data from any offset in the log, enabling replayability and fault-tolerance. Memcached, being a key-value store, allows data retrieval based on keys. Applications can directly access specific data by providing the corresponding key.

In summary, Kafka is a distributed streaming platform designed for real-time data processing, while Memcached is an in-memory caching system for fast data retrieval. Kafka supports persistence, fault tolerance, and ordered message storage, while Memcached offers fast in-memory caching without persistence.

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

Advice on Memcached, Kafka

viradiya
viradiya

Apr 12, 2020

Needs adviceonAngularJSAngularJSASP.NET CoreASP.NET CoreMSSQLMSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k
Comments
Ishfaq
Ishfaq

Feb 28, 2020

Needs advice

Our backend application is sending some external messages to a third party application at the end of each backend (CRUD) API call (from UI) and these external messages take too much extra time (message building, processing, then sent to the third party and log success/failure), UI application has no concern to these extra third party messages.

So currently we are sending these third party messages by creating a new child thread at end of each REST API call so UI application doesn't wait for these extra third party API calls.

I want to integrate Apache Kafka for these extra third party API calls, so I can also retry on failover third party API calls in a queue(currently third party messages are sending from multiple threads at the same time which uses too much processing and resources) and logging, etc.

Question 1: Is this a use case of a message broker?

Question 2: If it is then Kafka vs RabitMQ which is the better?

804k views804k
Comments
Roman
Roman

Senior Back-End Developer, Software Architect

Feb 12, 2019

ReviewonKafkaKafka

I use Kafka because it has almost infinite scaleability in terms of processing events (could be scaled to process hundreds of thousands of events), great monitoring (all sorts of metrics are exposed via JMX).

Downsides of using Kafka are:

  • you have to deal with Zookeeper
  • you have to implement advanced routing yourself (compared to RabbitMQ it has no advanced routing)
10.9k views10.9k
Comments

Detailed Comparison

Memcached
Memcached
Kafka
Kafka

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.

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

-
Written at LinkedIn in Scala;Used by LinkedIn to offload processing of all page and other views;Defaults to using persistence, uses OS disk cache for hot data (has higher throughput then any of the above having persistence enabled);Supports both on-line as off-line processing
Statistics
GitHub Stars
14.0K
GitHub Stars
31.2K
GitHub Forks
3.3K
GitHub Forks
14.8K
Stacks
7.9K
Stacks
24.2K
Followers
5.7K
Followers
22.3K
Votes
473
Votes
607
Pros & Cons
Pros
  • 139
    Fast object cache
  • 129
    High-performance
  • 91
    Stable
  • 65
    Mature
  • 33
    Distributed caching system
Cons
  • 2
    Only caches simple types
Pros
  • 126
    High-throughput
  • 119
    Distributed
  • 92
    Scalable
  • 86
    High-Performance
  • 66
    Durable
Cons
  • 32
    Non-Java clients are second-class citizens
  • 29
    Needs Zookeeper
  • 9
    Operational difficulties
  • 5
    Terrible Packaging

What are some alternatives to Memcached, Kafka?

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.

MySQL

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

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.

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

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.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

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