Mobile: Past, Present, Future - Tech Choices and Architecture Impact
summary
LinkedIn moves from Rails to Node then to Tornado/Play, replaces resource APIs with screen-based JSON and server-controlled sorting, and adds Kafka and push; HTML5 shows a 3–5% crash rate so the apps go native and grow to five apps and ~65 engineers serving ~38% mobile traffic. Tests change to route tests 95% coverage using VCR playback for fast deterministic runs, feature flags on trunk enable a monthly train model, and realtime metrics plus auto rollback EKG let server releases happen 3–4 times daily.
AI-written summary · about
chapters (9)
- 0:00Introduction and philosophy
- 3:23App design and architecture
- 5:23Initial mobile state 2011
- 9:19Transitioning to node.js
- 12:13Scaling development
- 20:00Trunk based development
- 28:28Push and real-time metrics
- 33:43Native apps and microservices
- 38:39Future of mobile
related talks
39mDoes The Browser Have A Future
23mClient/Server Architecture: Past, Present, & Future
01h 00mMobile App Architecture: How to Conquer the Giant!
38mThe Front-End Future
38mEmbrace the frontend revolution
21mTwo Mobile Transformers
55mPreparing for Rapid Growth - Tips for Enabling Your App and Team to Grow
42mChallenges for Developers of Building Large Web Applications