Fallthrough

APIs are built, not born, so how do we go about actually building them? Well, it starts with design. In this episode, Kris and Ian are joined by Jamie Tanna to talk about API design. From creating a theory of your API, through building its foundation, to actively prototyping as you design, the panel discusses what they've learned over the years to design high quality APIs. At the end we have unpopular opinions, but we also have a bonus behind the scenes look at howe we create episodes of this podcast. Make sure to stick around until the end of the episode for that content!

Supporters get access to an extended conversation about API design, where we continue some conversation that were cut short, dig more into how the podcast is made, and you'll get to hear Kris argue against using REST! You can get access by signing up at https://fallthrough.fm/subscribe.

Thanks for tuning in and happy listening!

Notes:

Table of Contents:

Prologue (01:11)
Chapter 1: Designing APIs (02:54)
- You will make mistakes (03:26)
- Inventing things from whole cloth (06:29)
- There is no correct (12:34)
Chapter 2: A Theory of Your API (17:48)
- Creating a foundation (31:26)
- Starting from your database schema (Supporter Only)
Chapter 3: Prior Art (34:13)
Chapter 4: Design Requires Code (41:37)
Chapter 5: The Happy Path (48:19)
Chapter 6: Application Transactions (53:08)
Chapter 7: What Is Forever? (57:06)
Chapter 8: Separate Application & Transfer (01:08:30)
Chapter 9: Stop Doing RESTful Nonsense (Supporter Only)
Chapter 10: Concrete Challenges with Correctness (01:11:59)
Appendix UNPOP: Unpopular Opinions (01:18:44)
- Jamie's Surprise Unpop (01:18:47)
- Jamie's Second Unpop (01:23:55)
Epilogue (01:26:55)