memcached

Memcached distributed memory caching. Use for simple caching.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

memcached is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Memcached distributed memory caching. Use for simple caching.

Teams using memcached should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/memcached/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/databases/memcached/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/memcached/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How memcached Compares

Feature / Agent	memcached	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Memcached distributed memory caching. Use for simple caching.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Memcached

Memcached is a high-performance, distributed memory object caching system. It is simpler than Redis. It does arguably one thing: Key-Value caching of strings/objects in RAM.

## When to Use

- **Simple Caching**: Pure LRU cache.
- **Multi-Threaded**: Memcached is multi-threaded (Redis is single-threaded). It scales vertically better on massive multicore machines for simple GET/SET throughput.
- **Session Cache**: Storing web sessions.

## Quick Start

```bash
# Telnet interface
set mykey 0 60 4
data
STORED

get mykey
VALUE mykey 0 4
data
END
```

## Core Concepts

### Slab Allocation

Memcached manages memory in "Classes" of chunks (Slabs) to prevent fragmentation.

### LRU (Least Recently Used)

When full, it evicts the oldest unused items.

### No Persistence

If you restart, data is gone.

## Best Practices (2025)

**Do**:

- **Use for huge read-heavy loads**: Facebook uses it heavily.
- **Use Serialization**: Store Protobuf or msgpack for efficiency.

**Don't**:

- **Don't use as a Datastore**: It is a cache _only_.
- **Don't use iterating**: You cannot "List all keys". You must know the key to get the value.
- **Comparison to Redis**: In 2025, Redis is generally preferred for features. Use Memcached if you specifically need multi-threaded scaling for pure String caching.

## References

- [Memcached Wiki](https://github.com/memcached/memcached/wiki)