O'Reilly's Performance Optimizations in a Cloud-Centric World

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/545501

Contents of this Issue


Page 20 of 38

6. Third-Party Components Websites are increasingly dependent on being consumers of data or functionality provided by third-party systems. Client Side Client-side systems will commonly display data from third parties as part of their core content. This can include: • Data from third-party advertising systems (e.g., Google AdWords) • Social media content (e.g., Twitter feeds or Facebook "like" counts) • News feeds provided by RSS feeds • Location mapping and directions (e.g., Google Maps) • Unseen third party calls, such as analytics, affiliate tracking tags, or monitoring tools Server Side Server-side content will often retrieve external data and combine it with your data to create a mashup of multiple data sources. These can include freely available and commercial data sources; for exam‐ ple, combining your branch locations with mapping data to deter‐ mine the nearest branch to the user's location. Performance Risks Dependence on these third-party components can create the follow‐ ing performance risks. Complete failure or inconsistent performance If your system depends on third-party data and that third party becomes unavailable, your system could fail completely. Likewise, poor performance by the third party can have a domino effect on your system's performance. Unexpected results Third parties can sometimes change the data they return or the way their data feeds work, resulting in errors when you make requests or when the requests return unexpected data. 6. Third-Party Components | 11

Articles in this issue

view archives of eBooks - O'Reilly's Performance Optimizations in a Cloud-Centric World