Downloaded 135 times
![Without conventions
• Attributes [HttpGet]
• [NonAction]](https://image.slidesharecdn.com/euricom-120912132401-phpapp02/85/REST-and-ASP-NET-Web-API-Tunisia-33-320.jpg)
![Without conventions
• Attributes [HttpGet]
• [NonAction]](https://image.slidesharecdn.com/euricom-120912132401-phpapp02/75/REST-and-ASP-NET-Web-API-Tunisia-33-2048.jpg)
Uploaded byJef Claes
REST and ASP.NET Web API (Tunisia)
REST is an architectural style for building distributed hypermedia systems based on HTTP. The core concepts of REST include resources identified by URIs, representations of those resources exchanged via standard HTTP methods like GET, PUT, POST, and DELETE. Effective REST APIs follow architectural values like performance, scalability, loose coupling, and consistency by making resources and relationships between them accessible over HTTP. ASP.NET Web API is a framework for building RESTful services on .NET. It allows creating HTTP-based services using controllers and attributes, supports content negotiation for XML and JSON, and includes features for error handling, message handlers, dependency injection, and testing.
More Related Content
Similar to REST and ASP.NET Web API (Tunisia)
REST and ASP.NET Web API (Tunisia)
- 1. REST & ASP.NET WebAPI By @JefClaes
- 2.
- 3.
- 4. REST is NOT... •„Webservices using JSON‟ • A protocol • A design pattern
- 5. REST is... “An architecturalstyle for building distributed hypermedia systems.”
- 6. In theory... REST isn‟t limited to a single message protocol.
- 7. But in practice... It‟sall about HTTP.
- 8. So now youwonder.. Haven‟t we been successfully building web services using SOAP and HTTP for over 10 years ?
- 9.
- 10. Resources • An entity,item, or just a thing you want to expose. • REST is Resource Oriented. A bank
- 11. Identifiers Something that identifiesa resource. BIC (= Bank Identifier Code): KREDBEBB URI: http://myapi.com/bank/KREDBEBB
- 12. Representations View on aresource‟s state at an instant in time. XML: JSON: Other: <Bank> { • Images <BIC>KREDBEBB</BIC> "BIC":"123“, • CSV <Name>KBC</Name> “Name”:”KBC” • Custom </Bank> } • ...
- 13. Verbs Actions on aresource. Read, Update, Delete, Add GET, PUT, DELETE, POST
- 14. Hypermedia HATEOAS: Hypermedia asthe engine of application state Linking your API together
- 15. Architecture of theWEB ARCHITECTURAL VALUES
- 16. Scalability and performance Yes,text-based, synchronous, request-response can be performant. • Stateless • Caching
- 17. Loose coupling • No transactions • No state • No guarantees • HATEOAS • No specific technology stack
- 18. Consistency and Uniformity Everybodyknows how to use HTTP – Constraints – Well understood semantics
- 19.
- 20. Richardson‟s Maturity Model Level 0: POX Level 1: Resources Level 2: HTTP verbs Level 3: Hypermedia
- 21.
- 22.
- 23. What? .NET(4.0) HTTP framework for building RESTful services.
- 24. When? • HTTP Services(WCF) • AJAX back-ends
- 25.
- 26. Options • ASP.NET MVC – Click, click, click • SelfHost
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33. Without conventions • Attributes[HttpGet] • [NonAction]
- 34.
- 35.
- 36.
- 37.
- 38. Default behaviour & IncludeErrorDetailPolicy • By default 500 Internal Server Error
- 39.
- 40.
- 41.
- 42. XML/JSON Supported out ofthe box: • text/xml • application/json (NewtonSoft)
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55. Summary • REST – Concepts – Architectual values – Left overs • ASP.NET Web API – Server/client – Exception handling – Content negotiation – Message handlers – IoC – Testing
- 56.
Editor's Notes
- #11 Batbelt?