Use server driven content negotiation, but enhance the response with links to alternate versions and formats of the representation, thus letting the client choose which URIs to follow due to its needs Howard Dierking recently wrote when comparing his newly gained experiences working with designing the next major revision of the NuGet API, V3, with his thoughts almost a year ago.
Recently, Tom Dale, one of the creators of ember.js, wrote an article that re-kindled a brewing debate on the need for progressive enhancement. This is a quick look at the different views on the debate.
Firebase is out of beta with pricing plans and SLAs. This article contains details on Firebase and an interview with Andrew Lee, CTO.
Recently Steve Jones from CapGemini commented on some text in a Nokia API project on github which indicated that designing and documenting APIs for REST based services was no longer required and that HATEOAS was sufficient. Given Steve's previous comments on IT valuing technology over thought, this was something he needed to call out as bad practice.
OAuth.io is an API and a service interfacing with more than 80 OAuth providers. This article contains an interview with Mehdi Medjaoui, Co-founder of OAuth.io, providing details on security, licensing and future developments.
"Don't version unless you absolutely must, and it is rare that you absolutely must" says Mike Amundsen in a series of API design workshops he held recently. Amundsen describes the "USE" paradigm for API design focussing on usability, scalability and evolvability. He describes the three most common styles of API implementation and how they compare to these principles.
Node.js has built a user-base and reputation for fast and scalable back-end systems. In a recent edition of the Nodeup podcast, four engineers share their experiences developing APIs using the platform. The conversation covers a range of key concerns including API design, security, testing, documentation, schemas and streaming. But advertising your API as RESTful may not be a good idea.
When JAX-RS 1.0 was first unveiled back in 2008 it became one of the first POJO/Annoation based frameworks for creating robust web-based applications. Now five years later Java EE 7 has been released and it includes the latest JAX-RS incarnation, version 2.0. InfoQ takes a look at the new features.
In the beginning of MBaaS, there was StackMob. Since then the mobile ecosystem has become flooded with competitors in this new approach to app dynamics. InfoQ takes a closer look at the Mobile Backend as a Service (MBaaS) provider StackMob and its privacy practices.
Final version of the RESTful Web Services Framework Jersey 2.0 was recently released. New features includes a Client API, Hypermedia support, Filters and interceptors, and support for asynchronous Clients and Services. Jersey 2.0 is a reference implementation of the JAX-RS 2.0 API Specification, (JSR 339), released late May.
The latest WSO2 API Manager adds native multi-tenancy, automatic generation of API documentation, and SAML-based SSO, running both on servers or in the cloud.
The fourth version of OData, the Microsoft-backed standard for querying data using REST conventions, has been accepted by the OASIS committee. The public review period will run thru June 2 and Microsoft expects OASIS to adopt the standard later this year.
A recent posting on a REST Architects list has prompted Ganesh Prasad to outline some problems that he sees with REST (over HTTP) in terms of more dynamic peer-to-peer environments and how they could be addressed. He suggests some lessons could be learned from Web Services and mentions an Internet Draft specification which he has been working on.