3 ms·
One thing not mentioned here: discoverability. As there are more and more APIs, more devices, and in general more complexity, computers should be talking to ea
by danpalmer 13y ago
One thing not mentioned here: discoverability.
As there are more and more APIs, more devices, and in general more complexity, computers should be talking to each other and figuring things out between themselves more. Right now almost all APIs require developers to explicitly code the interaction details. If 'RESTful' web services were actually 'RESTful' (i.e. reached level 3 on the Richardson maturity model) then we might be able to do that.
People keep saying that HATEOAS isn't ready for use yet, I'd say the only reason for that is that no one is using it. I would consider a level 3 qualifying web service to be technically far superior to the majority, and I would be more likely to use it.
- kirang1989 13y agoAny good resources to read more about "discoverability" that you'd recommend ?
- danpalmer 13y agoThe original thesis on REST by Roy Fielding is a good start, to understand the real motivation behind creating it. Martin Fowler has a good article on the Richardson Maturity Model, and what each part means: http://martinfowler.com/articles/richardsonMaturityModel.html http://martinfowler.com/articles/richardsonMaturityModel.htm... Finally, for an example of why HATEOAS is a good thing, and why APIs should be at level 3 on the RMM, Jon Moore has a good talk on Hypermedia APIs here: http://vimeo.com/20781278 http://vimeo.com/20781278 As far as I am aware, there are very few companies actually applying these principles. GitHub is doing something close to it in their API, and I have heard that Google uses this sort of system for their APIs extensively on internal projects. In terms of new-web-API-startup like companies, Twilio/Stripe et. al, I have yet to see many take it this far.
- kirang1989 13y agoI see. Thank you for the resources :)