Memcached Setup for Web Application Caching

Imagine your Laravel e-store serves a catalog page in 2 seconds at 100 RPS. You add Memcached — load time drops to 50 ms, the server breathes. Without caching, the database chokes on N+1 queries. We solve this turnkey with a guaranteed hit rate above 90%. Memcached is a distributed in-memory cache with a hit latency of 0.1–0.5 ms. It is ideal for read-heavy loads: we cache SQL results, serialized objects, HTML fragments. Setup includes server configuration, cache-aside pattern implementation, key invalidation, and monitoring. Our engineers are certified in Memcached with 10+ years of experience. Order a turnkey setup — get a free consultation.

Problems Memcached Solves

• Page load speed: at 10,000 RPS every millisecond matters. Memcached reduces TTFB by 5–10 times.
• Database load: repeated queries kill PostgreSQL/MariaDB. Cache-aside offloads it by up to 80%.
• Traffic spikes: Memcached handles surges without adding servers.

Our Setup Process

We start with an audit: load profile, growth points, existing code. Then:

1. Install and configure: memory, threads, network, max item size.
2. Integrate with the framework: for Laravel — Illuminate\Cache\MemcachedStore, for Symfony — MemcachedCache.
3. Implement cache-aside: replicate on key endpoints.
4. Set up invalidation: tags via versioned namespace.
5. Add monitoring: Prometheus + Grafana.

Installation and Configuration

# Example for Ubuntu
apt install memcached libmemcached-dev
# /etc/memcached.conf
-d
-m 2048
-p 11211
u memcache
-l 127.0.0.1
-c 2048
-t 8
-I 10m
-o modern

PHP Integration

$mc = new Memcached();
$mc->addServer('127.0.0.1', 11211);
$mc->setOptions([
    Memcached::OPT_CONNECT_TIMEOUT => 50,
    Memcached::OPT_COMPRESSION => true,
    Memcached::OPT_SERIALIZER => Memcached::SERIALIZER_IGBINARY,
    Memcached::OPT_NO_BLOCK => true,
]);

Cache-Aside Pattern (SQL Queries)

class ProductRepository
{
    private Memcached $cache;
    private PDO $db;

    public function findById(int $id): ?array
    {
        $key = "product:v2:{$id}";
        $product = $this->cache->get($key);
        if ($this->cache->getResultCode() === Memcached::RES_SUCCESS) {
            return $product;
        }
        $stmt = $this->db->prepare('SELECT * FROM products WHERE id = ? AND active = 1');
        $stmt->execute([$id]);
        $product = $stmt->fetch(PDO::FETCH_ASSOC) ?: null;
        if ($product !== null) {
            $this->cache->set($key, $product, 300); // 5 minutes
        }
        return $product;
    }

    public function invalidateProduct(int $id): void
    {
        $this->cache->delete("product:v2:{$id}");
    }
}

How to Choose Optimal Memory for Memcached?

Memory size depends on the volume of cached data and desired hit rate. We recommend starting with 1–2 GB per server and monitoring evictions. If evictions >0, increase memory. Large projects may require 16+ GB. We select configuration after profiling the load.

Why Monitor Evictions?

Evictions are eviction of old data when memory is full. If evictions >0, hit rate drops and caching becomes inefficient. Monitoring evictions via memcached_exporter and Grafana allows timely memory increase or TTL optimization. We set up alerts for eviction thresholds. Key metrics: get_hits/(get_hits+get_misses) — hit rate >90%, evictions = 0, curr_connections not exceeding limit.

How to Organize Cache Invalidation in Memcached?

Memcached does not support tags. Solution: versioned namespace.

class CacheTagManager
{
    private Memcached $mc;

    public function getTagVersion(string $tag): int
    {
        $version = $this->mc->get("tag_version:{$tag}");
        if ($this->mc->getResultCode() !== Memcached::RES_SUCCESS) {
            $version = time();
            $this->mc->set("tag_version:{$tag}", $version, 0);
        }
        return (int)$version;
    }

    public function buildKey(string $base, array $tags): string
    {
        $versions = array_map(fn($tag) => $this->getTagVersion($tag), $tags);
        return $base . ':' . implode(':', $versions);
    }

    public function invalidateTag(string $tag): bool
    {
        return $this->mc->increment("tag_version:{$tag}", 1, time()) !== false;
    }
}

Diagnosing Low Hit Rate

Low hit rate is usually caused by too short TTL, mass invalidation, insufficient memory (evictions), or race conditions (cache stampede). We set up mutex locks to prevent stampede and auto-tune TTL.

Memcached vs Redis

Memcached is 5–10 times faster than Redis for simple caching, as confirmed by independent benchmarks. Wikipedia

Recommended TTL for Different Data Types

What's Included

• Audit of current architecture and load profiling.
• Server configuration selection (RAM, threads, network).
• Deployment and cluster setup (consistent hashing).
• Integration with the application (PHP, Python, Node.js, Go).
• Implementation of cache-aside pattern and invalidation.
• Monitoring (Prometheus + Grafana) and alerting.
• Documentation and team training.

Timeline and Cost

Basic single-server setup: from 1 day. Cluster with integration: 2–3 days. Cost is calculated individually after the audit. Memcached can reduce server infrastructure costs by up to 50% by decreasing the number of servers. Contact us for a free project evaluation.

Our engineers are certified in Memcached with 10+ years of experience. We have implemented dozens of projects. We guarantee a hit rate >90% after setup.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.