Architecture Kata
summary
Designs take raw GPS + Wi‑Fi scans from trucks, batch ftp upload at depot or stream from phones, store raw records in a sharded NoSQL store (Mongo), run a scheduled importer to build a Wi‑Fi→location knowledge base, and expose a scaled query service (REST/JSON or binary for battery savings) that returns coordinates and accuracy. Teams target 500 q/min and 99.9% SLA, separate input and query services for independent scaling, keep raw history for future algorithms, and propose SMS fallback and caching for low‑power clients.
AI-written summary · about
chapters (8)
- 0:00Introduction and setup
- 10:20Problem statement and requirements
- 18:17Team formation and design exercise
- 32:49Team 1 presentation and review
- 44:51Team 2 presentation and review
- 55:26Team 3 presentation and review
- 1:02:26Voting and lessons learned
- 1:12:06Wrap-up and closing remarks
related talks
21mImplementing a Localization-Dependent Application
01h 03mModern Architecture 101 for New Engineers & Forgetful Experts
18mRethinking Apps with Local-First Architecture
16mTransforming farmer’s lives using Android in Kenya
43mOffline-first Architecture - How to survive without the internet?
49mArchitecture assessments
46mDigital scale-up architectural patterns
32mWhat Is the Best Architecture for Android Apps That Integrate Closely with External Devices?