Skip to main content

Dependency Injection for Common Global Dependencies

The use of singletons can often be replaced by simply adjusting scoping of objects. The vast majority of dependencies fit this pattern, with a few exceptions such as DateTime instances, or logging.

Sometimes you just need these dependencies everywhere. You can find yourself passing these dependencies down into the deep depths of your code base. Such changes are often dangerous, time consuming and undesirable.


For a while the use of some date/time abstraction was my default approach to handling dates and times. This fake clock or calendar instance when combined with DI at the lowest level does actually work. However if we stop and think about the abstraction it is clearly unnecessary in many cases. Unless your domain is dealing with date and times explicitly, you don't really need an abstraction. In other words, other than the system where the code is running when or why would you provide a different implementation?

The approach taken as part of the example within the Dependency Elimination Principle is my current solution to date/times and DI. This is still dependency injection, except the value is provided, not the method of obtaining the value. This is essentially one of the benefits of functional programming.


All systems need some form of logging. Commonly either the standard library or a highly rated logging framework is used. The general advice has been to use the logging component directly, rather than providing your own abstraction. Most frameworks already provide interfaces or base classes that make this easy to achieve.

Even so logging suffers the same issue as date/times when it comes to DI. You often need the logging component everywhere, whether it is simply to pass on to other services.

Logging and DI generally do not go well together. Instead simple use the logging instance directly. A good logging framework would be fast, so any automated tests will not notice the difference. Likewise whether logging is configured or not, this should not cause tests to fail. In summary, not every object has to be provided via dependency injection. Loggers being a prime example.

Due to this directly using a logging instance is the preferred approach. Do not rely on DI. However semantic or structured logging does change this suggestion as the use of a domain explicit interface can provide benefits. Semantic logging will be expanded in a future post.


Date/Time and Logging are the two most common global dependencies. The majority of all other dependencies can and probably should be satisfied by traditional DI where possible. As always each dependency should be validated prior to introduction. It may be possible to either eliminate or replace the component in question.


Popular posts from this blog

Three Steps to Code Quality via TDD

Common complaints and problems that I've both encountered and hear other developers raise when it comes to the practice of Test Driven Development are: Impossible to refactor without all the tests breakingMinor changes require hours of changes to test codeTest setup is huge, slow to write and difficult to understandThe use of test doubles (mocks, stubs and fakes is confusing)Over the next three posts I will demonstrate three easy steps that can resolve the problems above. In turn this will allow developers to gain one of the benefits that TDD promises - the ability to refactor your code mercifully in order to improve code quality.StepsStop Making Everything PublicLimit the Amount of Dependencies you Use A Unit is Not Always a Method or ClassCode quality is a tricky subject and highly subjective, however if you follow the three guidelines above you should have the ability to radically change implementation details and therefore improve code quality when needed.

DRY vs DAMP in Tests

In the previous post I mentioned that duplication in tests is not always bad. Sometimes duplication becomes a problem. Tests can become large or virtually identically excluding a few lines. Changes to these tests can take a while and increase the maintenance overhead. At this point, DRY violations need to be resolved.SolutionsTest HelpersA common solution is to extract common functionality into setup methods or other helper utilities. While this will remove and reduce duplication this can make tests a bit harder to read as the test is now split amongst unrelated components. There is a limit to how useful such extractions can help as each test may need to do something slightly differently.DAMP - Descriptive and Meaningful PhrasesDescriptive and Meaningful Phrases is the alter ego of DRY. DAMP tests often use the builder pattern to construct the System Under Test. This allows calls to be chained in a fluent API style, similar to the Page Object Pattern. Internally the implementation wil…

Coding In the Real World

As a student when confronted with a problem, I would end up coding it and thinking - how do the professionals do this?For some reason I had the impression that once I entered the industry I would find enlightenment. Discovering the one true way to write high quality, professional code.It turns out that code in industry is not too far removed from the code I was writing back when I knew very little.Code in the real world can be:messy or cleanhard or easy to understandsimple or complexeasy or hard to changeor any combination of the aboveVery rarely will you be confronted with a problem that is difficult. Most challenges typically are formed around individuals and processes, rather than day to day coding. Years later I finally have the answer. Code in the real world is not that much different to code we were all writing when we first started out.If I could offer myself some advice back in those early days it would be to follow KISS, YAGNI and DRY religiously. The rest will fall into plac…

Feature Toggles

I'm a fan of regular releasing. My background and experience leads me to release as regularly as possible. There are numerous benefits to regular releases; limited risk, slicker release processes and the ability to change as requirements evolve.The problem with this concept is how can you release when features are not functionally complete?SolutionIf there is still work in progress, one solution to allow frequent releases is to use feature toggles. Feature toggles are simple conditional statements that are either enabled or disabled based on some condition.This simple example shows a feature toggle for an "Edit User" feature. If the boolean condition is false, then we only show the "New User" feature and the "Admin" feature. This boolean value will be provided by various means, usually a configuration file. This means at certain points we can change this value in order to demonstrate the "Edit User" functionality. Our demo environment could …

Reused Abstraction Principle

This is the second part of my series on abstractions.Part 1 - AbstractionsPart 3 - Dependency Elimination PrincipleThe Reused Abstraction Principle is a simple in concept in practice, but oddly rarely followed in typical enterprise development. I myself have been incredibly guilty of this in the past.Most code bases have a 1:1 mapping of interfaces to implementations. Usually this is the sign of TDD or automated testing being applied badly. The majority of these interfaces are wrong. 1:1 mappings between interfaces and implementations is a code smell.Such situations are usually the result of extracting an interface from an implementation, rather than having the client drive behaviour.These interfaces are also often bad abstractions, known as "leaky abstractions". As I've discussed previously, these abstractions tend to offer nothing more than simple indirection.ExampleApply the "rule of three". If there is only ever one implementation, then you don't need …