breach-encapsulation-naming

The breachEncapsulationOf naming convention preserves encapsulation by explicitly flagging getters that break domain boundaries, ensuring internal state access is restricted to persistence or serialization and guiding teams to respect Tell Don't Ask principles.

Use explicit getter naming for domain model persistence when ORM frameworks or serialization layers require direct access to internal state, applying the breachEncapsulationOf prefix to signal a deliberate boundary violation rather than standard property access.

Refactor domain model getters to enforce Tell Don't Ask by replacing standard accessor methods with breachEncapsulationOf-prefixed methods, making encapsulation breaks visible during code review and preventing uncontrolled getter usage across the codebase.

Yes, the breachEncapsulationOf naming pattern works across multiple programming languages including Java, Kotlin, Scala, TypeScript, Python, Go, and Rust, providing a standardized accessor pattern for domain entities wherever persistence or serialization is needed.

The best way to prevent invisible encapsulation breaks in domain models is enforcing a clear accessor pattern using the breachEncapsulationOf prefix, which makes state access explicit and discourages uncontrolled getter usage outside of serialization contexts.

A limitation of using explicit getter prefixes for domain entity serialization is that the breachEncapsulationOf pattern requires team-wide discipline during refactoring, as persistence layers must correctly invoke the prefixed accessors without falling back to standard getter methods.