Pragmatic APIs 101

Abstract

Over the last five years, I have studied REST and HTTP APIs a lot. Nowadays, everyone claims to have a REST API, yet the REST architecture is complex and not really practicable in real life. In this talk, we will see that it does not matter to be 100% REST-compliant, and above all, how to build an API in a pragmatic manner.

About the slides

This slide deck has been written with Monod, then exported as a Markdown file (monod.md) using Cmd + S. I created a Reveal.js template made of HTML and CSS (using the same CSS as in Monod), and a tool to fix a few things in the markdown exported by Monod (bin/fix script). The idea of this slide deck is to have a backup, in case the Internet goes wrong, my laptop burns, or any other disaster.

Here is my workflow:

1. I write slides in Monod
2. I export the Markdown into this repository
3. I run bin/fix monod.md
4. I commit both monod.md and slides.md (generated by bin/fix)
5. I profit!