This chapter gives you the three decisions that make the rest of Damat easier:
- What belongs inside a reusable module?
- What must the host application decide?
- Which execution primitive fits each kind of work?
A module owns one portable domain capability. The application assembles modules and chooses runtime policy. Jobs, durable events, and pipelines make asynchronous work explicit instead of hiding it in request handlers.
Read these short pages in order: