BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage REST Content on InfoQ

  • Metadata-Driven Design: Building Web APIs for Dynamic Mobile Apps

    More than ten years ago, software architect Kevin Perera invented a design method for architectures that was called "metadata-driven design and development". In this article, Aaron Kendall explains how to use this design method and outlines similarities as well as differences to current techniques like RESTful services or HATEOAS by implementing a metadata-driven mobile application.

  • Managing Technology with CORE Strategy & Architectural C’s & P’s

    Suman Pradhan, who has worked in healthcare, financials and technology sectors, has written about developing the CORE (Consolidate, Optimize, Refresh and Enable) approach to helping architects and developers build sustainable solutions that match the business needs. In this article he discusses CORE and compares and contrasts with other software architectural techniques.

  • Service-Oriented Architecture and Legacy Systems

    In this article, authors provide an overview of current SOA technologies and how to evolve in legacy environments. They also discuss the topics of SOAP vs. REST web services, Enterprise Application Integration and incremental transition to SOA in legacy environments.

  • REST-y Reader

    Rounding out our first Web APIs series Mike shares books he recommends for those who want to learn more about designing, implementing, and maintaining APIs for the Web.

  • Roy Fielding on Versioning, Hypermedia, and REST

    Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, the process of designing network software that can adapt over time, and the challenge of thinking at the scale of decades.

  • Making the Case for an API Roadmap

    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.

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

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

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

BT