Command design pattern geeksforgeeks

Command pattern is a data driven design pattern and falls under behavioral pattern category . A request is wrapped under an object as command and passed to invoker object.

The main motivation for using the Command pattern is that the executor of the command does not need to know anything at all about what the command is, what context information it needs on or what it does . All of that is encapsulated in the command.

The main difference is , the command does some action over the object . It may change the state of an object. While Strategy decides how to process the object. It encapsulates some business logic.

In command pattern there is a Command object that encapsulates a request by binding together a set of actions on a specific receiver . It does so by exposing just one method execute() that causes some actions to be invoked on the receiver.1 Eyl 2021

The command pattern should be used when: You need a command to have a life span independent of the original request, or if you want to queue, specify and execute requests at different times . You need undo/redo operations. The command’s execution can be stored for reversing its effects.

A Command pattern is an object behavioral pattern that allows us to achieve complete decoupling between the sender and the receiver . (A sender is an object that invokes an operation, and a receiver is an object that receives the request to execute a certain operation.