Single Page Apps: What an API Developer Should Know

on YouTube ↗29m

" summary

Eight months leading a front-end team building an Angular client uncovers concrete tradeoffs: deploy SPA bundles statically (S3) while the API must enforce real-time authorization, handle state sync vs client-side Redux/RxJS stores, and support XSRF protection. An edge API can aggregate calls and hold credentials but can be abused. Server-side rendering (React/Vue) helps SEO not security. Favor additive-only versioning to avoid simultaneous client/back-end upgrades and expect polling or WebSockets for live updates.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:08Why API developers should learn SPAs
3. 3:14SPA architecture overview
4. 5:31SPAs static deployments and routing
5. 7:25Security challenges in SPAs
6. 12:22State management in APIs
7. 17:31SPA architecture for APIs
8. 20:00Edge APIs for SPA integration
9. 22:17Guiding principles for API teams
10. 24:31Breaking development silos
11. 26:58Conclusion

" related talks

• 10mUniversal Apps: Architecture for the Modern WebElyse Kolker Gordon · The Lead Developer New York 2018
• 28mSingle Page Applications - was it a good idea?Mateusz Ostafil · 4Developers 2022 Online
• 01h 07mGreat single page apps need great backendsAdib Saikali · SpringOne2GX 2014
• 40mFRONTEND CHOICESAlex Coles · wroc_love.rb 2014
• 13mHow to Survive the Single Page App-ocalypseJim Newbery · The Lead Developer London 2018
• 48mSecurity Risk: Single-Page Applications.Andreas Falk · Devoxx Ukraine 2022: Secure our Future
• 24mBuilding Realtime Singlepage AppsHenrik Joreteg · NodeConf 2011
• 31mDecoupled, Not Disconnected: State and Sync in Micro-FrontendsAmira Shawky · reactjsday 2025