Hands-On Design Patterns with Swift

Why you should use a DI Container

We have seen that Dependency Injection can be achieved by implementing the right constructor and binding the dependencies at the start of the app, without using a third-party framework.

However, sometimes using one of these containers could help to ensure a uniform architecture, which is helpful when you have a really big development team. If the container you choose is used in several apps, you can be sure that it's often more robust than an internally-developed one. If the dependencies are fixed and don't change during the life of the app, injecting manually is probably better, but if the dependencies are dynamic and change for different reasons, a DI container should permit to have a more flexible code ...