Service Locator violates encapsulation

Service Locator violates encapsulation in statically typed languages because it doesn't clearly communicate preconditions.

Service Locator violates encapsulation Service Locator violates encapsulation by Mark Seemann Service Locator violates encapsulation in statically typed languages because it doesn't clearly communicate preconditions. The horse has been long dead, but some people still want to ride it, so I'll beat it yet again. Over the years, I've made various attempts to explain why Service Locator is an anti-pattern (e.g. that it violates SOLID ), but recently it struck me that most of my arguments have been focused on symptoms without ever addressing the fundamental problem. As an example of discussing sym

saved by

• Tom

related reading

• The Law of Leaky Abstractions – Joel on Softwarejoelonsoftware.com
• The Wrong Abstraction - Sandi Metzsandimetz.com
• Clean Coder Blogblog.cleancoder.com
• SOLID Design Principles Explained- Stackifystackify.com
• Patterns for Defensive Programming in Rust | corrode Rust Consultingcorrode.dev
• SOLID Design Principles Explained: Building Better Software Architecture | DigitalOceandigitalocean.com
• Why (most) High Level Languages are Slow // A Random Walk Through Geek-Spacesebastiansylvan.com
• Reading 4: Specificationsweb.mit.edu
• LEAP 71 | PicoGK.org Blogpicogk.org
• No, dynamic type systems are not inherently more openlexi-lambda.github.io
• Reflecting on deserialization. Why you should explicitly decode your JSON.hashset.dev
• How to write complex softwaregrantslatton.com