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.
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.
The article describes the general outline of the Stats Anomalies Detector developed at MyHeritage and provides a detailed explanation of how to enhance the code to meet your company’s needs.
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? 2
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? 8
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. 1
Apache CouchDB is a 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. 3
There's recently been a lot of discussion about the convergence of SOA Governance and API Management. InfoQ spoke to a panel of SOA Governance and API Management experts to garner their views. 1
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. 1
Many development teams publish SOA services, yet struggle to create a service architecture that is widely shared, re-used, and adopted across internal development teams. 1
The n+1 one problem doesn’t just affect ORMs, any kind of Web API can suffer from the same performance problems. Ali Kheyrollahi discusses some of the ways to identify and correct n+1 scenarios.
This article describes the increasingly popular Microservice architecture pattern, used to architect large, complex and long-lived applications as a set of cohesive services that evolve over time. 12
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
5 OAuth Essentials for API Access Control.
OAuth standardizes a number of important access-related challenges for API publishers. However, deploying OAuth as an authorization mechanism for enterprise APIs raises challenges around scalability...
5 Pillars of API Management.
The boundaries of the traditional enterprise are blurring, as organizations open their on-premise data and application functionality for use in new internal and external applications...
A Guide to REST and API Design.
“If all you have is a hammer, then everything looks like a nail,” said American psychologist Abraham Maslow as he tackled the idea that those in the field of psychology needed to approach treatment from multiple perspectives...
A How-to Guide to OAuth & API Security.
OAuth is an emerging Web standard that lets users grant third-party clients restricted access to resources they own. In the past, it was common to ask a user to...
Protecting Your APIs Against Attack and Hijack.
The application programming interface (API) is an emerging technology for integrating applications using Web technology. This approach is exploding in popularity...
5 Ways to Get Top Mobile Developer Talent for your Open APIs.
In this eBook, we will provide a detailed overview of five key ways smart enterprises attract and nurture top third-party developer talent...