Great single page apps need great backends
summary
Argues that reliable SPAs require disciplined backends: Spring 4, Spring Boot and Spring Security power consistent JSON error responses (limit to 200/500/400/401/403/404 plus a UUID error code), include user and developer messages and validation details, and map runtime exceptions to a single error POJO via @ControllerAdvice. Shows session handling with a custom x-spa-api-login header and auth handlers, uses Guava LoadingCache for shared immutable state, demos an echo/mock service, and cites a real app: ~160 tables, ~100k Java, ~20k JS, two devs to production.
AI-written summary · about
chapters (7)
- 0:00Introduction and scope
- 4:28Defining the architecture
- 11:06Consistent error handling
- 37:37Managing Spring security
- 47:00URL space management
- 51:01Managing shared state
- 58:54Frontend and backend teamwork
related talks
51mSecuring SPAs with Spring
29mSingle Page Apps: What an API Developer Should Know
27mMastering Secure Single Page Apps & APIs
50mThe State of Server Side Java Webapps
28mSingle Page Applications - was it a good idea?
32mBuilding Apps with an API-based Backend
46mFrom Untested Spaghetti to Well-Rested Developers
01h 01mSingle Page Applications without REST API