MVC Module Loading vs. Mezzio Middleware‑Only: Is the Startup Cost Worth the MVC Convenience?

Background

Laminas MVC loads every configured module and its services on each request. Even with lazy listeners, the fixed cost of parsing module configuration files and bootstrapping the event manager inflates memory usage and request‑startup time. Mezzio, on the other hand, allows an application to be built from a minimal set of middleware, loading only the code required for the matched route. Benchmarks on a simple hello‑world endpoint show a 30‑50 % reduction in startup time compared to a default MVC skeleton with three modules.

The core trade‑off for a low‑traffic workload is whether the measurable performance gain justifies losing MVC conveniences such as module‑based configuration merging, automatic view model injection, and shared event manager support.

Unresolved Decision

While both frameworks support lazy service factories, MVC still incurs a fixed bootstrap cost that may outweigh the benefits for sites with minimal traffic. Mezzio requires rewriting controllers as middleware, which could introduce migration overhead and break plugins that rely on MVC events.

Given these constraints, the following questions remain:

• Does the ~30‑50 % startup time reduction in Mezzio outweigh the loss of MVC’s module‑based configuration merging for low‑traffic workloads?
• Will the need to rewrite controllers as middleware negate the memory savings in a typical low‑traffic scenario?
• Is enabling lazy service factories in MVC sufficient to bring its memory usage within acceptable limits for low‑traffic sites?