A Production-Ready Laravel Architecture with Traefik and FrankenPHP
A practical guide to deploying a high-performance Laravel stack using Octane, FrankenPHP, and a fully automated Docker Compose workflow.
Laravel is a very performant framework, but a standard architecture has one big flaw derived from how PHP works: It has to rebuild the entire framework on every single request.
Even with optimizations, this process still takes 40 to 60 ms on my machine with PHP 8.4. Luckily, for years, the PHP and Laravel worlds have had a solution that dramatically reduces this load time: Laravel Octane and FrankenPHP. The booting time for the Laravel framework can drop to just 4 to 6 ms per request. Incredible, isn't it?
Nice architectural overview — combining a traditionally synchronous PHP framework with modern edge/proxy tooling really highlights the production context trade-offs that matter.
In real systems, the first bottleneck you hit isn’t nominal request throughput but how predictable your routing, load balancing, and error boundaries are under load (e.g., Traefik readiness/liveness checks, backpressure, HTTP/2 vs keepalives).
From a performance and observability standpoint, I’d be curious which metric or signal you treat as the first real indicator that this stack is production-ready — p95 response time under load, 5xx rates escaping health checks, queue drain times, or something else? That usually dictates where you invest next (caching, worker size, autoscaling).
sorry for late reply, i actually built https://laraplugins.io/ too, here i handle 3 million requests per month, serve mcp traffic and handle multiple hundreds thousands of jobs per month. all self hosted on one vps with 4 core and 8gb or ram.