Cut your Dependencies with Dependency Injection for East Bay.NET User Group

46
Cut your Dependencies Dependency Injection Berkeley, February 14th 2013 East Bay.NET

description

Dependency injection is a design patter with the potential to write cleaner code. Over the lifetime of a product, maintaining the product is actuall one - if the the most - expensive areas of the overall product costs. Writing clean code can significantly lower these costs. Writing clean code also makes you more efficient during the initial development time and results in a more stable code base. In this talk, we will dive into the basics of Inversion of Control (IoC) and Dependency Injection (DI) to review different ways of achieving decoupling. We will explorer best practices, design, and anti-patterns.

Transcript of Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Page 1: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Cut your DependenciesDependency

InjectionBerkeley, February 14th 2013

East Bay.NET

Page 2: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Theo Jungeblut• Engineering manager & lead by day

at AppDynamics in San Francisco

• Coder & software craftsman by night, house builder and soon to be dad

• Architects decoupled solutions & crafts maintainable code to last

• Worked in healthcare and factory automation, building mission critical applications, framework & platforms

• Degree in Software Engineeringand Network Communications

• Enjoys cycling, running and [email protected]

www.designitright.net

Page 3: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Rate Session & Win a Shirt

http://www.speakerrate.com/theoj

Page 4: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Where to get the Slides

http://www.slideshare.net/theojungeblut

Page 5: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Overview

• What is the issue?• What is Dependency Injection?• What are Dependencies?• What is the IoC-Container doing for you?• What, how, why?• Q & A

Page 6: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

UI

Service

ProcessorProcessor

Service

ResourcesResources

UI

Processor

A cleanly layered Architecture

Page 7: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

What is the problem?

Page 8: Cut your Dependencies with Dependency Injection for East Bay.NET User Group
Page 9: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

What is Clean Code?

Page 10: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Clean Code is maintainable

Source code must be:• readable & well structured• extensible• testable

Page 11: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Code Maintainability *

Principles Patterns Containers

Why? How? What?

Extensibility Clean Code Tool reuse

* from: Mark Seemann’s “Dependency Injection in .NET” presentation Bay.NET 05/2011

Page 12: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

What is Dependency Injection?

Page 13: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Without Dependency Injectionpublic class ExampleClass{

private logger logger;

public ExampleClass(){

this.logger = new Logger();

this.logger.Log(“Constructor call”);}

}

Page 14: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

public class ExampleClass{

private logger logger;

public ExampleClass(){

this.logger = new Logger();

this.logger.Log(“Constructor call”);}

}

Without Dependency Injection

Avoid

Page 15: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Inversion of Control –

Constructor Injectionhttp://www.martinfowler.com/articles/injection.html

public class ExampleClass{

private logger logger;

public ExampleClass(ILogger logger){

this.logger = logger;if (logger == null){

throw new ArgumentNullException(“logger”);

}

this.logger.Log(“Constructor call”);}

}

Page 16: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Benefits of Dependency InjectionBenefit Description

Late binding Services can be swapped withother services.

Extensibility Code can be extended and reusedin ways not explicitly planned for.

Paralleldevelopment

Code can be developed in parallel.

Maintainability Classes with clearly definedresponsibilities are easier to maintain.

TESTABILITY Classes can be unit tested.

* from Mark Seemann’s “Dependency Injection in .NET”, page 16

Page 17: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

The Adapter Patternfrom Gang of Four, “Design Patterns”

Page 18: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

What are

Dependencies ?

Page 19: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Stable Dependency

“A DEPENDENCY that can be referenced without any detrimental effects.

The opposite of a VOLATILE DEPENDENCY. “

* From Glossary: Mark Seemann’s “Dependency Injection in .NET”

Page 20: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Volatile Dependency“A DEPENDENCY that involves side effects that

may be undesirable at times.

This may include modules that don’t yet exist, or that have adverse requirements on its

runtime environment.

These are the DEPENDENCIES that are addressed by DI.“

* From Glossary: Mark Seemann’s “Dependency Injection in .NET”

Page 21: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Lifetime a Job

for the Container

Page 22: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

“Register, Resolve, Release”“Three Calls Pattern by Krzysztof Koźmic: http://kozmic.pl/

1. Register 2. Resolve

Build up You code

Execute ReleaseClean

up

Page 23: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

What the IoC-Container will do for you

1. Register 2. Resolve

Build up

ReleaseClean up

Page 24: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Separation of Concern (SoC)probably by Edsger W. Dijkstra in 1974

You codeExecu

te

• Focus on purpose of your code• Know only the contracts of the

dependencies• No need to know

implementations• No need to handle lifetime of

the dependencies

Page 25: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

The 3 Dimensions of DI

1.Object Composition2.Object Lifetime3.Interception

Page 26: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Register - Composition Root

• XML based Configuration• Code based Configuration• Convention based (Discovery)

Page 27: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Resolve

Resolve a single object request for example by Constructor Injection by resolving the needed object graph for this object.

Page 28: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Release

Release objects from Container when not needed anymore.

Page 29: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Anti Patterns

Page 30: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Control Freak

http://www.freakingnews.com/The-Puppet-Master-will-play-Pics-102728.asp

Page 31: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

