InfoQ Homepage API Content on InfoQ
-
API Conf Panel: Emerging Automation Layers on Top of Today’s APIs
The panelists present various approaches to API automation, sharing from their experiences.
-
API Conf Panel: API Design Best Practices
Jakub Nesetril, Tony Tam, Kirsten Jones share tools and tips for building great APIs.
-
Building Hypermedia APIs with HTML
Jon Moore discusses the pros and cons using HTML for an API media type, as well as the particulars of implementation patterns, from representations to building programmatic HTML clients.
-
API Conf Panel: APIs, Platforms and Ecosystem
The panelists explore the challenges API platform owners and users face in conflict situations and can be done to mitigate them.
-
API Conf Fireside Chat: Albert Wenger, Partner Union Square Ventures
Albert Wenger shares insight in the API business with examples from companies they have invested into, such as Twitter, Foursquare, Etsy, etc.
-
Introduction to WebSocket
Gunnar Hillert introduces WebSocket, the protocol and the corresponding W3C API, with an emphasis on the JSR-356 defining the Java EE 7 API.
-
API Conf Panel: API Business Models
John Musser, Joe Rago, Augusto Marietti, Steven Willmott, Michael Vizard
-
API Conf Fireside Chat: Peter Orlowsky, VP, Getty Images
Peter Orlowsky provides insights into the strategy choices that created Getty Images’ API program and the customer/business value the API creates.
-
API Conf Panel: API Infrastructure Providers
Many of today’s APIs rely on 3rd party systems, software and services to operate, infrastructure that comes in various flavors. This panel covers these different flavors and how to choose between them
-
Writing Usable APIs in Practice
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
-
API Conf Panel: The Future of Media API
Irakli Nadareishvili, Jon Moore, and Anthony Cuellar share insight in creating teams and building media APIs for distributing content.
-
Web Development: You're Doing It Wrong
Stefan Tilkov challenges many commonly-held assumptions about how to best develop web applications, emphasizing the strengths and ideal roles for HTML, CSS, JavaScript, HTTP and URIs.