Backend less Development revisited

on YouTube ↗44m

" summary

Argues that frontend teams can work totally independently during development by fully mocking REST APIs, claiming some projects finish ~90% of UI work before backend sync and citing a portal bank UI used in over 120 Scandinavian banks. Shows three mocking approaches: server-side contract (Swagger/API Blueprint/RAML) generating mocks, browser-layer stubs with sinon.js or framework intercepts in Angular.js, and dynamic data from JSON Schema plus bundling (webpack/Browserify) for intelligent CRUD, timeouts and E2E tests.

AI-written summary · about

" chapters (14)

1. 0:00Introduction and speaker background
2. 1:12Single Page Application approach
3. 3:01Problems with traditional web apps
4. 5:59Tight coupling between frontend and backend
5. 11:36What is backend-less development
6. 14:28Technical perspective of backend-less
7. 17:18Why backend-less development matters
8. 20:17Mocking API layers
9. 23:31JSON schema for mock data
10. 28:48Server API endpoint mocking
11. 32:20Mocking browser API
12. 36:03Mocking framework layer
13. 38:53Automating mocks with build tools
14. 43:15Summary and key takeaways

" related talks

• 40mFRONTEND CHOICESAlex Coles · wroc_love.rb 2014
• 38mEmbrace the frontend revolutionÁlvaro Sánchez-Mariscal · Codemotion Roma 2014
• 01h 29mClient-Side UI SmackdownCraig Walls · SpringOne2GX 2012
• 25mStop mocking - develop frontends with real K8s setupsRobert Stein · Conf42 Cloud Native 2022
• 46mMicro Frontend: the microservice puzzle extended to frontendaudrey neveu · Voxxed Days Microservices 2019
• 26mBackend For Frontend: Building APIs w. end user in mindOmkar Pimple, Jordan Soklevsky · apidays Barcelona 2019
• 44mMicro Frontend: the microservice puzzle extended to frontendaudrey neveu · Jfokus 2019
• 38mThe Front-End FutureFrancis Hwang · GoRuCo 2012