API as an Ancient Roman Aqueduct

on YouTube ↗34m

" summary

Covers what an API is and why teams need one, using principles for proper API design, maintenance, and techniques to preserve backward compatibility. Discusses practical approaches to evolving APIs without breaking existing clients.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 3:30API as Roman aqueduct
3. 7:02Designing API from scratch
4. 14:50Naming and design rules
5. 18:47API backward compatibility
6. 22:08Yandex Maps API customization
7. 25:18Map styling and competition
8. 27:36API priorities: users vs devs
9. 31:39Fixing API errors
10. 33:25XML vs JSON data

" related talks

• 26mAPI archaeology: guiding the API journeyErik Wilde · Apidays LIVE Paris 2020
• 41mAPI = Some REST and HTTP, Right? RIGHT?!Rustam Mehmandarov · Codemotion Madrid 2026
• 50mAPI GovernmentMarco Antonio Sanz · T3chFest 2017
• 26mAPIs are the new skin of your organisationMarc Burgauer · apidays Paris 2021
• 51mAPI Design in Real Life: What You Don't See in BooksMario Mancuso, Rafael Rocha · QCon São Paulo 2018
• 23m359o of API Design: Things to consider when crafting your APIAriyandi Widarto · apidays LIVE Jakarta 2020
• 01h 01mAPI Design – How to Do It Better (and How Not To)Uwe Friedrichsen · W-JAX 2019
• 49mAdvanced API design: how an awesome API can attract friends...Jonathan Dahl · RubyConf 2011