In the presentation from Gluecon 2014, Rob Zazueta - Director, Platform Strategy at Mashery, an Intel Company - introduces his API design framework intended to help developers implementing an API cut through the RESTful debates to get to what worksbest. For more information, please visit http://www.narwhl.com
Thank you for listening to me yammer for the next 30 minutes.
I love the API community. There are incredibly smart and passionate people who are eager to connect us to the future. I have a great deal of respect for all of them and their ideas and I love jumping into the fray on the API Craft group, at conferences like RESTfest and, of course, right here at Gluecon.
I can not stand peoplewho identify problems without suggesting solutions. I tend to believe you become part of the problem at that point.
Don’t let your API’s design surprise your developer customers; surprise them, instead, with the cool things you can do with it.
This is perhaps the most important point. APIs can not live in the abstract and expect to survive – they need to get out there and be used. NARWHL is intended for teams who need to get past the debate and build an API today.
No talk about RESTful APIs can be legally delivered without mentioning both Roy Fielding’s 2000 thesis and the Richardson Maturity Model. IF you leave it out, expect to get a ticket in the mail.
NARWHL starts where the RMM ends. It is by default intended to be RMM Level 3 compliant, but to add some additional structure based on best practices that are already in the wild and that are recommended.
I’m not talking about anything revolutionary here – this should look familiar to you. And that’s the point.
Taming the RESTed NARWHL: Striking the Balance Between Usability and Zealotry in REST.