Skip to content
0:00 / 0:00

#domainmodeling#clojure#functionalprogramming

Art of Domain Modeling - Eric Normand - reClojure 2021

London Clojurians

3.9K subscribers • 53 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Eric Normand

Intermediate. Assumes working knowledge.

3.1K views4 years ago1 recommendation

Software designProgramming languagesDomain-driven designFunctional programmingSoftware architecture

Eric Normand explores domain modeling in functional programming, presenting an analytical framework to build and improve software models.

After you've mastered immutable data and higher-order functions, what's next in functional programming? Domain modeling is the next-level skill that few functional programmers learn. But a good domain model can mean the difference between a painful codebase and a joyful one. And it's not just programmer morale that hangs in the balance. A better model can help the business deliver more value. In this talk, you will explore the art of domain modeling. You will learn to see past software design rules of thumb. Instead, you will discover an analytical framework for building and improving software models of a domain. That framework will help you in functional programming or in whatever paradigm or language you are using.

Why it's here

1 person recommends this

What people say. Recommended as a quick and clear introduction to functional domain-driven design.

u/RetroUnlockedin r/rust • Recommends

On “What architecture designs have worked good for you?”

…it is not performant, but my code is written more for accuracy than to squeeze every ms of performance. (Not to trigger someone, and claim you cannot do both.) In my opinion the best way to write an application is to do domain driven design (functional style not oop style). How this works is quite simple, this the quickest introduction I know of link to this video Basically you define the signatures of all your functions. Define the type of all your input and output. Finally you define behavior through tests. Rust is perfect because you can write all of this domain modeling close to the code. It is important to note that you do all this before you even write a single line of implementation. Then d…