One of the most important elements to consider when designing API response messages is which format you’ll use. Most modern apps prefer JSON and this is what we recommend. Only use XML if there's a strong use case to support it. With that said, let’s focus on how to model your response message, for both a single resource and a collection of resources, by looking at how three large APIs do this.
Our friends at ChicagoRuby - a group of Ruby on Rails enthusiasts in downtown Chicago - kindly shared a recording of a recent talk I did about Backend-as-a-Service (BaaS) technology. Check it out to hear about the BaaS platform as a powerful new class of tool that is fast becoming essential for developers, especially for mobile projects.
In a previous webcast, we established that an SOA is not flexible enough to meet the requirements of today's projects. In this follow-up session, Brian Pagano and Greg Brail talk about what an API initiative that evolves your infrastructure entails - including designing a facade for your services, ensuring services are stateless, handling complex and stateful transactions, and more. Video and slides are here.
In a recent webcast: SOA in the API World - Facades, Transactions, Stateless Services . . . , we talked about what an API initiative to extend SOA with APIs to meet the demands of business in the growing app economy entails - including designing a facade for your services, ensuring services are stateless, handling complex and stateful transactions, and more. There were many great questions posed during our session and we didn't have time to cover all so we've written out the Q&A here.
Our previous discussions about API design, which are covered in Web API Design, centered on URL design and we hinted about versioning, errors, and client considerations. Recently, we also outlined an API modeling strategy that’s easy to use. Now we’ll discuss the security measures that you can use to surround your API.
We did a third edition of our webcast on API design, where we drew upon the discussions and implementations with hundreds of crafters and technologists, which helped shape our API design thinking in the twelve months since the previous edition of RESTful API Design. Grounded in the premise that the design of an API communicates how app developers will use it and that the API is an extension of a brand, one of the first topics we tackled in the webcast was API modeling.
In this recent webcast Ben Whaley and Alan Ho discussed the latest thinking in DevOps and how great DevOps helps tune performance, improve stability, and meet the new operational challenges of battery life, disparate OSs and versions, Apple & Google duopoly, and more presented by mobile apps. Check out the video and slides to learn how to operate your mobile apps so that they successfully engage users and build a 5-star reputation.