BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage REST Content on InfoQ

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

  • Microservices: Decomposing Applications for Deployability and Scalability

    What are microservices? 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.

  • Restify and Mobilize Your Data

    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.

  • Russ Miles on Antifragility and Microservices

    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.. We're discussing these new concepts with Russ Miles to find out what they are good for and how to apply them in an architect's or developer's daily business - for existing applications and those to come

  • Exposing CQRS Through a RESTful API

    Command Query Responsibility Segregation (CQRS) is an architectural pattern that segregates reads and writes of a system into two separate models. We propose and demonstrate an approach for building a RESTful API on top of CQRS systems. This approach joins HTTP semantics and resource-based style of REST APIs with distributed computing concerns such as eventual consistency and concurrency.

BT