my-java-rules

What problem does it solve?

This collection codifies Elixir and Phoenix best practices such as Domain-Driven Design, explicit boundaries, and robust testing to improve maintainability and alignment across teams.

Core Features & Use Cases

• Domain-Driven Design: organize code around business domains rather than technical layers
• Functional Core, Imperative Shell: keep domain logic pure with side effects at boundaries
• Explicit Over Implicit: prioritize clarity over magic
• Composition Over Inheritance: build systems from small, focused components
• Single Responsibility: each module and function should do one thing well
• API/Implementation Separation: public API delegates to implementation modules
• Boundary Enforcement: validate inputs at boundaries using tools like NimbleOptions
• Pattern Matching, Railway-Oriented Programming, Typespecs: embrace robust control flow and typing
• Testing Strategies: test public APIs, use Mox, ExMachina, and property-based testing
• Performance and Security: best practices for performance and security in Phoenix apps
• Documentation and Quality: doc for public functions, consistent formatting, static analysis

Quick Start

Start by outlining a domain boundary in a Phoenix context and implement a simple API that delegates to a clean, testable domain action.