my-java-rules

Structure Elixir and Phoenix projects using Domain-Driven Design by organizing code around business domains rather than technical layers, keeping domain logic pure with side effects at boundaries, and ensuring each module has a single responsibility. This approach improves maintainability and alignment across teams.

The best way to enforce boundary validation in Phoenix contexts is by validating inputs at boundaries using standard tooling like NimbleOptions. This ensures explicit over implicit design, prioritizing clarity over magic to maintain robust domain boundaries.

Test Phoenix public APIs with Mox and ExMachina by focusing on public API testing rather than internal implementation details. Use Mox for mocking external dependencies, ExMachina for generating test data, and incorporate property-based testing for robust validation.

Use functional core and imperative shell in Elixir architecture when you need to keep domain logic pure with side effects isolated at boundaries. This pattern separates business rules from infrastructure concerns, making systems easier to test and maintain.

Yes, this approach requires typespecs and pattern matching in Elixir to embrace robust control flow and typing. Explicit naming, typespecs, and boundary-driven design are fundamental principles that ensure code clarity and reliability across Phoenix projects.

Start implementing domain boundaries in a Phoenix context by outlining a specific domain boundary and implementing a simple API that delegates to a clean, testable domain action. This establishes the API/implementation separation pattern for scalable architecture.