Domain logic is the unique core of our applications, but it's often entangled with the implementation details of our application: scattered throughout http-handlers, database functions, and UI templates. In the object-oriented world, MVC prescribes a separate place for domain-logic: the model; but as functional-programmers, how should we separate our domain-logic from the rest of our application?

In Clojure, we have some good functional and data-driven solutions for various problems, but domain-logic solutions are home-grown and often not very idiomatic.

In this talk, Rafal examines the problem of domain-modeling in Clojure, reviews existing approaches, and introduces a new library for data-driven domain modeling, that could become a common-ground for the Clojure community to build shared tooling around.