Transitioning to Hypermedia APIs

• Avoid duplication of services
• Quickly develop new applications
• Work with partners

• Requires standards and consistency
• And other challenges

• Base service and resource classes
• Enforce types services return
• Collections vs Single resources

• Support JSON and XML, defaults to JSON
• Provide extensions to return other representations

• GET Collections
• Others Single resources
• DELETE no body

• final classes with out supported status codes
• provides guidance on when to use which code
• provide lots of examles

• Custom Service
• Reads metadata to discover services
• Ensure conform to naming standards and proper casing

http://martinfowler.com/articles/richardsonMaturityModel.html

• Were Level 1.5
• HTTP Verbs were supported but not used correctly
• Only 200's, 404, or 500 were supported

• Baby Steps
• Introduced to support paginations and self links
• Eventually began adding context links
• TODO: Looking for richer linking support for extra metadata, possible support for elasticSearch type queries

• Became more expressive
• Convey more descriptive context so client doesn't need to parse error message for status code.
• Now at Level 3