// UNITY Exampleinternal static class Program{ private static UnityContainer unityContainer; private static SingleContactManagerForm singleContactManagerForm;

private static void InitializeMainForm() { singleContactManagerForm = unityContainer.Resolve<SingleContactManagerForm>(); }}

Inversion of Control –

Service Locatorhttp://www.martinfowler.com/articles/injection.html

Page 32: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

// UNITY Exampleinternal static class Program{ private static UnityContainer unityContainer; private static SingleContactManagerForm singleContactManagerForm;

private static void InitializeMainForm() { singleContactManagerForm = unityContainer.Resolve<SingleContactManagerForm>(); }}

Inversion of Control –

Service Locatorhttp://www.martinfowler.com/articles/injection.html

Anti-Pattern

based on Mark Seemann

Page 33: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Inversion of Control –

Setter (Property) Injection

// UNITY Examplepublic class ContactManager : IContactManager{ [Dependency] public IContactPersistence ContactPersistence { get { return this.contactPersistence; }

set { this.contactPersistence = value; } }}

http://www.martinfowler.com/articles/injection.html

Page 34: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Property Injection

+ Easy to understand

- Hard to implement robust

* Take if an good default exists

- Limited in application otherwise

Page 35: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Method Injectionpublic class ContactManager : IContactManager{ …. public bool Save (IContactPersistencecontactDatabaseService, IContact contact) { if (logger == null) {

throw new ArgumentNullException(“logger”); } …. // Additional business logic executed before calling the save

return contactDatabaseService.Save(contact); }}

http://www.martinfowler.com/articles/injection.html

Page 36: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Method Injection

• Needed for handling changing dependencies in method calls

Page 37: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Ambient Contextpublic class ContactManager : IContactManager{ …. public bool Save (….) { …. IUser currentUser = ApplicationContext.CurrentUser; …. }}

* The Ambient Context object needs to have a default value if not assigned yet.

Page 38: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Ambient Context

• Avoids polluting an API with Cross Cutting Concerns

• Only for Cross Cutting Concerns

• Limited in application otherwise

Page 39: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

InterceptionPublic class LoggingInterceptor : IContactManager{ public bool Save(IContact contact) { bool success;

this. logger.Log(“Starting saving’);

success = this.contactManager.Save(contact);

this. logger.Log(“Starting saving’);

return success; }}

Public class ContactManager : IContactManager{ public bool Save(IContact contact) { ….

return Result }}

* Note: strong simplification of what logically happens through interception.

Page 40: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Dependency Injection Container & more• Typically support all types of Inversion of Control mechanisms• Constructor Injection• Property (Setter) Injection• Method (Interface) Injection• Service Locator

•.NET based DI-Container• Unity• Castle Windsor • StructureMap• Spring.NET• Autofac• Puzzle.Nfactory• Ninject• PicoContainer.NET• and more

Related Technology:• Managed Extensibility Framework (MEF)

Page 41: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

The “Must Read”-Book(s)

http://www.manning.com/seemann/

by Mark Seemann

Dependency Injection is a set of software design principles and patterns that enable us to develop loosely coupled code.

Page 42: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Summary Clean Code - DIMaintainability is achieved through:

• Simplification, Specialization Decoupling (KISS, SoC, IoC, DI)

• Dependency InjectionConstructor Injection as default, Property and Method Injection as needed, Ambient Context for Dependencies with a default,Service Locator never

• Registration Configuration by Convention if possible, exception in Code as neededConfiguration by XML for explicit extensibility and post compile setup

• Quality through Testability (all of them!)

Graphic by Nathan Sawaya

courtesy of brickartist.com

Page 43: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Downloads, Feedback & Comments:

Q & A

Graphic by Nathan Sawaya courtesy of brickartist.com

[email protected] www.speakerrate.com/theoj

Page 44: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

References… http://www.manning.com/seemann/http://en.wikipedia.org/wiki/Keep_it_simple_stupidhttp://picocontainer.org/patterns.htmlhttp://en.wikipedia.org/wiki/Dependency_inversion_principlehttp://en.wikipedia.org/wiki/Don't_repeat_yourselfhttp://en.wikipedia.org/wiki/Component-oriented_programminghttp://en.wikipedia.org/wiki/Service-oriented_architecturehttp://www.martinfowler.com/articles/injection.htmlhttp://www.codeproject.com/KB/aspnet/IOCDI.aspxhttp://msdn.microsoft.com/en-us/magazine/cc163739.aspxhttp://msdn.microsoft.com/en-us/library/ff650320.aspxhttp://msdn.microsoft.com/en-us/library/aa973811.aspxhttp://msdn.microsoft.com/en-us/library/ff647976.aspxhttp://msdn.microsoft.com/en-us/library/cc707845.aspxhttp://msdn.microsoft.com/en-us/library/bb833022.aspxhttp://unity.codeplex.com/

Lego (trademarked in capitals as LEGO)

Page 45: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

Blog, Rating, Slides

http://www.DesignItRight.net

www.speakerrate.com/theoj

www.slideshare.net/theojungeblut

Page 46: Cut your Dependencies with Dependency Injection for East Bay.NET User Group

… thanks for you attention!

Please fill out the feedback, and…