Explain differences between the service container concept vs service locator (anti)pattern vs (usually property-based) dependency injection

[mrts]

Point: service container is an IoC mechanism that can be used well or not well.

Mark Seemann:

A DI container encapsulated in a Composition Root is not a Service Locator - it's an infrastructure component.

It becomes a Service Locator if used incorrectly: when application code (as opposed to infrastructure code) actively queries a service in order to be provided with required dependencies, then it has become a Service Locator.

When a container is used according to the Register Resolve Release pattern from within a Composition Root it's all good.

References:

• http://blog.ploeh.dk/2011/08/25/ServiceLocatorrolesvs.mechanics/
• http://amy.palamounta.in/2012/10/26/on-service-location/
• http://blog.ploeh.dk/2014/06/10/pure-di/
• http://adamcod.es/2013/11/25/service-locator-vs-dependency-injection-container.html