litestar-di

Define an async provider function and register it in the dependencies dict, for example dependencies={"db_session": Provide(provide_session)} on the Litestar app, router, controller, or route handler. Litestar resolves the value by name when a handler declares it as a parameter.

Stay on Provide() for small apps with under roughly ten dependencies and flat graphs. Move to Dishka when you need explicit cross-scope management (app singletons plus request transients), repetitive hand-wiring, or shared services across CLI and HTTP entry points.

Create Provider classes with a Scope, build a container via make_async_container, and call setup_dishka(container, app). Handlers then declare parameters annotated with FromDishka (aliased as Inject[T]) to trigger resolution per request.

Same-name lookups resolve inward: a handler-level dependency overrides the controller's, which overrides the app's. This lets tests or specific routes replace providers without changing global registration.

Opening database sessions or clients at import time creates global mutable state that leaks across requests and breaks scope lifetimes. Providers should create and close such resources within their declared scope so tests can override them cleanly.