InfoQ Homepage API Content on InfoQ
-
An Interview with HAL Creator Mike Kelly
As part of our ongoing series on Web APIs Mike Amundsen talks to Mike Kelly about his reasons for creating HAL and his experiences over the last three years with web developers and the API community.
-
A Business Perspective on APIs
This article, the first of a new series, examines APIs from a business perspective, whether or not they are open and overtly monetized. It covers the importance of tying your APIs back to your business value, looks at the type of data that should be used, and studies the success stories of Amazon and Twilio.
-
Article Series: Web APIs: From Start to Finish
This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges, and taking the long view on maintaining public APIs on the Web over time. Along the way there are interviews with influential individuals and even a suggested reading list on APIs and related topics.
-
Stats Anomalies Detector
The article describes the general outline of the Stats Anomalies Detector we developed at MyHeritage and provides a detailed explanation of how to enhance the code (will be available soon at MyHeritage GitHub) to meet your company’s needs.
-
Sam Newman: Practical Implications of Microservices in 14 Tips
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? At last GeeCon 2014 in Krakow, Sam Newman tried to answer those questions by giving 14 tips about how microservices can interface, how the can be monitored, deployed, and made safer.
-
Why Some Web APIs Are Not RESTful and What Can Be Done About It
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful?
-
Why SOA Should Be Viewed As “Dependency-Oriented Thinking”
Ganesh Prasad proposes minimizing service dependencies in a SOA implementation rather than avoiding point-to-point connections in order to obtain a more flexible system that can evolve over time.
-
Apache CouchDB: The Definitive Introduction
Apache CouchDB is an open source document NoSQL database that uses JSON for storing documents. In this article, Jan Lehnardt gives an overview of CouchDB, its architecture and what problems it aims to solve and why it is different from all other databases.
-
Virtual Panel: Convergence of SOA Governance and API Management
There's recently been a lot of discussion about the convergence of SOA Governance and API Management. Services and APIs appear to deal with similar concerns, but historically the approach & philosophy has been different. Is there convergence and how? InfoQ spoke to a panel of SOA Governance and API Management experts to garner their views.
-
SOA and API Schism and Unification
While both API and SOA have similar business and technical goals, many API proponents continue to describe APIs as a significantly different approach with little connection to SOA. They often promote a deep and divisive schism between pragmatic REST APIs and SOA. The division inhibits cleanly integrating SOA services and RESTful APIs into a unified architecture.
-
Converging API Governance and SOA Governance
Achieving Service Oriented Architecture initiative success requires creating loosely coupled consumer-provider connections, enforcing a separation of concerns between consumer and provider, exposing a set of re-usable, shared services, and gaining service consumer adoption. Many development teams publish SOA services, yet struggle to create a service architecture that is widely adopted.
-
Web APIs and the n+1 Problem
The n+1 one problem doesn’t just affect ORMs. Any kind of Web API, RPC/Web Service or RESTful, can suffer from the same performance problems. In this article, Ali Kheyrollahi discusses some of the common scenarios that lead to n+1 in web APIs and ways to correct them.