So you've built your HTTP API, and now that it's live, you're suddenly dealing with a whole new set of problems. Do you really need to PUT the entire Customer just to change someone's email address? Why does it take you 25 API calls just to render a shopping cart? How do you find the bottlenecks when just drawing a web page requires fifty HTTP requests? What happens when one of your API consumers accidentally tries to GET your entire customer database?
In this talk, we'll look at the problems of running ReSTful APIs in the real world, and the architectural patterns that exist to help us solve those problems. We'll talk about hypermedia - how does it work and why does it matter. We'll look at resource expansion, and how it can reduce your server workload and speed up your client applications. We'll talk about how to implement PATCH properly, how to handle security and authentication for your APIs, and what tools and services exist to help you design, deliver and debug your HTTP APIs.
About Dylan Beattie
Dylan wrote his first web page in 1992 and never looked back. He's the systems architect at Spotlight, the UK's leading casting service for professional actors. Dylan works on distributed systems, ReST APIs and microservices, and the challenges involved in introducing scalable architecture in a company where legacy systems generate most of the revenue.
Dylan a frequent speaker at conferences and user groups, where he's spoken about topics including continuous delivery, Conway's Law, front-end development, OAuth2, federated authentication and ReST. Dylan lives and works in London, and when he's not wrangling software he's into guitars, skiing, diving, beer, Lego, Africa, cats and hats.