Question

I have a singleton service with a dependency on a service with a request scoped lifecycle.

If I allow the container to inject the request scoped service when I first get the singleton it will be fine for the current request but will be disposed of in any subsequent request.

Does this mean I have to use the dependency container to create the request scoped service within the singleton?

Answer 1

I wouldn’t recommend injecting the container itself in your singleton service. Instead:

• abstract the creation of your request-scoped service behind a factory, and inject the factory, or
• change your singleton’s scope and make it request-scoped. This shouldn’t be a problem unless the instantiation of the service is expensive.