InfoQ Homepage Web API Content on InfoQ
-
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.
-
How to Test ASP.NET Core Web API
In this article, we will investigate testing your ASP.NET Core 2.0 Web API solutions. We will look at internal testing with Unit Testing and externally testing your solution with a new testing framework in ASP.NET Core called Integration Testing.
-
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.
-
Advanced Architecture for ASP.NET Core Web API
This article looks into how ASP.NET Core makes it easy to build a modern web API. This enables an implementation that is easy to design, test, and maintain. By using the Ports and Adapter Pattern business logic can be decoupled from API frameworks and data access.
-
InfoQ Call for Articles
InfoQ provides software engineers with the opportunity to share experiences gained using innovator and early adopter stage techniques and technologies with the wider industry. We are always on the lookout for quality articles and we encourage practitioners and domain experts to submit feature-length (2,000 to 3,000 word) papers that are timely, educational and practical.
-
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.
-
Key Steps to Building and Managing an Effective API Marketplace
Across industries, companies are now looking for ways to shape their digital businesses by extending their services through external APIs. To reap the benefits of an API program, however, organizations need to move beyond basic API management to creating an API marketplace, a specialized type of platform business model that focuses on connecting producers and consumers.
-
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.
-
Untangling an API-First Transformation at Scale. Lessons Learnt at PayPal – Part 3
This is the third in a three-part series that explores how PayPal has adopted a more API-first approach to building platform services. In this article, we’ll take a closer look at the program aspects and some of the execution and operational challenges that had to be overcome.
-
Untangling an API-first Transformation at Scale. Lessons Learnt at PayPal – Part 2
This is the second in a three-part series that explores how PayPal has adopted a more API-first approach to building platform services. In this article, we’ll take a closer look at how the portfolio of API’s themselves are managed.