InfoQ Homepage Web API Content on InfoQ
-
Don’t Think like an Engineer When Designing Microservices
When designing microservices and their APIs, you need to think like a designer focusing on the users, Nic Benders claimed in his presentation at the recent Microservices Practitioner Summit. Design the API first, then build your services with an outside-in approach.
-
Visa Launches Visa Developer Suite of APIs
Visa Developer opens the world’s largest retail payment network to the world of developers. The suite of APIs available via this newly launched platform include far more than the expected credit card validation and authorization systems by including APIs for micro-transactions, wish lists, and shopping carts.
-
A Discussion of the Past and Future of Web APIs with Dion Hinchcliffe
Interview with Dion Hichcliffe to get his vision for the direction of Web APIs. Based on a decade of in-depth experience, Dion explains how the history of REST and simple design influenced the ultimate popularity of web APIs over web services. As businesses adopt web APIs more broadly, Dion explains the past and present, and hints at the future of APIs, platforms and networks.
-
Interview with Tony Tam on the Open API Initiative and Latest Swagger News
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.
-
A Pattern for API Backends Serving Frontends
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.
-
Apigee Technologists Explain API Trends, Products, and Standards
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.
-
Daniel Jacobson on Ephemeral APIs and Continuous Innovation at Netflix
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.
-
Dropbox API v2 Launched for Swift, Python, .NET, and Java
Dropbox has announced its API v2, which supports four SDKs: Swift, Python, .NET, and Java, is generally available to developers. According to Dropbox, Dropbox API v2 is “simpler, more consistent, and more comprehensive”. Currently, API v2 does not support JavaScript and Objective-C.
-
The RAML Workgroup Announces RAML 1.0 and API Workbench
The RAML community has announced the release of RAML 1.0, API Workbench and a JavaScript plus a Java RAML parser.
-
Dropbox Deprecates APIs and Prioritizes User Collaboration
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.
-
Interview with Runscope on API Testing and Monitoring
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.
-
Interview with Form.IO: API Creation Using Web Forms
<form.io> is an open source platform that enables front end developers to autonomously build backend APIs using forms to drive their apps. The platform provides a single solution for creating both APIs and user interfaces for consumption by a front end javascript framework. InfoQ spoke with the founders of <form.io> to learn more about the platform capabilities and the future they envision for it.
-
Ionide is a New Atom-based F# IDE Written in F#
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.
-
Interview with Readme.io Founder on the Future of API Documentation
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: A New API for Managing Servers
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.