Design patterns·Who calls whom, and when
the request became an object with an execute method, so you could put it in a queue, log it and undo it.
Command pattern
Also calledcommand, action object, request as object
Turning an invocation into a first-class object carrying its receiver and arguments, so it can be stored, passed, queued, retried, logged or reversed. That reification is the point — a strategy and a command can be identical in shape, and the difference is that a strategy is how to do something and a command is a particular thing to do. It is the object-level relative of every persisted-request idea, from job queues to event sourcing.