BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage API Content on InfoQ

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

  • C#/Web API Code Generation Patterns for the RAML User

    In this article, Jonathan Allen outlines the design patterns that users of REST specification languages such as RAML, Swagger, and API Blueprint should adhere to when generating code for C# and ASP.NET Web API. This includes topics such as model validation, async support, and request cancellation.

  • Enterprise Mobility is Going Beyond “Mobile First” Approach. Are You Ready?

    The mobile revolution is changing the way organizations work and manage their operations, as well as engage with their employees. As a result, organizations are reconsidering their technologies and techniques to make their traditional organizational cultures and roles more mobile friendly, making ‘mobile first’ a must have strategy.

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

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

  • From Monolith to Multilith at ticketea

    ticketea is a large online ticket selling platform in Spain. This article describes their growing pains and how DevOps and an API-based distributed architecture allowed them to cope with growth, both from a technical (from monolith to multilith) and people (awareness and knowledge sharing) perspective.

  • Thinking Outside-In: How APIs Fulfill the Original Promise of Service-Oriented Architecture

    The article explores how and why APIs are a lightweight and agile way of building reusable business systems. While some SOA adopters delivered these goals many efforts faced complexity and failed. The key difference with APIs is in the shift from hierarchical services to distributed resources, simplicity, statelessness and a focus on making it practical for the business to understand and implement

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

BT