Request and Response Management
Common entities used to manage web requests and responses. These patterns seek to decouple clients from the underlying systems used by the service.
Developers may select zero, one, or more of these patterns when designing a given service.
|Service Controller||How can the correct web service be executed without having to maintain complex parsing and routing logic?|
|Data Transfer Object||How can one simplify manipulation of request and response data and also minimize dependencies between domain layer entities, request structures, and response structures?|
|Request Mapper||How can a service process data from requests that are structurally different yet semantically equivalent?|
|Response Mapper||How can the logic required to construct a response be reused by multiple services?|