Creating a RESTful API without losing too much sleep

REST (REpresentational State Transfer) continues to be the dominant way to provide a standard method for data access in a web environment. There are a lot of discussions on what makes a good RESTful API, but examples are sometimes hard to come by. How do you structure your code to enable REST but also ensure that you can update and maintain the code over the long haul?
It this talk I will walk through some of the things that I have learned in implementing a RESTful API. We will discuss some of the following topics:
* Landmines - what are some things not to do when developing your REST stack
* Pure data vs hypermedia (HATEOAS anyone?)
* Layering the stack to enable automated testing at all tiers
* Securing your endpoints
* Testing -- tools to explore and validate your endpoints [181]

Comments

Comments are closed.