Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Your favorite enterprise IT architecture stories of 2014

9/10

API best practices for developing agile, cloud-ready applications

Source:  Thinkstock

When an enterprise architect is tasked with designing an API, he or she may go down several different paths. Some may gravitate toward using SOAP, while others may choose REST. Although either interface model can be effective, an API best practice would be to consider all options.

In this tip, expert Tom Nolle urges developers to apply API best practices to design applications that are ready for use in the cloud age. For example, Nolle recommends focusing on data elements as self-defining, rather than thinking solely of customer parameters.

Read more here: API best practices for cloud-ready application development

View All Photo Stories

Join the conversation

5 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

What are some of the most valuable API best practices you've learned?
Cancel
Frame-work style coding is one of the best API practices that can be applied.  I think frame-work styling coding is best for storage and reuse. It makes sense to use this style if you are teaching a course amongst younger coders or you just want to develop it for different projects. I think it also makes sense to use value mapping in order to store data. Mobile based projects can be tied to storage.
Cancel
Thanks, tyler59. I am not familiar with frame-work style coding. I will have to take a look into it!
Cancel
I would consider how wide spread sharing the API might be, have a plan for handling authentication and authorization (or in some cases registration and activation), to be able to better handle the many potential users of an API, and I would also early on try to have a good way of publishing the API, promoting coming changes to the API, and have a way to handle maintenance releases in a way that allows 3rd Party Vendors to be able to continue to leverage 'older ways' of doing things, while providing progressively better API features.
Cancel
Thanks for offering some solid advice, Veretax!
Cancel

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide.com

SearchWinDevelopment

DevOpsAgenda

Close