BT

InfoQ Homepage Web API Content on InfoQ

  • How Zalando Delivers APIs with Radical Agility

    InfoQ interviewed Thomas Fraustein, architect at Zalando, about his team’s radical agility development organization that is optimized for an API-first approach. He explains what an API-first approach is, and provides tips on building good APIs for scalable microservice architectures where a large number of services are offered efficiently.

  • Virtual Panel: Document and Description Formats for Web APIs

    In this virtual panel we hear from 4 individuals deeply involved in the Web API space. Each of them has a unique take on the values, benefits, and costs of documentation and description formats in general, and provide their own unique perspective from their vantage points across the Web. They agree on one thing: something must be done to help developers find their way through the world of Web APIs

  • An Open API Initiative Update

    The Open API Initiative group is evolving what has become the de-facto standard API Description Format to produce a consistent and compatible format for describing APIs, allowing interoperation between tooling, systems, and runtime environments. Tony Tam, creator of the popular Swagger Specification is providing an update on the group activity.

  • Creating RESTful Services with T4 Based on Model and Interfaces

    When generating RESTful services with WebAPI, a lot of boilerplate code has to be implemented. Amel Musić demonstrates how T4 and EnvDTE can be used to create a flexible code generator that dramatically reduces the amount of time and effort this takes.

  • HTTP-RPC: A Lightweight Cross-Platform REST Framework

    HTTP-RPC is an open-source framework allowing developers to create and access cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles such as statelessness and uniform resource access.

  • One API, Many Facades?

    An interesting trend is emerging in the world of Web APIs, with various engineers and companies advocating for dedicated APIs for each consumer with particular needs. Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. You might need to optimize your API accordingly.

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

  • Programming with Semantic Profiles: In the Land of Magic Strings, the Profile-Aware is King

    As this article’s author, Mark Foster, puts it, "Absent profiles, the API space will be relegated to blindly passing around 'magic strings, fooling ourselves into thinking we are passing reliable semantic information." Here, Foster — one of the editors of the ALPS specification — explains what semantic profiles are and how they can transform the way Web APIs are desgined and implemented.

  • Profiles on the Web: An Interview with Erik Wilde

    Erik Wilde talks to Mike Amundsen about Profiles, Description, Documentation, Discovery, his Sedola project and the future of Web-level metadata for APIs.

  • The APIs.json Discovery Format: Potential Engine in the API Economy

    In the fast growing world of APIs and microservices, finding just the right API when you are developing a web, or mobile application, or possibly integrating between existing systems, is always a tedious task.

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

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.