- Learning AWS（Second Edition）
- Aurobindo Sarkar Amit Shah
- 447字
- 2021-06-30 18:52:55
Designing for performance
When an application is deployed to the cloud, latency can become a big issue. There is sufficient evidence that shows that latency leads to loss in business. It can also severely impact user adoption.
You will need to attack the latency issue through approaches that can improve the user experience by reducing the perceived and real latency. For example, some of the techniques you can use include rightsizing your infrastructure, using caching and placing your application and data closer to your end users.
Perceived latency can be reduced by pre-fetching data that is likely to be used by the application, or caching frequently used pages/data. Additionally, you can design your pages in a manner that after they are loaded, the downloaded page doesn’t need to traverse the network for most of the subsequent navigation. You can also use AJAX, or similar technology to reduce perceived latency of web pages loading.
Ensure that the data required by your processing components are located as close to each other as possible. Use caching and edge locations to distribute static data as close to your end users as possible. Performance oriented applications use in-memory application caches to improve scalability and performance by caching frequently accessed data. On the cloud, it is easy to create highly available caches and automatically scale them by using the appropriate caching service.
Most cloud providers maintain a distributed set of servers in multiple data centers around the globe. These servers are used to make it easy to use Content Delivery Network (CDN) to serve content to end users from locations closest to them. This service is made available to you by the cloud service provider through an easy-to-use web service interface. The distributed content could be HTML, CSS, PHP, or image files in regular web applications. CDNs can also be used for rich media and content sites with live streaming video.
The content is distributed to various edge locations, and is served to end users from points closest to them. This reduces latency while simultaneously improving the performance of your web application/site, significantly.
The following figure shows how a typical web application hosted on the cloud can leverage the CDN service to place content closer to the end user. When an end user requests content using the domain name, the CDN service determines the best edge location to serve that content. If the edge location does not have a copy of the content requested, then the CDN service pulls a copy from the origin server (for example, the web servers in Zone 1). The content is also cached at the edge location to service any future requests for the same content:
