All insights
Insight · Web Development

Laravel 12 in Production: Patterns We Reach For Every Build

Queues, Pulse, Octane, Pennant — a tour of the Laravel 12 features that earn their keep on real production workloads.

Bilal AhmedMarch 18, 20268 min read
Laravel 12 in Production: Patterns We Reach For Every Build

01 · Section

Queues are not optional anymore

Any Laravel app that sends an email, hits a third-party API, or processes an upload should be using queues. Horizon makes Redis-backed queues trivial to run, observe and scale — there is no excuse to be running these jobs synchronously in 2026.

Default to the queue. Move work back to sync only when the data dependency forces it. The fastest controllers we ship return a 202 and let workers do the rest.

02 · Section

Octane changes the cost model

Octane keeps the framework booted between requests via Swoole or FrankenPHP. P95 response times typically drop 40–70% on cold endpoints, and a single small server now handles traffic that previously needed three.

Watch for state leakage — singletons that previously died with the request now persist. Audit every binding and middleware once before going live, and the rest is free performance.

03 · Section

Pulse and Pennant cover the gaps

Pulse gives you slow queries, slow jobs, slow requests and exception spikes in one dashboard — no Datadog bill required for small and mid-size teams.

Pennant ships feature flags as a first-class primitive. Combined with Laravel's scoped configuration, gradual rollouts and kill switches stop being a custom build.

Key takeaways

  • Default to queues; sync should be the exception, not the rule.
  • Run Octane in production — the upside far outweighs the audit cost.
  • Use Pulse before reaching for a paid APM on small/mid-size apps.
  • Adopt Pennant for feature flags rather than rolling your own.

Tags

#Laravel#PHP#Queues#Octane#Architecture
BA

Written by

Bilal Ahmed

8 min read · Posted in Web Development

Need help shipping this?

Turn ideas in articles into products in production.

We're the team that builds what these posts describe.