The Dependency Injection (DI) pattern of software development offers many benefits in the area of separation of concerns. The loose-coupling nature of this pattern allows for truly atomic unit tests and (theoretically) more effective development.
While the DI pattern is well documented in web UI technologies that espouse separation of concerns (such as MVC), the use of this pattern in the less glamorous area of application integration using web services is a little leaner on the volume of documentation. Being that application integration apps such as WCF Services have a tendency to perform some elaborate transportation and transformation logic, having the benefits of the DI pattern greatly improves the effectiveness of the development of these applications.
So, in terms of WCF Services, how exactly do we achieve the DI pattern? Thanks to the lightweight Unity library, we can offer the following DI benefits for a WCF Service:
While the DI pattern is well documented in web UI technologies that espouse separation of concerns (such as MVC), the use of this pattern in the less glamorous area of application integration using web services is a little leaner on the volume of documentation. Being that application integration apps such as WCF Services have a tendency to perform some elaborate transportation and transformation logic, having the benefits of the DI pattern greatly improves the effectiveness of the development of these applications.
So, in terms of WCF Services, how exactly do we achieve the DI pattern? Thanks to the lightweight Unity library, we can offer the following DI benefits for a WCF Service:
- File-less activation of services (no more pesky .svc files to maintain)
- Loosely coupled development
- Rapid and agile development thanks to unit testing
