CDN Locks: A way to ensure data integrity in the CDN
summary
A simple API-backed lock object (username, CDN name, message, lock type, timestamp) is implemented in Traffic Portal/Traffic Ops and ships in ATC 6.0 to prevent concurrent snapshot/queue races. It supports soft/shared locks where many editors can change content but only the lock owner can snap/queue, and hard/exclusive locks that block others from editing or snapping. Admins can clear stuck locks, one lock per CDN is enforced, and demos show it working.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:59Why CDN Locks
- 4:54CDN Locks API
- 6:47How it works
- 7:41CDN Object
- 8:28Shared Logs
- 10:53Get CDN Log
- 12:19Delete CDN Log
- 13:22CDN Locks Validation
- 14:34CDN Locks Demo
- 15:35Soft Lock Demo
- 23:54Future Work
- 24:57Questions
- 25:27Conclusion
related talks
33mCDN — The Technology Taking Games to the Next Level
29mSex, Lies & Videotapes: The Truth Behind Your CDN Logs
23mMastering the CDN Present & Future
15mTimelock Drive: Isolated Time-Based Defense for Storage Systems
14mPreAcher: Secure and Practical Password Pre-Authentication by Content Delivery Networks
16mCDN Challenges of HTTP-based Low Latency Live Streaming Delivery
53mCDNs 101: An Introduction to Content Delivery Networks
32mWhat is a CDN & why Developers should Care about using one
