Being lazy doesn’t refer to being lazy in life, but being lazy about the creation or instantiation of objects in our code. Sometimes, creation of an object is very costly. Now, when we say “costly”, we are not talking about money. Rather, we are talking about the memory consumed in the process and by the object itself.

Consider a component A that uses a service B. It is very likely for class A to have methods that do not use the object of class B. Please refer the code below:

If we are using class A for MethodTwo and MethodThree only, we will overburden the run time to instantiate B, which, in fact, will never be used. So, how do we handle it?


Using Lazy <T>

When we inject a dependency as Lazy<T>, we delay the construction of part of the object graph either for functional or performance reasons. Moreover, Lazy<T> will be automatically injected, as long as T is registered with the DI container.

Lazy<T> represents a value that is initialized the first time it is accessed. Therefore, the above code can be written as the following:


As a result, class B object will be instantiated only when we access it for the first time. This is to say, that the object instantiation takes place at line _b.Value.ClassBMethod(); and the object will remain in memory for any further use. Not to mention, if we create an object of class A and call the methods MethodTwo and MethodThree, class B will not be instantiated.

This is certainly one way of using lazy initialization. We can also use Lazy<T,TMetadata>. It works exactly the same way as Lazy<T>, but adds a Metadata property that can be used to get information about the value before it is instantiated. To know more about it, please stay tuned. 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.