Apache Configuration: Optimization, Security, and Caching

Imagine: a WordPress e-commerce store with 1000 unique visitors per hour throws a 503 error. Typical picture — Apache has exhausted MaxClients, and PHP-FPM is not configured. Without caching, every request for static content (CSS, JS, images) loads the server anew — LCP skyrockets past 5 seconds. In 90% of cases, this is solved by switching to PHP-FPM via Unix socket and enabling mod_expires. Over 10 years, we've configured Apache for 500+ projects: from simple landing pages to high-load SaaS. Below is a proven scheme that reduces TTFB by 30% and memory consumption by 40%.

The non-obvious problem is .htaccess. On every request, Apache checks directories from root to DocumentRoot for .htaccess. For deep structures, this can be up to 10 disk operations. We use AllowOverride None and move rules to the VirtualHost config. This speeds up delivery by 15–20%.

Typical problems we solve

• Slow static delivery — without mod_expires and mod_deflate, the browser re-requests files every time, LCP grows by 30%.
• Insecure VirtualHosts — open directories, outdated protocols, missing HSTS.
• Incorrect .htaccess — Laravel breaks due to missing RewriteRule, .env accessible from outside.
• PHP-FPM over TCP instead of Unix socket — an extra 20% latency on localhost.
• No rate limiting — a single client can download all content in seconds.

How we configure Apache turnkey

Our stack: Apache 2.4+, PHP 8.3 (FPM via socket), Laravel, WordPress, any CMS. For each project, we create a production-ready config tailored to the load. Here's an example for Laravel:

<VirtualHost *:443>
    ServerName example.com
    DocumentRoot /var/www/myapp/current/public

    SSLEngine on
    SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem
    Protocols h2 http/1.1

    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
    Header always set X-Frame-Options "DENY"

    <Directory /var/www/myapp/current/public>
        AllowOverride All
        Require all granted
        Options -Indexes
    </Directory>

    <FilesMatch \.php$>
        SetHandler "proxy:unix:/var/run/php/php8.3-fpm.sock|fcgi://localhost"
    </FilesMatch>

    <FilesMatch "\.(css|js|jpg|png|gif|ico|svg|woff2)$">
        Header set Cache-Control "public, max-age=31536000, immutable"
    </FilesMatch>

    ErrorLog ${APACHE_LOG_DIR}/myapp-error.log
    CustomLog ${APACHE_LOG_DIR}/myapp-access.log combined
</VirtualHost>

<VirtualHost *:443>
    ServerName blog.example.com
    DocumentRoot /var/www/wp/current

    SSLEngine on
    SSLCertificateFile /etc/letsencrypt/live/blog.example.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/blog.example.com/privkey.pem
    Protocols h2 http/1.1

    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
    Header always set X-Content-Type-Options "nosniff"

    <Directory /var/www/wp/current>
        AllowOverride None
        Require all granted
        Options -Indexes +FollowSymLinks
        # WordPress rewrite rules
        RewriteEngine On
        RewriteBase /
        RewriteRule ^index\.php$ - [L]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule . /index.php [L]
    </Directory>

    <FilesMatch \.php$>
        SetHandler "proxy:unix:/var/run/php/php8.3-fpm.sock|fcgi://localhost"
    </FilesMatch>

    <IfModule mod_expires.c>
        ExpiresActive On
        ExpiresByType image/jpg "access plus 1 year"
        ExpiresByType image/jpeg "access plus 1 year"
        ExpiresByType image/gif "access plus 1 year"
        ExpiresByType image/png "access plus 1 year"
        ExpiresByType text/css "access plus 1 month"
        ExpiresByType application/javascript "access plus 1 month"
    </IfModule>

    <IfModule mod_deflate.c>
        AddOutputFilterByType DEFLATE text/html text/css application/json application/javascript
        DeflateCompressionLevel 6
    </IfModule>

    ErrorLog ${APACHE_LOG_DIR}/wp-error.log
    CustomLog ${APACHE_LOG_DIR}/wp-access.log combined
</VirtualHost>

What is included in the work

• Audit of the current Apache configuration.
• Setup of VirtualHost, SSL (Let's Encrypt), HSTS.
• Optimization of MPM event, gzip, caching.
• .htaccess tuned for your CMS (Laravel, WordPress, Drupal).
• Implementation of rate limiting and security headers.
• Load testing (ab, siege) and handover of documentation.
• Training your team on configuration management and post-deployment support.

MPM and caching optimization for high-load projects

The first step is choosing the MPM. For dynamic PHP sites, use mpm_event. Optimization example:

<IfModule mpm_event_module>
    StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxRequestWorkers   150
    MaxConnectionsPerChild 0
</IfModule>

Then enable compression and caching:

<IfModule mod_deflate.c>
    AddOutputFilterByType DEFLATE text/html text/css application/json application/javascript
    DeflateCompressionLevel 6
</IfModule>

<IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType text/css              "access plus 1 year"
    ExpiresByType application/javascript "access plus 1 year"
    ExpiresByType image/jpeg             "access plus 1 year"
    ExpiresByType image/png              "access plus 1 year"
</IfModule>

A common mistake is using mod_php instead of PHP-FPM. The former consumes 40% more memory under peak load. Switching to PHP-FPM reduces TTFB by 15% and doubles throughput.

Why use PHP-FPM with Apache?

PHP-FPM over Unix socket reduces latency by 20% on localhost compared to TCP. Moreover, mod_php consumes 40% more memory under peak loads because each Apache process carries the interpreter. PHP-FPM allows flexible pool management and separate php.ini configuration.

How Apache differs from Nginx and when to choose it

Apache is better than Nginx in two cases: when .htaccess is critical (shared hosting) or when using modules like mod_ldap, mod_authnz_ldap. Otherwise, Nginx gives 30% more RPS on static content.

Comparison of Apache MPM modules

Work process for Apache configuration

1. Analysis: study current config, load, CMS.
2. Design: select MPM, modules, caching parameters.
3. Implementation: configure VirtualHost, SSL, .htaccess, rate limiting.
4. Testing: check LCP, CLS, TTFB via Lighthouse, load testing.
5. Deployment: apply config, monitor logs, hand over documentation.

Common mistakes we avoid:

• Missing Header always set X-Content-Type-Options "nosniff".
• Incorrect DocumentRoot permissions (should be 755, not 777).
• Using mod_php instead of PHP-FPM — 40% more memory consumption.

Estimated timelines

Basic Apache setup with PHP-FPM takes from 1 day. Full cycle with optimization, security, and load testing — up to 3 days. The cost is calculated individually. Order a configuration audit — we will assess your project and offer a turnkey solution. Get an Apache configuration that meets best practices with guaranteed stable operation under peak load. Contact us for a consultation on your project.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.