CODE Magazine / Articles

GraphQL

Articles filed under GraphQL

Articles

Showing 1–6 of 6

  1. CODE Magazine: 2024 - May/June cover

    From SOAP to REST to GraphQL

    This article by Joydip Kanjilal provides an overview of the evolution of web APIs from SOAP to REST to GraphQL. By understanding the progression from SOAP to REST to GraphQL, developers can make informed decisions when choosing the right API design for their projects. The article includes code examples and instructions for building applications using SOAP, REST, and GraphQL.

  2. CODE Magazine: 2023 - July/August cover

    Building Microservices Architecture Using GraphQL and ASP.NET 7 Core

    This article provides an overview of GraphQL, its features and benefits, and how it compares and contrasts with REST and gRPC. It also explains how to take advantage of GraphQL to build microservices-based real-time applications in ASP.NET Core 7 and provides an overview of GraphQL schemas and their components.

  3. CODE Magazine: 2021 - July/August cover

    Let’s Talk About Microsoft Graph

    It seems like everyone’s talking about Microsoft Graph these days. Sahil shows you why.

  4. CODE Magazine: 2021 - January/February cover

    Full Stack Cloud Development with AWS Amplify

    Get started developing for AWS using Amplify and React to build a simple photo application. Create back-end services using Amazon Cognito, a managed identity service, add storage, and use the GraphQL API to deploy. then use Amplify to build the front end.

  5. CODE Magazine: 2020 - March/April cover

    Introduction to GraphQL for .NET Developers: Mutation

    Peter uses the Hot Chocolate Library to teach you about GraphQL. Learn how to use the Entity Framework to access and store data and explore mutations using GraphQL.

  6. CODE Magazine: 2019 - September/October cover

    Intro to GraphQL for .NET Developers: Schema, Resolver, and Query Language

    Peter introduces you to GraphQL so your REST API client list can grow and change without a lot of pain. You can use strongly typed schema, eliminated over- and under-fetching, and you can get analytics about how clients are really using your API.