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 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.
The content management company Box recently announced the arrival of four security and governance APIs. These APIs are aimed at helping companies handle legal, security, and compliance needs better.
The goal for the W3C Web payments working group is standardization of the flow, APIs and messages for online payments. These standardizations are meant to be payment method agnostic. On September 15, working drafts for the HTTP API and messages specifications were released for public comment.
Yelp announced the release of a brand new API called Fusion which provides developers with higher granularity filtering across Yelp data, greater access to uploaded photos and Yelp business partner data, and 24 hour caching.
Google is acquiring API management company Apigee for $635 million.
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.
Almost five years in the making, Dropwizard's Java RESTful Web Service framework version 1.0.0 offers a host of new features including Java 8, Http/2 and Scala support, and the latest versions of supporting Java APIs.
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 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.
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.
Pivotal’s cloud platform, Pivotal Cloud Foundry, now supports additional Apigee API management tooling focussed on hybrid (i.e. part public/part private) cloud support. While Apigee’s hybrid cloud management software, Edge Microgateway, was released last year, Cloud Foundry users can now utilize it within the Pivotal platform’s Apigee plugin.
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.
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.
Microsoft has published their guidance for creating “RESTful” APIs. Roy Fielding calls them HTTP APIs that have little to do with REST.