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

  • A Standardized, Specification-Driven API Lifecycle

    At QCon Plus last November, Kin Lane, Chief Evangelist with Postman, and the Open Technologies Team lead presented on API specifications. API specifications are essential to him and at Postman. So he wanted to share a bit of how they see API specifications impacting how they produce and consume APIs.

  • Ballerina for Full-Stack Developers: a Guide to Creating Backend APIs

    This article explores Ballerina’s intuitive syntax for writing REST APIs. We also discuss authentication, authorization, OpenAPI tool, observability, SQL/NoSQL client libraries, and key language features. At the end of this article, you will have a good understanding of why Ballerina is a prominent candidate for writing your next backend API.

  • Introducing the KivaKit Framework

    In this article, we take a brief tour of the KivaKit open source Java microservices application framework. KivaKit is a collection of mini-frameworks designed to work together. Each mini-framework is described in more detail at https://www.kivakit.org as well as on Jonathan Locke’s blog State of the Art.

  • Consistency, Coupling, and Complexity at the Edge

    Successful use of a microservices architecture requires maintaining a clear separation of concerns in the various layers and by employing design principles best suited to each layer. While RESTful API design has become the standard for microservices, it can cause problems at the UI layer. Alternatives such as the Backend-for-Frontend pattern using GraphQL can provide better separation of concerns.

  • Benefits of Loosely Coupled Deep Learning Serving

    As deep networks are becoming more specialized and resource-hungry, serving such networks on acceleration hardware in tight-budget environments is also becoming difficult. Instead of using API frameworks, loosely coupled components can be preferred as an alternative. They bring high controllability, easy adaptability, transparent observability, and cost-effectiveness when serving deep networks.

  • GraphQL Reference Guide: Building Flexible and Understandable APIs

    This online guide aims to answer pertinent questions for software architects and tech leaders, such as: Why would you use GraphQL? Why should you pay attention to GraphQL now? How can GraphQL help with data modelling in the Enterprise?

  • Overcoming RESTlessness

    New API protocols like GraphQL, gRPC, and Apache Kafka have risen in popularity as alternatives to REST-inspired HTTP APIs. Instead of seeking to replace REST, the software engineering industry should seek to evolve by building on the maturity of the REST ecosystem while exploiting the technological strengths of the new protocols.

  • Give REST a Rest with RSocket

    Representational State Transfer (REST) has become the de facto standard for communicating between microservices. The author argues that is not a good thing. We need a modern material to replace HTTP for creating modern services. Open source RSocket is designed for services. It is a connection-oriented, message-driven protocol with built-in flow control at the application level.​​​​​​​

  • The Argument for WCF Hosting in .NET Core

    Should WCF Hosting be Supported in .NET Core? To a lot of people this seems like a strange question; the answer is obviously... yes? no? Well actually it is quite contentious with people on both sides of the issue fiercely arguing for their position. We’ll try to unpack the debate and explain the arguments on both sides.

  • An "Integration-First" Approach to Building a Commerce Platform for Payment Terminals

    In this article Praveen Alavilli describes how they designed a payment terminal system for interoperability and extensibility, allowing developers to build new shopping experiences.

  • Always Be Publishing: Continuous Integration & Collaboration in Code Repositories for REST API Docs

    API documentation is an often overlooked part of making any API a success. This article explores how to make the documentation part of a continuous integration pipeline keeping it closer to the code itself.

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

BT