Slim leaves many architectural choices to the application. A small set of conventions for dependency injection, middleware and route registration prevents a growing API from becoming a single file of callbacks.
Register dependencies
Use a PSR-compatible container integration when the project needs it. Register application services and infrastructure adapters in a composition root. Prefer constructor injection in ordinary classes so required dependencies are visible.
Build a middleware pipeline
Place request-wide concerns such as request IDs, authentication and error handling in middleware. Keep route-specific authorization close to the route or application action. Document execution order because middleware wraps downstream processing.
Organize routes by feature
Group related routes and keep handlers thin. Validate input before calling application services. Return PSR-7 responses with deliberate status codes and content types.
Test composition and behavior
Test middleware independently and exercise representative routes through the application. Include tests for ordering-sensitive behavior such as authentication before a protected handler.
Further reading
- Slim middleware: https://www.slimframework.com/docs/v4/concepts/middleware.html
- PHP-FIG PSR standards: https://www.php-fig.org/psr/