This document discusses the unit of work design pattern in Microsoft Dynamics AX. It introduces unit of work as a way to perform CRUD operations sequentially as a single transaction. This improves performance over individual database hits and ensures referential integrity. Advantages include not needing to hold parent record IDs, ability to insert data in a single trip, and better performance. A demo compares inserting many records via individual inserts versus using a unit of work, showing the latter is on average 3 times faster.