Thanks to all who participated in last week's webinar: "API Trends: What to expect in 2012" with Sam @sramji, Anant @jhingran, and Brian @brianpagano. Here are the video and slides. Thanks for a great interactive session.
Last time, we looked at why you might consider complementing your API with an SDK or code libraries. In the series so far, we've covered a lot of tips and tricks for designing pragmatic RESTful APIs.
You may be asking - How do I follow all these best practice guidelines and still maintain and iterate my APIs? What should I be thinking from an architectural perspective in terms of implementing these best practices?
Add an API virtualization layer ...
So far in the API design series, I've looked at best practices for designing pragmatic RESTful APIs. This time, I'll talk about complementing APIs with code libraries and SDKs. What to do when building a UI requires a lot of domain knowledge?
In this post in the series, let's think about how app developers use that API you're designing and dealing with chatty APIs. Imagine how developers will use your API. When designing your API and resources, try to imagine how developers will use it to say construct a user interface, an iPhone app, or many other apps.
We've covered singular vs. plural nouns to label your resources, tips for search, handling errors, and more. Now lets take a look at what some API requests and responses look like for our dogs API.
I've talked about versioning as one of the most important considerations when designing your pragmatic RESTful API. So it deserves another mention, keeping in mind basic versioning recommendations, such as:
- How many versions should you maintain?
- For how long should you maintain a version?
Wayne Gretzky has this great quote -
A good hockey player plays where the puck is. A great hockey player plays where the puck is going to be.
A few days ago I had a great conversation with a big retailer (and with many other customers since then) about engaging customers on the edge of the enterprise and think it's worth sharing.
Today our systems of record in enterprises are ERP and billing systems. That will continue to be the case but the problem is that all these...