Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
API Craft
Home
+ new post
About this group
Join this group
Message from discussion HATEOAS -> Level 3 REST?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Brian Mulloy  
View profile  
 More options Apr 15 2012, 7:59 pm
From: Brian Mulloy <br...@apigee.com>
Date: Sun, 15 Apr 2012 19:59:29 -0400
Local: Sun, Apr 15 2012 7:59 pm
Subject: Re: HATEOAS -> Level 3 REST?
Print | View thread | Show original | Report this message | Find messages by this author

I like the maturity model for REST but I don't like it for web APIs in general because it implies a false sense of linearity toward some API nirvana.

There are other sets of constraints that are just as valuable and relevant and mature to certain problem domains as HATEOAS is to the web client-server model.

For example, many web APIs consumed by an iOS app maintain their own engine of app state and it's a really good and valuable thing -- just ask the  Instagram crew :-) -- just because it will never make sense as HATEOAS doesn't mean the API team is less talented or the design less mature. It just means the client is the engine of app state, CATEOAS.

Sent from my iPhone

On Apr 15, 2012, at 12:25 PM, MattM <matthewmclartys...@gmail.com> wrote:

> I think establishing the maturity model is a great way to approach this.  If the audience gets Levels 1 and 2 quickly, then you don't need to spend a lot of time (no loss).  If they DON'T get it quickly, then clearly they need to hear it and won't be ready for HATEOAS without it.

> Does anyone else on here agree that this maturity model (that was created a few years ago) could use a few more levels, possibly around areas like security, service levels, and other non-functional areas?  Could be an interesting group assignment.

> Thanks, Matt

> On Saturday, 14 April 2012 08:58:13 UTC-7, Matthew Bishop wrote:
> Like many of you, our company struggles with both saying and
> understanding HATEOAS. A few months ago I had to try to explain this
> to a new group of staff members and I tried using "Level 3 REST"
> instead. I pointed to the Richardson Maturity Model at
> http://martinfowler.com/articles/richardsonMaturityModel.html

> It worked. People got what I was talking about much easier because the
> Level 3 was framed in reference to the other Levels.

> I'm no longer using the term HATEOAS but Level 3 from now on. What do
> you think?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google