InfoQ Homepage GraphQL Content on InfoQ
Articles
RSS Feed-
/articles/federated-GraphQL-platform-Netflix/en/smallimage/Evolving-the-Federated-GraphQL-Platform-at-Netflix-small-1691653833320.jpg)
Evolving the Federated GraphQL Platform at Netflix
This article describes the journey of the migration towards a Federated GraphQL architecture. Specifically, it shows the GraphQL platform Netflix has built consisting of the Domain Graph Services framework for implementing GraphQL services in Java using Spring Boot and graphql-java, and tools for schema development. It also describes how the ecosystem has evolved at various stages of adoption.
-
/articles/graphql-ballerina/en/smallimage/graphql-ballerina-s-1656508786726.jpg)
Using GraphQL and Ballerina with Multiple Data Sources
The Ballerina programming language is well-suited to developing GraphQL applications, due to the network abstractions, network-aware type system, clear data representations, and visual diagrams. This article discusses the benefits of GraphQL and Ballerina, and walks through a sample application that retrieves data from a database and a 3rd-party API.
-
/articles/Standardized-Specification-Driven-API-Lifecycle/en/smallimage/logo-1647025459155.jpg)
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.
-
/articles/auth-layer-auth0-hasura/en/smallimage/logo-1629735628854.jpg)
Bootstrapping the Authentication Layer and Server with Auth0.js and Hasura
When you're trying to prototype an MVP for your app and want to start iterating quickly, the upfront cost of setting up authentication can be a massive roadblock. The authentication layer requires significant work, and you must always be on the lookout for security vulnerabilities.
-
/articles/consistency-coupling-complexity/en/smallimage/consistency-coupling-complexity-s-1628577348640.jpg)
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.
-
/articles/GraphQL-ultimate-guide/en/smallimage/GraphQL-Pillar-Page-small-1615289418898.jpg)
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?
-
/articles/architecture-trends-2020/en/smallimage/InfoQ-Trend-Report-logo-1586328980243.jpg)
Software Architecture and Design InfoQ Trends Report—April 2020
An overview of how the InfoQ editorial team sees the Software Architecture and Design topic evolving in 2020, with a focus on fundamental architectural patterns, framework usage, and design skills.
-
/articles/overcoming-restlessness/en/smallimage/overcoming-restlessness-s-1548835990305.jpeg)
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.