Altitude San Francisco 2018: We Own Our Destiny
•
0 recomendaciones•486 vistas
1) CNN adopted GraphQL in 2016 to improve page load speeds by allowing clients to request specific data fields rather than entire documents, reducing response sizes by over 90% in some cases. 2) CNN later developed its own Data API using GraphQL and saw request volumes increase to over 7 million per hour with an 89% cache hit rate. 3) For live storytelling, CNN chose to implement Server-Sent Events which allows for near real-time updates without polling by allowing servers to push messages to clients as new data becomes available.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Altitude San Francisco 2018: We Own Our Destiny
Similar a Altitude San Francisco 2018: We Own Our Destiny (20)
Más de Fastly
Más de Fastly (20)
Último
Último (20)
Altitude San Francisco 2018: We Own Our Destiny
- 1. We Own Our Destiny AD Slato n
- 2. Who is AD Slaton? • Atlanta native • At Turner/CNN since 2011 • I like to tell Dad jokes • Find me @adslaton
- 3. Question? Did you know the first French Fries weren’t actually cooked in France?
- 4. Answer. They were cooked in Greece!
- 5. What are we discussing? • How CNN handles Graphql at the CDN • Why CNN chose Server Sent Events the new live storytelling experience
- 7. CNN + Graphql. • Open sourced by Facebook in 2015 • Promise: Clients request what they want • CNN development in early 2016 • Page speed is top of mind • Weather Data API as proof • Homepage component
- 8. CNN + Graphql. • Weather request • From this: /weather/getForecast/json/30337/ true/USGA0028 • To this: /weather/graphql? query=%7BwsiForecast(zip%3A%2230348% 22%2Ccelsius%3A%22false%22)%7Bcurrent Conditions%7Btemperature%2Cdescription% 2Cicon%7D%2Clocation%7Bcity%2CstateOr Country%7D%7D%7D • Content length: • From this: ~16664 • To this: ~142
- 9. CNN + Graphql. 2016 Election Night + CNN Weather Data API 16M Max Requests/Hr (GETs) ~96% Cache Hit
- 10. CNN + Graphql. • CNN Data API developed in 2017 • More complex queries • Schema Stitching • Problem: URL Character Limit ~2048 • Use POST requests • What about caching POST requests?!
- 11. CNN + Graphql. • Fastly POST caching feature • Default limit (~8K) • What if we can diff the post body? • POST body hash • Pass as request header • Use as part of the cache key • Let’s Party!!!
- 12. CNN + Graphql. CNN Data API (9/6/2018) 7.6M Max Requests/Hr ~89% Cache Hit
- 13. Not bound to URL limits Not bound to POST body cache limits Be smart We Own Our Destiny
- 14. CNN Livestory
- 15. CNN Livestory. • Address the live storytelling experience • Needs to be near real time • Options • Polling • Websockets • Server Sent Events (SSE)
- 16. CNN Livestory. • Solution: SSE • Allow servers to send new data • At any time • reduce http request overhead • Servers push messages to clients • Treated as events
- 17. CNN Livestory. • These features help us to scale: • Request collapsing • Stream miss • data chunks sent as available • Shielding • HTTP/2 • Multiplexing on same connection
- 18. CNN + Livestory. CNN Livestory Notify API (9/6/2018) 3.8M Max Requests/Hr ~98% Cache Hit
- 19. CNN + Livestory. • We purge the cache on surrogate key • We notify clients there changes • Clients get updates
- 20. Not bound to polling intervals Real time updates Be smart We Own Our Destiny
- 21. Own Your Own Destiny • Be Pragmatic • Be Honest • Consider the tool, old and new • Ignore the Naysayers
- 22. “It is not in the stars to hold our destiny but in ourselves.” William Shakespeare