๐ญ. ๐๐น๐ถ๐ฒ๐ป๐-๐ฆ๐ฒ๐ฟ๐๐ฒ๐ฟ: Separation of concerns is the principle behind the client-server constraints. By separating the user interface concerns from the data storage concerns, we improve the portability of the user interface across multiple platforms and improve scalability by simplifying the server components.
๐ฎ. ๐ฆ๐๐ฎ๐๐ฒ๐น๐ฒ๐๐: communication must be stateless, as in the client-stateless-server (CSS) style. Each request from the client to the server must contain all of the information necessary to understand the request. Session state is therefore kept entirely on the client.
๐ฏ. ๐๐ฎ๐ฐ๐ต๐ฒ๐ฎ๐ฏ๐น๐ฒ: To improve network efficiency, we add cache constraints to form the client-cache-stateless-server style. Cache constraints require that the data respond to a request with the implicit or explicit label as cacheable or non-cacheable. If a response is cacheable, then a client cache is given the right to reuse that response data for later, equivalent requests.
๐ฐ. ๐๐ฎ๐๐ฒ๐ฟ๐ฒ๐ฑ ๐ฆ๐๐๐๐ฒ๐บ: A client cannot ordinarily tell whether it is connected directly to the end server or an intermediary along the way. Intermediary servers may improve system scalability by enabling load-balancing and by providing shared caches. Layers may also enforce security policies.
๐ฑ. ๐๐ผ๐ฑ๐ฒ-๐ผ๐ป-๐๐ฒ๐บ๐ฎ๐ป๐ฑ: REST allows client functionality to extend by downloading and executing code in the form of applets or scripts. Simplifies clients by reducing the number of features required to be pre-implemented. It allows features to download after deployment improves system extensibility.
๐ฒ. ๐จ๐ป๐ถ๐ณ๐ผ๐ฟ๐บ ๐๐ป๐๐ฒ๐ฟ๐ณ๐ฎ๐ฐ๐ฒ: By applying the software engineering principle of generality to the component interface, the overall system architecture becomes simplified, and the visibility of interactions is improved.
Comments