Four ways a hand-rolled Ruby facade breaks down as your app grows

A simple Ruby class can serve as a clean facade — for example, wrapping Rails.configuration or a Redis pool under a single App namespace — and it outperforms common alternatives like method_missing or dependency-injection containers on discoverability and testability. However, a developer and author of the Ruby gem 'briefly' argues that the plain-class approach has four specific failure points that emerge as the codebase scales. Unlike method_missing, which hides methods from tab-completion, jump-to-definition, and RSpec verifying doubles, a proper class facade exposes real methods that editors and test tools can inspect. DI containers such as dry-container use string keys rather than methods, sacrificing the same discoverability benefits the plain class provides for free. The article frames these trade-offs as the honest basis for deciding when a lightweight dependency becomes worth adding over a hand-rolled solution.