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 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.
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.
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
In this installment of our .NET Open Source series we talk to Thomas Imart. His library, Tweetinvi, is designed to make working with Twitter’s Stream API easier to use. 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