How to build decentralized serverless html5 applications
summary
Shows how to replace S3 + Lambda with a stack using IPFS, DAT and Ethereum, with concrete demos: adding files to IPFS yields IPFS content-addressed hashes and Merkle trees, HTTP gateways create a bottleneck but the browser companion runs a local node, IPNS provides stable pointers, and DAT syncs large datasets. Describes a prototype that stores photos on IPFS while keeping ownership records in Ethereum via EmbarkJS linking Ethereum smart contracts to IPFS, cites Turkish Wikipedia recovery and left-pad as real failures this fixes.
AI-written summary · about
chapters (10)
- 0:00Introduction and buzzwords
- 10:24Decentralized vs centralized networks
- 12:38Static websites and IPFS basics
- 16:35IPFS demo and content addressing
- 22:47Resilience and censorship resistance
- 27:27IPFS for dynamic content
- 31:56Use cases and open source resilience
- 33:21Ethereum and serverless backends
- 35:55Decentralized app demo
- 36:38Q&A session
related talks
41mLearn how to build decentralized and serverless HTML5 applications...
43mBuilding decentralized and serverless html5 apps (...)
51mDistributed Apps with IPFS
01h 00mIPFS — InterPlanetary File System with Node.js
39mA Universal "Hostless" Substrate for a Post-Serverless Futur
01h 04mKeynote: Towards a more effective, decentralized web
23mIPFS and how to distribute the web
31mDecentralized React states - using IPFS to sync, store, and recover state