After the Linux Foundation announced the formation of the Open API Initiative (OAI) in the beginning of November with an impressive list of founding members, API developers had questions about the role OAI would play driving consensus around standards. Tony Tam addressed some of these questions later in November at the API Strategy and Practice Conference in Austin, Texas.
In this interview Fred George explains how the internet of things can exploit microservices and the challenges that the Internet of Things is posing and how to deal with them. InfoQ also asked him for advice for the software industry regarding the usage of microservices for the Internet of Things.
The web experience through a mobile device differs in many ways from a desktop version with its smaller screen, limited data plans and need for fewer requests. A mobile device also requires different data and may provide other interactions, e.g. with a bar code reader. One solution is to have one API backend for each type of client, a Backend For Frontend (BFF), Sam Newman explains in a blog post.
Raphael Simon, senior systems architect at RightScale, has created “goa”, a Go-based HTTP microservice framework that allows the definition of a service API via a Domain-Specific Language (DSL) and the automated code generation of the corresponding “boilerplate” server and client code. InfoQ sat down with Simon and asked questions about the goa microservice framework.
Following the “I love API” conference in San Jose, InfoQ had a chance to speak with Ed Anuff and Marsh Gardiner from Apigee to explain their view on new developments with Swagger and changes to API use in IoT, healthcare, and mobile. They also discuss open source projects like Swagger Editor, potential changes to how API security is handled, and the unrealized ideal of hypermedia.
InfoQ had the opportunity to interview Daniel Jacobson about ephemeral APIs, their link to experience-based APIs and when to consider them. He also explains why generic resource-based API architectures can run into problems at scale and why he doesn’t use an API descriptor language. Finally, he describes the various tools they built to deliver those APIs including Falcor, Scryer or Nicobar.
Support for Dropbox's Datastore and Sync APIs ended last week, leaving developers confused and depending on a new Core API which is still in preview status. Meanwhile recent announcements of collaboration products appear to signal a prioritization away from developers towards a focus on user collaboration.
API developer experience is a relatively novel focus aimed to improve API design so it provides a seamless experience to developers when writing software. It can help increase programmers’ efficience and make it easier for developers to achieve goals on behalf of end users.
Runscope, an API monitoring and testing vendor, announced the general availability of Live Traffic Alerts, a real time API performance monitoring solution for live production traffic for key API transactions. InfoQ used this opportunity to speak to Runscope about their vision and the value their platform brings to its consumers.
Ionide, based on the Atom Editor, is a suite of packages that aim to provide a full-featured, modern, cross-platform, open-source IDE for F# development. InfoQ has talked with Ionide’s creator, Krzysztof Cieślak.
Documentation, one of the great neglected areas of software development, is finally getting some attention, with a number of relatively new tools. For an API documentation can be considered essential. Gregory Koberger is working on a system with the intent of connecting developer documentation more directly to APIs and the API dashboard.
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.