Redfish 1.0 is defined as a standard and a RESTful API for the management of scale-out commodity servers. Although it was created with the current needs of scalable architectures in mind, Redfish can be used for the management or the integration of the older platforms and their tool chains.
REST and hypermedia has a lot of benefits but they significantly complicates building both the client and the server API, thus useful only in some scenarios Jimmy Bogard states in a series of blog posts highlighting what’s needed to get a full hypermedia solution from server to client including choosing a hypermedia-rich media type.
Postman is a popular Chrome application used to test, build, and document web APIs. InfoQ interviewed Abhinav Asthana, the founder and CEO of Postman, about the latest release to give our readers a better understanding of what Postman is, how it was created, why it’s popular with API developers, and what’s new in 3.0.
InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.
Michael Bryzek, co-founder and ex-CTO at Gilt, discussed at QCon New York how ‘dependency hell’ could impact the delivery and maintenance of microservice platforms. Bryzek suggested that dependency hell may be mitigated by making API design ‘first class’, ensuring backward and forward compatibility, providing accurate documentation, and automatically generating client libraries.
Parse has announced its new Schema API, which allows to programmatically manipulate the database schema used by an app, and the Parse API Console, which aims to make it easier to use Parse REST API without writing any code.
At WSO2Con EU 2015, WSO2 has announced API Cloud and App Cloud, two complete solutions for managing APIs and respectively enterprise applications throughout their lifecycle.
API languages are in their infancy and API developers are actively using API Blueprint, RAML, and Swagger. Together, as a community, developers are defining the standards that will be used in the future. InfoQ recently had the opportunity to talk to Jakub Nesetril, creator of the API Blueprint project and CEO of Apiary.
Apigee has opened up API Studio, a free online tool for creating, testing and sharing APIs.
Under the name of Project Oxford, Microsoft has made available a set of RESTful APIs that aim to make it possible for developers to build apps that feature face recognition, speech processing, and other machine learning algorithms. Part of the Azure portfolio, the new APIs are currently in beta and free to use up to 5,000 call per month.
Mashape has open sourced their API Layer called Kong.
InfoQ had the opportunity to interview Uri Sarid, creator of another famous API language, the RAML project. Uri is also CTO of MuleSoft and we appreciate that he was generous with his time to help the community understand RAML’s technology and governance, share his view of the SmartBear acquisition of Swagger, and provide interesting comparison points between RAML, Swagger and API Blueprint.
As outlined in the NPAPI Deprecation Guide, Chrome 42, which was due this month and was recently released to the stable channel, has disabled support for the Netscape Plug-in API. The reason is that NPAPI “has become a leading cause of hangs, crashes, security incidents, and code complexity” and the intent was first announced in 2013.
Twitter recently announced that it has cut-off their firehose data distributor DataSift. This move echoes Twitter's controversial 2012 API changes which restricted the Twitter client ecosystem. There is much speculation as to whether this latest announcement is an attempt to control the tweet analytics space and whether or not this is behaviour fitting of a platform provider.
AnyPresence, one of the leading MBaaS players has launched JustAPIs, a platform for building and deploying RESTful APIs.