What is Future Friendly?
summary
Argues for building decoupled services instead of monoliths: use service oriented architecture with JSON REST APIs (one API per feature), prefer Node or similar for lightweight endpoints, and keep UI out of API responses — use middleware to render HTML only for browsers. Cites concrete numbers: 60/40 apps versus web usage now and tablet shipments exceeding 50% of PC shipments. Warns about non‑browser endpoints — smart TVs, in‑store digital signage dropping to ~$1k, Pebble and Firefox OS — design client‑agnostic services.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:14The past 13 years
- 3:50The desktop web
- 5:48The mobile web
- 8:24Web vs native
- 9:46Actiondriven computing
- 10:28Casual computing
- 11:55Tablet TV engagement
- 14:34Smart TVs
- 17:07Smart Appliances
- 17:52Pebble
- 18:47ARM
- 21:32ServiceOriented Architecture
- 22:58Resting
- 23:28API
- 25:39Services
- 27:32Shipping the UI
- 29:07PhoneGap
- 29:26Desktop Web
- 31:00Conclusion
related talks
34mArchitektury Aplikacji: The last mile of microservices
41mMigrating from Monolithic to Future-Proof MFs
50mMicroservices, APIs, and the Autonomous Web
55mGive it a REST - Tips for designing and consuming public API's
39mPatterns for Micro Frontends
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
48mIT Architecture : All your micro-services are wrong PERIOD!
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future