BT

InfoQ Homepage API-Design Content on InfoQ

Articles

RSS Feed
  • Using OpenAPI to Build Smart APIs for Dumb Machines

    This article discusses how to build, manage and maintain APIs with OpenAPI, including some of the most notable features in v. 3.0.

  • On Abstractions and For-Each Performance in C#

    Donald Knuth famously said, “We should forget about small efficiencies, say about 97% of the time”. But when faced with the other 3%, it is good to know what’s going on behind the scenes. So in this article we’ll be taking a dive into the foreach loop.

  • Designing with Exceptions in .NET

    Exceptions are an integral part of working with .NET, but far too many developers don’t think about them from an API design perspective. Most of their work begins and ends with knowing which exceptions they need to catch and which should be allowed to hit the global logger. You can significantly reduce the time it takes to correct bugs if you design the API to use exceptions correctly.

  • Microservices Evolution at SoundCloud

    At the MicroXchg conference in Berlin, Bora Tunca from SoundCloud presented the evolution of SoundCloud’s microservices architecture throughout the years. We had the opportunity to interview him and learn more about SoundCloud’s architecture evolution and microservices in general.

  • Graph API in a Large Scale Environment

    MyHeritage is a rapidly-growing destination used around the world to discover, preserve and share family histories. There is increasing demand for our services, accessed both internally and externally by our partners via the FamilyGraph API. Millions of API calls are made every day providing a huge challenge in terms of performance, scalability and security.

  • Metadata-Driven Design: Designing a Flexible Engine for API Data Retrieval

    Bulk data is commonly accessed via files & FTP. As the world moves toward APIs to facilitate collaboration, what are the requirements for data APIs? This article describes a meta-data driven architecture for bulk data ingestion. Two APIs operate in parallel to provide data changes as well as the data records themselves. An example demonstrates how API responses are parameterized using meta-data.

  • Review: Designing APIs for the Web

    Mike Amundsen's video series "Designing APIs for the Web" is a straightforward dive into API design suitable for a broad set of stakeholders. The thirteen part series provides a rich blend of practical advice, new ideas & a bit of controversy to keep you on your toes. This article reviews the series so you know what to expect. It provides an overview of the content and a balanced commentary.

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

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

  • Designing an Event Log API with RAML

    API designers have several documentation formats to choose from. RAML, a recently open-sourced API documentation format adopts a contract-first approach which has become the favoured model for API design. The RAML language also includes constructs that help reduce duplication inherent in other formats. This article steps through a simple API design to illustrate some of RAML's DRY features.

  • Seven Steps to Create an Unbeatable Enterprise Mobility Strategy

    As mobility is transforming our lives, this article gives a step-by-step approach on how enterprises can seamlessly connect their mobile workforce to back-end systems for increased productivity. Covering topics like business goal definition, API and data security or user experience it provides a broad overview on what to keep in mind while planning an enterprise mobility strategy.

  • Minding the API Hierarchy of Needs with RAML and APIkit

    Reza Shafii explains how to satisfy two fundamental needs of API design and implementation, as defined by the API hierarchy of needs, with RAML, API Designer and APIkit.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.