This article, the first of a new series, examines APIs from a business perspective. It covers the importance of tying your APIs back to your business value, with examples from 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 maintaining public APIs on the Web over time.
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? 1
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.
Donald Raab, creator of GS Collections, reveals the power of that framework, and how together with Lambda expressions, it sprinkles Java with some of the sparkle of Smalltalk.
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