关于PHP-DI编译时需手动Autowire的类范围的技术咨询

Great question—this is a common pain point when optimizing PHP-DI for large-scale applications, so let’s break this down clearly:

You Don’t Need to Autowire Every Class #

First, let’s clarify: PHP-DI will automatically attempt to autowire most classes at runtime by default, even if you don’t explicitly list them in your config. The autowire() directive in your compile-time config is specifically for pre-compiling the dependency resolution logic to avoid costly runtime reflection.

That means you don’t need to add every single class in your app—focus on the ones that will give you the biggest performance boost.

Prioritize These Classes #

Start with these categories to get the most value:

• Controllers: As you guessed, these are critical because every request hits a controller. Pre-compiling their autowiring eliminates reflection overhead on every request.
• Core Service Classes: Think database connections, cache clients, central business logic services, or any service that’s instantiated frequently across your app. These are used constantly, so pre-compiling their dependencies pays off.
• Complex Dependencies: If a class has a deep dependency tree (e.g., a service that depends on multiple other services), runtime reflection for that chain can add up. Pre-compiling these cuts that overhead entirely.

Skip These Classes (Most of the Time) #

You can safely leave these out unless you notice specific performance issues:

• Simple DTOs/Value Objects: Classes with no dependencies or only primitive types have negligible reflection overhead. PHP-DI can resolve them quickly at runtime without pre-compilation.
• Rarely Used Classes: Tools or services that are only called in edge cases (e.g., a one-off export service) don’t justify the config overhead or compile time.
• Classes with Custom Definitions: If you’ve already defined a class with a factory(), instance(), or custom binding, you don’t need autowire()—PHP-DI will use your custom logic instead.

Pro Tip for Large Apps: Batch Autowire by Namespace #

Instead of listing every controller or service individually, use wildcard patterns to batch entire namespaces. This keeps your config clean and scalable:

return [
    // Autowire all controllers in the App\Controller namespace
    'App\\Controller\\*' => autowire(),
    // Autowire core services
    'App\\Service\\Core\\*' => autowire(),
    // Add other high-priority namespaces as needed
];

How to Refine Your List #

If you’re unsure where to draw the line:

1. Start with controllers and core services—this gives you immediate performance gains.
2. Use PHP-DI’s built-in profiling or your app’s performance monitoring to identify classes that are triggering frequent reflection.
3. Add those high-reflection classes to your compile config incrementally.

内容的提问来源于stack exchange，提问作者sridesmet