InfoQ Homepage API Content on InfoQ
-
Rethinking CodeGen: IDL, Thrift, gRPC, Ohh My
Cameron Waeland discusses the evolution of Compass and presents their extensible code generation framework which is at the heart of their automatically generated REST to gRPC reverse proxy.
-
Open Data in UK
Senaka Fernando discusses Open Data: what it is, who uses it, why APIs are important, and how to promote the use of it.
-
Front-End APIs: Powering Fast-Paced Iterations
Aditya Modi and Karthik Ramgopal explore LinkedIn’s ideas behind API modeling, the challenges they’ve faced, and how they are evolving their modeling strategy over time based on their learnings.
-
Generating Unified APIs with Protocol Buffers and gRPC
Chris Roche and Christopher Burnett discuss how they extended the Protocol Buffer (PB) IDL to create unified APIs and data models, and how they used Envoy to move HTTP 1.1 services to gRPC.
-
How to Structure Your Bot with Clarke
Hugo Hache introduces Clarke, a Ruby DSL library designed to build conversational bots.
-
Financial Grade OAuth and OpenID Connect
Nat Sakimura discusses using OAuth and OpenID for securing financial transaction services.
-
Email Enters the Bots’ Era: How to Bridge the Divide Between an Old & A New Technology
Antoine Lefeuvre compares emails and bots, highlighting the benefits and drawbacks of each.
-
Go Mobile in Africa and Monetize to 116M Customers Thanks to APIs
Aurélien Duval Delort presents Orange’s mobile APIs available in Africa.
-
Refactor Front-end APIs & Accounting for Tech Debt
Julia Nguyen talks about accounting for technical debt in feature work and best practices in refactoring front-end APIs based on her work adding Apple Pay support to perk itemization at Indiegogo.
-
From Customer Self Service Portals to Web APIs
Florian Marquardt presents how Regiocom has created and uses web APIs to serve the energy market in several countries.
-
Reinventing Credit Insurance with APIs
Christophe Spoerry discusses embedding insurance in B2B innovations.
-
How to Survive the API Copyright Apocalypse
Steven Willmott recommends avoiding the possible API copyright troubles by sharing API definitions rather than copyrighting them.