BT
Older rss
  • Making the Case for an API Roadmap

    by Chris Haddad on  Nov 26, 2014

    Chris Haddad explains why one should create a roadmap for an API, providing advice on avoiding common API pitfalls, creating business value and monetizing API assets.

  • An Interview with HAL Creator Mike Kelly

    by Mike Amundsen on  Nov 25, 2014 3

    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

    by Matt McLarty on  Nov 18, 2014 2

    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

Posted by Mike Amundsen on  Nov 18, 2014

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.

Sam Newman: Practical Implications of Microservices in 14 Tips

Posted by Sergio De Simone on  Oct 28, 2014

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

Why Some Web APIs Are Not RESTful and What Can Be Done About It

Posted by Abel Avram on  Oct 26, 2014

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

Why SOA Should Be Viewed As “Dependency-Oriented Thinking”

Posted by Ganesh Prasad on  Oct 16, 2014

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

Posted by Jan Lehnardt on  Aug 28, 2014

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

Web APIs and the n+1 Problem

Posted by Ali Kheyrollahi on  Jun 02, 2014

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.

Microservices: Decomposing Applications for Deployability and Scalability

Posted by Chris Richardson on  May 25, 2014

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. 8

Restify and Mobilize Your Data

Posted by Val Huber on  May 21, 2014

Val Huber explains creating a RESTful API from an existing database schema, extending the API to define multi-table hierarchical resources, and adding behavior using declarative reactive expressions. 2

Russ Miles on Antifragility and Microservices

Posted by Ralph Winzinger on  May 13, 2014

Currently, Antifragility and Microservices are trending topics and this might be a hint that there are new architectural paradigms or design patterns on their way for building application systems.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT