Presentation on REST principles and patterns held at Region Västra Götaland

2. Niklas Gustavsson [email_address] http://protocol7.com http://twitter.com/protocol7

3. REST

4. REST?

5. HTTP 1.1

6. Some HTTP history http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm

7. Some HTTP history

8. HTTP used right

9. Constraints

10. Constraints Everything is a resource

11. Constraints Every resource has an identifier (URL) http://example.com/reports/niklas

12. Constraints Transfer representations Defined by content-types

13. Constraints All resources expose a uniform interface GET, POST, PUT, DELETE

14. Constraints Hypermedia as the engine of application state

15. http://gowalla.com/api/explorer

16. Constraints Client-server, Stateless, Cacheable, Layered

17. Why?

18. Why? It's easy! Well, it's not

19. Why? It's what others use

20. Why? The web has been successful, copy!

21. Why? Interoperability on the right level

22. Patterns

23. Collection resource http://example.com/contacts

24. GET to retrieve links to all items GET http://example.com/contacts HTTP/1.1 200 OK { [ {“url” : “/contacts/123”}, {“url” : “/contacts/124”}, ]}

25. GET to retrieve a specific item GET http://example.com/contacts/123 HTTP/1.1 200 OK { “name” : “Kalle Anka” }

26. POST to create new POST http://example.com/contacts { “name” : “Niklas Gustavsson” } HTTP/1.1 201 Created Location: http://example.com/contacts/456

27. PUT to update PUT http://example.com/contacts/123 { “name” : “Niklas Anka” } HTTP/1.1 200 OK

28. DELETE to delete DELETE http://example.com/contacts/123 HTTP/1.1 204 No content

29. Advanced stuff

30. Link relations http://www.infoq.com/articles/webber-rest-workflow

31. AtomPub

32. Reliability

33. Async

34. Frameworks!

35. Want more?

36. Demo http://github.com/protocol7/rest-demo

37. Questions?