I just finished my session at NDC London – for those of you who were there, here’s the code + slidedeck.
For those of you who weren’t, a short description:
REST used to be a buzzword, but these days, it’s a given: we’re all building REST-ful API’s (or want to be building them). Yet there’s a lot to talk about and a lot that can go wrong when building a REST-ful API.
In this session, we’ll dive into best practices concerning URI design/routing, partial updates, filtering, sorting & paging, data shaping, versioning and more. We’ll learn about the standards that have been created to allow some of these requirements, and how you can use them, with one purpose in mind: build a truly evolvable, cross-platform consumable REST-ful API.
In short, you’ll learn about the good, the bad and the ugly concerning REST.
… and in case you want to continue learning, you can always (warning: shameless commercial plug coming up! :)) check my Pluralsight courses on Building and Securing a REST-ful API for Multiple Clients in ASP.NET or OAuth2 and OpenID Connect Strategies for Angular and ASP.NET.