Domain Modeling Made Functional

Wrapping Up

In this chapter, we started by looking at some high-level principles of persistence: separating queries from commands, keeping the I/O at the edges, and ensuring that bounded contexts own their own data store. We then dived down into the low-level mechanics of interacting with a relational database.

And that brings us to the end of the third part of this book. We’ve now got all the tools we need to design and create a full implementation of a bounded context: the pure types and functions inside the domain (Chapter 9, ​Implementation: Composing a Pipeline​), the error handling (Chapter 10, ​Implementation: Working with Errors​), the serialization at the edges (Chapter 11, ​Serialization​), and, in this chapter, the database for storing ...