BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage API Content on InfoQ

  • Google Makes Public Their API Design Guide

    Google has made public an API Design Guide for creating HTTP or RPC APIs. These design principles are recommended especially to developers creating gRPC APIs connecting to Google Cloud Endpoints.

  • Google Cloud Endpoints is Now Generally Available

    After three months in beta, Google has announced the general availability of its Open API-based Cloud Endpoints (GCE) API management system, which aims to make it possible to build efficient, ready-to-scale API platforms, says Google.

  • Microsoft Adds Team and LUIS Support for Flow

    Microsoft has recently announced changes to its cloud workflow service, Flow, to enable teams to contribute and manage flows centrally. This new sharing capability is also available to SaaS and custom API Connectors. In addition to these collaboration features, Microsoft has also announced support for Gmail connectivity and integration with additional Microsoft Cognitive Services APIs.

  • The OpenAPI Spec, Based on Swagger, Reaches 3.0

    The Open API Initiative has announced the preview of the OpenAPI 3.0 with an Implementer Draft scheduled for the end of February.

  • Amazon Adds Finer Granularity of Control to Their Voice Recognition API

    Amazon’s Alexa Voice Service API, the NLP (natural language processing) API that powers Amazon Echo, has a new update that allows for developers to use Alexa to turn any device into a “smart” device through the use of the API’s voice recognition features.

  • Technologies for the Future of Software Engineering

    The Cloud, infrastructure as code, federated architectures with APIs, and anti-fragile systems: these are technologies for developing software systems that are rapidly coming into focus, claimed Mary Poppendieck. Systems are moving towards the cloud, and APIs are replacing central shared databases and enable the internet of things. We need to develop anti-fragile systems which embrace failure.

  • Google Releases .Net APIs for Google Cloud

    Google recently announced .Net support for Google Cloud APIs. This includes C# bindings and PowerShell cmdlets. A Visual Studio extension is also available, allowing to browse Google Cloud resources and to deploy Asp.Net applications on Google Compute Engine.

  • GitHub Adopts New GraphQL API

    GitHub recently introduced at their Github Universe conference the alpha release of their new API, written in Facebook’s GraphQL (a query language that allows for self-service API contracts). GitHub writes in its engineering blog that its main reason for switching API paradigms is lack of scalability with their existing RESTful contracts.

  • Google to Aquire API Management Company Apigee

    Google is acquiring API management company Apigee for $635 million.

  • Netflix Attempts to Reconcile Large Scale APIs with Developer Autonomy

    Katharina Probst and Justin Becker, engineering managers at Netflix, recently wrote an article on maintaining developer autonomy in API environments for Netflix's tech blog. The August 23 blog post "Engineering Trade-Offs and the Netflix API Re-Architecture" explores the difficulty of reconciling developer code and process ownership with multiple team-wide shared services in API environments.

  • Amazon Introduces API Gateway Usage Plans

    Amazon recently updated their API Gateway service to include Usage Plans. A common pattern for companies that expose their APIs, include monetizing them through a 3rd party developer ecosystem. Usage Plans allow an organization to manage 3rd party developer consumption patterns and billing at an API key level.

  • Google's Chrome 53 Beta Brings Shadow DOM V1

    Google's Chrome 53 Beta brings support for Shadow DOM V1, as well as the PaymentRequest API. A significant improvement from the earlier V0 version, among the V1 upgrades are deprecation of multiple shadow roots, and a closed shadow root where a closed mode is designed to disallow any access to a node in a closed shadow root from an outside world.

  • API Mocking Tool WireMock v2 Released with Improved Request Matching and Stub Management

    WireMock v2, an API mocking and service virtualisation tool, has been released. Core enhancements include improved request verification failure reporting, the ability to create custom request matching logic (including the use of Java 8 lambdas), randomly distributed delays (currently with uniform and lognormal distributions), and matching on cookies and basic auth headers.

  • Uri Sarid on RAML 1.0 Release and Latest MuleSoft API News

    InfoQ had the opportunity to speak with Uri Sarid, the CTO of MuleSoft at their CONNECT 2016 annual conference in San Francisco. Sarid is the creator of RAML, which just released its long awaited version 1.0 in GA, so it was a good opportunity to follow-up from last year’s interview and also to get a broader view on MuleSoft’s solutions for API teams and his vision for APIs.

  • How and Why Etsy Moved to an API-First Architecture

    At QCon New York 2016, Etsy software engineer Stefanie Schirmer told how her company successfully transitioned to an API-first architecture that supports multiple devices, addresses server-side performance problems, and was quickly adopted by development teams.

BT