Strengths and weaknesses of dependency injection
Download as PPTX, PDF2 likes868 views
The document discusses best practices for order processing using various repository patterns, emphasizing dependency management and lifecycle control. It critiques service locator patterns and advises against relying on container-specific dependencies while promoting constructor injection and explicit type registrations. The content also includes methods for handling order operations and suggests strategies for dependency injection and cross-cutting concerns.
More Related Content
Similar to Strengths and weaknesses of dependency injection (20)
![[NetPonto] NoSQL em Windows Azure Table Storage](https://cdn.slidesharecdn.com/ss_thumbnails/nosqltablestorage-140329122027-phpapp02-thumbnail.jpg?width=560&fit=bounds)
More from Dennis Doomen (20)
Strengths and weaknesses of dependency injection
- 1. Dennis Doomen | @ddoomen | Aviva Solutions | The Continuous Improver
- 4. Order Processing IOrderRepository Nhibernate OrderRepository Storage RavenDB OrderRepository Storage Storage In-memory Repository Bookkeeping Diagnostics Decorator Diagnostics Decorator Strategy Selection Allow Test-time dependencies Inject dependencies from different modules Control lifecycle (e.g. per http request, singleton, etc) Inject Cross-cutting Concerns Promote depending on abstractions
- 14. Order Processing IStoreOrders<T> + CreateQuery<T>(); + Add<T>(); + Delete<T>(); NHibernate Repository Order Processing IStoreOrders + GetIncompletedOrders(minValue); + StoreOrder(); + CompleteOrder(); OrderRepository VS
- 16. • Don’t use the Service Locator pattern • Use container only at the root… • …so don’t use the container as a dependency • Constructor injection only • Pass local dependencies to methods • Avoid container-specific dependencies • Use delegates for factories, indexes, etc. • Include registrations in at least one test • Use types explicitly in registrations • Let the container handle the life cycle • Access date & time through delegate • Avoid configuration-based setup (e.g. XML).