Client and server, 3 meters above the Cloud
summary
Claims and concrete engineering: designs bring distributed-systems patterns to mobile and IoT—publish/subscribe via MQTT, challenge-response authentication for Bluetooth locks, and opportunistic piggybacking to move data when gateways go offline. Implements Sofia access-control system deployed in a Milan co-working, uses Cisco gateways and Microsoft Azure, and confronts cache-coherence, retry/backoff and offline credential problems. Cites the 50 billion devices (2020) projection and shows what actually gets built and why those patterns are chosen.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 1:00Title
- 1:20Design Patterns
- 1:50Frontend vs Backend
- 2:32Realworld Deployment
- 2:49Client and server
- 4:32Serviceoriented architecture
- 5:20Microservices
- 6:21Big bowl of mud
- 6:55Why should I bother
- 7:23Internet of Things
- 10:10Business Case
- 11:37Publishsubscribe
- 12:49Bluetooth door
- 14:40Smart lock
- 15:16Offline access
- 15:47Fog Computing
- 16:51Mobile Application
- 17:13Local Gateway
- 18:09Local Gateway offline
- 18:24Local Gateway opportunistic networking
- 20:37use case
- 21:15human characteristics
- 22:05coworking space
- 22:30cache coherence
- 23:37no man is an island
- 24:20disconnected systems
- 25:27synchronous systems
- 25:55Sofia
- 27:17Conclusion
- 28:40No software is an island
- 28:58Stop fighting clientside
- 29:08The worst enemy
- 29:25Matteo Ferroni
related talks
53mPowering 100+ million daily users
25mTaming Client-Server Communication
11mExplaining distributed systems like I'm five
42mPowering 100+ million daily users
40mIoT & Microservices
25mScaling IoT in Practise: From PoCs to Deployment
23mDesigning Robust and Scalable Distributed Applications
39mArchitectural design patterns applied to Distributed Systems