2017-09-14 23:07:40 +05:30
|
|
|
---
|
|
|
|
|
layout: pattern
|
|
|
|
|
title: Partial Response
|
|
|
|
|
folder: partial-response
|
|
|
|
|
permalink: /patterns/partial-response/
|
2019-12-13 21:09:28 +02:00
|
|
|
categories: Behavioral
|
2021-05-19 10:49:05 -06:00
|
|
|
language: en
|
2017-09-14 23:07:40 +05:30
|
|
|
tags:
|
2019-12-13 21:09:28 +02:00
|
|
|
- Decoupling
|
2017-09-14 23:07:40 +05:30
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Intent
|
|
|
|
|
Send partial response from server to client on need basis. Client will specify the the fields
|
|
|
|
|
that it need to server, instead of serving all details for resource.
|
|
|
|
|
|
2019-12-07 20:01:13 +02:00
|
|
|
## Class diagram
|
2017-09-14 23:07:40 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
|
Use the Partial Response pattern when
|
|
|
|
|
|
|
|
|
|
* Client need only subset of data from resource.
|
|
|
|
|
* To avoid too much data transfer over wire
|
|
|
|
|
|
|
|
|
|
## Credits
|
|
|
|
|
|
|
|
|
|
* [Common Design Patterns](https://cloud.google.com/apis/design/design_patterns)
|
