InfoQ Homepage 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.
-
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.
-
Using Microservices in the Internet of Things
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.
-
Defining, Reviewing and Implementing Service APIs with “goa”, a Go-based Microservice Framework
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.
-
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.
-
What is API Developer Experience and Why It Matters
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.
-
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.
-
Design of a Hypermedia REST API Server and Consuming Client
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.
-
Deploying Scrum and SAFe at Philips Lighting
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.