Can we do without a backend app?
summary
Examines whether a full backend can be avoided by assembling API-first services and cloud-managed building blocks. It discusses using third-party APIs for databases, communication, payment, and authentication plus cloud provider features like step functions and serverless functions to orchestrate a procedural workflow, and applies this as a crash test to build an e-commerce app using only plug-and-play services.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:28Static sites first
- 13:53Modern generators
- 17:05Headless CMS
- 21:16Hydration and dynamic
- 23:01Modern frontend debate
- 24:29Headless e-commerce
- 26:16No-backend tools
- 31:58Managed servers
- 39:02Backend delegation
- 43:22Relevant use cases
- 45:10Conclusion and limits
related talks
36mHow a Serverless Backend Makes a Frontend Developer's Life Easier
36mCloud First Web Apps in Azure
24mServerless powered Low Code
18mAPIs at Scale Through Minimalism in Code and Architecture
04mServerless Architectures: What, why, why not, and where next?
28mFunctional Web Apps: A New Paradigm For Web Development
28mServerless Backend for Frontend on AWS
29mServerless For Startups