Ash Framework: My Misconceptions | Joseph Koski’s Blog

Ash Framework inverts the typical framework approach by prioritizing domain modeling over persistence concerns—rather than designing databases first and deriving business logic from them, Ash asks developers to model the domain itself and let persistence follow. The framework achieves this through extensive code generation at multiple levels: one-time scaffolds, repeatable generators that evolve with resource definitions, ongoing regeneration that tracks schema changes, and compile-time macros that inject functions declaratively, fundamentally differentiating it from Rails' runtime metaprogramming by leveraging Elixir's compile-time capabilities.

Visit Original Article →