Downloaded 82 times
Uploaded byJef Claes
REST and ASP.NET Web API (Milan)
This document discusses REST (REpresentational State Transfer) and ASP.NET Web API. It begins by defining REST as an architectural style for building distributed hypermedia systems and emphasizing that REST in practice relies on HTTP. The document then covers basic REST concepts like resources, identifiers, representations, and verbs. It discusses HATEOAS and how hypermedia links APIs together. Finally, it provides an overview of ASP.NET Web API, describing how it maps to REST concepts and allows building RESTful web services and clients in .NET.
More Related Content
Similar to REST and ASP.NET Web API (Milan)
REST and ASP.NET Web API (Milan)
- 1. REST & ASP.NETWeb API @JefClaes
- 2. Thanks to thesponsors
- 3.
- 4.
- 5.
- 6. REST is NOT... •‘Webservices using JSON’ • A protocol • A design pattern
- 7. REST is.. “An architecturalstyle for building distributed hypermedia systems.”
- 8. In theory... REST isn’t limited to a single message protocol.
- 9. But in practice... It’sall about HTTP.
- 10. So now youwonder.. Haven’t we been successfully building web services using SOAP and HTTP for over 10 years ?
- 11.
- 12. Resources • An entity,item, or just a thing you want to expose. • REST is Resource Oriented.
- 13.
- 14.
- 15.
- 16.
- 17. Identifiers Something that identifiesa resource. ID: 1 URI: http://batman.com/api/batresource/1
- 18. Representations View on aresource’s state at an instant in time. XML: JSON: Other: <BatResource> { • Images <Id>1</Id> "Id":"1", • CSV <Description> "Description":"Bataran • Custom Batarang g", • ... </Description> "Quantity":1 <Quantity>1</Quantity> } </BatResource>
- 19. Verbs Actions on aresource. Create Read Update Delete POST GET PUT DELETE
- 20. Hypermedia HATEOAS: Hypermedia asthe engine of application state Linking your API together { "Id":"1", "Description":"Batarang", “Quantity":1, “Links": { "Rel":"Next", "Href":"http://localhost:8080/api/batresource/2" } }
- 21. HypeRRRRRRRmedia • Relations • Embedded resources • Reference data • Redistribution of effort • Reduction of payload size • Reflow • Restriction of functionality
- 22. Architecture of theWEB ARCHITECTURAL VALUES
- 23. Scalability and performance Yes,text-based, synchronous, request-response can be performant. • Stateless • Caching
- 24. Loose coupling • No transactions • No state • No guarantees • HATEOAS • No specific technology stack
- 25. Consistency and Uniformity Everybodyknows how to use HTTP –Constraints –Well understood semantics
- 26.
- 27. Richardson’s Maturity Model Level 0: POX Level 1: Resources Level 2: HTTP verbs Level 3: Hypermedia
- 28.
- 29. What? .NET HTTP framework (4.0) for building RESTful services.
- 30. When? • HTTP Services(WCF) • AJAX back-ends
- 31.
- 32. Options • WebHost – ASP.NET MVC: Click, click, click • SelfHost
- 33.
- 34. Mapping Web APIto REST concepts
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49. Summary • REST – Concepts – Architectual values – Left overs • ASP.NET Web API – Server – Client
- 50. There is more Slidesand source on http://jefclaes.be Extensibility? • Next session (Raffaele Rialdi) • http://github.com/JefClaes/aspnet-webapi-samples-tunisia
- 51. Please rate thissession Scan the code, go online, rate this session