More Related Content
Similar to It is time for REST
Similar to It is time for REST (20)
Recently uploaded
Recently uploaded (20)
It is time for REST
- 1. It is time for REST Oleksandr Stefanovskyi 1
- 2. ❏ History ❏ Resource-based ❏ Representations ❏ Six architecture constraints: ❏ Uniform interface ❏ Stateless ❏ Client-server ❏ Cacheable ❏ Layered system ❏ Code on demand Overview 2
- 3. ❏ Why Chaos came ❏ What is SOAP ❏ Why REST At first Chaos came to be 3
- 4. Advantages: ❏ Suitable for use with any transport protocol ❏ Has available to it all the facilities of XML Disadvantages: ❏ The verbosity of the protocol ❏ Slow parsing speed of XML ❏ Lack of a standardized interaction model SOAP 4
- 5. ❏ Performance ❏ Scalability ❏ Simplicity of a uniform Interface ❏ Modifiability of components ❏ Visibility of communication ❏ Reliability REST - REpresentational State Transfer 5
- 6. ❏ Things vs actions ❏ Nouns vs verbs ❏ Identified by URIs ❏ Separate from their representations Resource Based 6
- 7. ❏ How resources get manipulated ❏ Part of the resource state ❏ Typically JSON or XML Representation 7
- 8. Resource: lector (Oleksandr) Service: contact information(GET) Representation example Representation: name, address, twitter JSON or XML format 8
- 9. To create new customer POST http://www.example.com/customers To read a customer with Customer ID# 33245 GET http://www.example.com/customers/33245 Resource Naming Examples 9
- 10. POST http://www.example.com/orders POST http://www.example.com/customers/33245/orders GET http://www.example.com/customers/33245/orders GET http://www.example.com/orders/8769 Resource Naming Examples 10
- 11. ❏ Use identifiers in your URLs ❏ Leverage the hierarchical nature of the URL ❏ Design for your clients, not for your data ❏ Resource names should be nouns ❏ Use plurals in URL segments ❏ Avoid using collection verbiage in URLs ❏ Use lower-case in URL segments ❏ Keep URLs as short as possible Resource Naming 11
- 12. Update customer with ID 12345 ❏ GET api.example.com/services ?op=update_customer&id=12345&format=json ❏ GET http://api.example.com/update_customer/12345 ❏ GET http://api.example.com/customers/12345/update ❏ PUT http://api.example.com/customers/12345/update Resource Naming Anti-Patterns 12
- 13. ❏ Uniform Interface ❏ Stateless ❏ Cacheable ❏ Client-Server ❏ Layered System ❏ Code on Demand (optional) Six constraints 13
- 14. ❏ Resource-Based ❏ Manipulation of Resources Through Representations ❏ Self-descriptive Messages Uniform Interface 14
- 15. ❏ State contained within the request itself ❏ Communicated back to the client via ❏ Headers ❏ Status ❏ Response body Stateless 15
- 16. ❏ The methods GET and HEAD are cacheable. ❏ The following status code are cacheable: 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, and 501. ❏ There is no specific headers in the response, like Cache-Control, that prevents caching. Cacheable 16
- 17. ❏ GET — retrieve a specific resource (by id) or a collection of resources ❏ POST — create a new resource ❏ PUT — replace a specific resource (by id) ❏ PATCH — update or modify the resource (by id) ❏ DELETE — remove a specific resource (by id) HTTP Methods for RESTful Services 17
- 18. ❏ GET — return 200 (OK) ❏ POST — return 201 (CREATED) ❏ PUT — return 200 (OK) ❏ DELETE — return 204 (NO CONTENT) HTTP Response Codes to Indicate Status 18
- 19. 200 (OK) 201 (CREATED) 204 (NO CONTENT) 400 (BAD REQUEST) 403 (FORBIDDEN) 404 (NOT FOUND) 500 (INTERNAL SERVER ERROR) Most common response codes 19
- 20. ❏ Resource based ❏ Representation ❏ Uniform interface ❏ Cacheable ❏ Client-Server Architecture ❏ HTTP methods as verbs So what is REST is? 20