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. Memcached vs MySQL

Memcached vs MySQL

OverviewDecisionsComparisonAlternatives

Overview

MySQL
MySQL
Stacks129.6K
Followers108.6K
Votes3.8K
GitHub Stars11.8K
Forks4.1K
Memcached
Memcached
Stacks7.9K
Followers5.7K
Votes473
GitHub Stars14.0K
Forks3.3K

Memcached vs MySQL: What are the differences?

Introduction

Memcached and MySQL are both widely used technologies in the field of web development. While they both serve the purpose of storing and managing data, there are key differences between the two that set them apart. In this article, we will explore these differences to understand when and how to use each technology in a web project.

  1. Scalability: One key difference between Memcached and MySQL is their approach to scalability. Memcached is designed to be a distributed caching system, allowing for horizontal scaling by adding more servers to the cache pool. On the other hand, MySQL is a relational database management system, which can scale vertically by adding more powerful hardware. This difference makes Memcached more suitable for handling high traffic and read-heavy workloads, while MySQL is better suited for complex data relationships and write-intensive operations.

  2. Data Structure: Memcached and MySQL also differ in terms of data structure. Memcached is a key-value store, where data is stored and retrieved based on a unique key. This makes it fast and efficient for simple lookups and retrieval operations. In contrast, MySQL is a relational database that supports structured and organized data, allowing for complex queries, indexing, and relationships between different tables. This makes MySQL a better choice when dealing with complex data structures and queries that involve multiple tables.

  3. Data Persistence: Another important difference between Memcached and MySQL is data persistence. Memcached is primarily an in-memory cache, which means that the data stored in Memcached is temporary and can be lost in case of a cache restart or failure. On the other hand, MySQL is a disk-based database that provides data durability and persistence. This makes MySQL a better choice for applications that require long-term storage and data persistence, where data loss is not acceptable.

  4. Query Language: Memcached and MySQL also differ in terms of the query language they use. Memcached does not provide a SQL query language and supports only basic operations like get, set, and delete. In contrast, MySQL supports the SQL query language, which allows for complex data manipulation, filtering, sorting, and joining operations. This makes MySQL more powerful and flexible in terms of data retrieval and manipulation capabilities compared to Memcached.

  5. Transaction Support: Memcached and MySQL also differ in terms of transaction support. Memcached does not provide built-in support for transactions, making it unsuitable for applications that require ACID (Atomicity, Consistency, Isolation, Durability) properties. On the other hand, MySQL provides full ACID compliance and supports transactions, making it suitable for applications that require data consistency and integrity.

  6. Data Types: Lastly, Memcached and MySQL differ in terms of supported data types. Memcached supports only basic data types like strings, integers, and binary data. MySQL, on the other hand, supports a wide range of data types including strings, integers, floats, dates, and more. This makes MySQL more versatile in terms of storing and manipulating different types of data compared to Memcached.

In summary, Memcached and MySQL differ in terms of scalability, data structure, data persistence, query language, transaction support, and supported data types. Understanding these key differences is crucial for choosing the right technology for your web project based on its requirements and expected workload.

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 MySQL, Memcached

Kyle
Kyle

Web Application Developer at Redacted DevWorks

Dec 3, 2019

DecidedonPostGISPostGIS

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

449k views449k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Navraj
Navraj

CEO at SuPragma

Apr 16, 2020

Needs adviceonMySQLMySQLPostgreSQLPostgreSQL

I asked my last question incorrectly. Rephrasing it here.

I am looking for the most secure open source database for my project I'm starting: https://github.com/SuPragma/SuPragma/wiki

Which database is more secure? MySQL or PostgreSQL? Are there others I should be considering? Is it possible to change the encryption keys dynamically?

Thanks,

Raj

401k views401k
Comments

Detailed Comparison

MySQL
MySQL
Memcached
Memcached

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.

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.

Statistics
GitHub Stars
11.8K
GitHub Stars
14.0K
GitHub Forks
4.1K
GitHub Forks
3.3K
Stacks
129.6K
Stacks
7.9K
Followers
108.6K
Followers
5.7K
Votes
3.8K
Votes
473
Pros & Cons
Pros
  • 800
    Sql
  • 679
    Free
  • 562
    Easy
  • 528
    Widely used
  • 490
    Open source
Cons
  • 16
    Owned by a company with their own agenda
  • 3
    Can't roll back schema changes
Pros
  • 139
    Fast object cache
  • 129
    High-performance
  • 91
    Stable
  • 65
    Mature
  • 33
    Distributed caching system
Cons
  • 2
    Only caches simple types

What are some alternatives to MySQL, Memcached?

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.

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.

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.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

InfluxDB

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.

CouchDB

CouchDB

Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript.

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