1. ASP.NET Web API
  2. Web API Design
  3. REST (Representational State Transfer )
  4. HATEOAS (Hypermedia as the Engine of Application State )
  5. Scaffolding in Web API

ASP.NET Web API

  • Option for web applications
  • Makes it easy to build HTTP-based services
  • Ideal for RESTful APIs
  • Designed to convert SOAP into REST

Web API Design

  • An intentional approach to building APIs
  • A “must have” if your APIs will be consumed by third-party services
  • Attention to details:
    • How consumable is the API (signature, content negotiation)?
    • Does it comply with standards (response codes, etc.)?
    • Is it secure?
    • How do you handle multiple versions?
    • Is it truly RESTful?

REST (Representational State Transfer ) in Web API

Introduction and overview of Representational State Transfer :

  • Client-server
  • Stateless
  • Resource-based (vs. remote procedure call)
  • HTTP methods (GET, POST, PUT, DELETE)
  • Indempotency and side effects
  • It’s a style, not a standard
  • Don’t hate on HATEOAS

HATEOAS (Hypermedia as the Engine of Application State ) in Web API

  • Hypermedia is the key
  • It all starts at a URL
  • Resources are returned
  • Media types and locations are included
  • References based on state

Scaffolding in Web API

Generation of Web API projects out of the box with Visual Studio