A corollary to the Composition Root and Register Resolve Release patterns is that object graphs should be composed up front, sometimes well in advance to when a particular dependency is needed. Such object graphs can potentially become quite big, which tends to make some people uneasy. Isn't it terribly inefficient? No, it almost never is, and in the few cases where it is, there are ways to get around it.
This session examines big object graphs composed with and without Dependency Injection containers, using simple code examples.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?