tl;dr Patterns, 20 Years Later: Command ...
Some questions arise out of this:
Command tends to lead to several consequences:
A couple of different takes on the Command include:
- Unit of Work: Frequently, particularly in data-persistence systems, we have a desire to put explicit "boundaries" around several engagements to the database. Were these entirely database-specific, they might be bundled into a transaction, but to open and hold a transaction from a middleware (or client-side) component is undesirable. Thus, we "bundle up" the work to be done into a single conceptual entity, referred to as a Unit of Work.
Last updated: 25 February 2022