On Mon, Jul 10, 2017 at 1:35 PM, Luke Horton
wrote:
> This is probably not clojure specific, but it’s a problem for which i’ve
> never really found a satisfying in other languages. Maybe clojure has a
> better opinion on the matter?
>
> How does one evolve/change data (entities) in a system over
In Domain Driven Design, the domain model is the part which should be made
to change the least, which is why getting is right is important, and more
design time should go into it (often it receives the least amount of
thought). The whole concept of DDD is based around this axiom, that
changing
Per some recommendations on clojurians #clojure channel:
- namespaced keys and addition over destruction
- generally keep your data as flat as possible
- finicky nested over "organized" data models are magnets for repeated
restructures into a new "better, more organized" structure
On Monday, Ju
This is probably not clojure specific, but it’s a problem for which i’ve
never really found a satisfying in other languages. Maybe clojure has a
better opinion on the matter?
How does one evolve/change data (entities) in a system over time without
also having to change every piece that touches
