Book Image

Modern API Development with Spring and Spring Boot

By : Sourabh Sharma
Book Image

Modern API Development with Spring and Spring Boot

By: Sourabh Sharma

Overview of this book

The philosophy of API development has evolved over the years to serve the modern needs of enterprise architecture, and developers need to know how to adapt to these modern API design principles. Apps are now developed with APIs that enable ease of integration for the cloud environment and distributed systems. With this Spring book, you'll discover various kinds of production-ready API implementation using REST APIs and explore async using the reactive paradigm, gRPC, and GraphQL. You'll learn how to design evolving REST-based APIs supported by HATEOAS and ETAGs and develop reactive, async, non-blocking APIs. After that, you'll see how to secure REST APIs using Spring Security and find out how the APIs that you develop are consumed by the app's UI. The book then takes you through the process of testing, deploying, logging, and monitoring your APIs. You'll also explore API development using gRPC and GraphQL and design modern scalable architecture with microservices. The book helps you gain practical knowledge of modern API implementation using a sample e-commerce app. By the end of this Spring book, you'll be able to develop, test, and deploy highly scalable, maintainable, and developer-friendly APIs to help your customers to transform their business.
Table of Contents (21 chapters)
1
Section 1: RESTful Web Services
7
Section 2: Security, UI, Testing, and Deployment
12
Section 3: gRPC, Logging, and Monitoring
16
Section 4: GraphQL

Chapter 13 – GraphQL Fundamentals

  1. It depends on the use cases. However, it performs much better for mobile apps and web-based UI applications.
  2. Fragments should be used while sending a request from the GraphQL client when the response contains an interface or union.
  3. You can use a variable in a GraphQL query/mutation as shown next. You are going to modify the GraphQL request sent in step 6 of the Testing GraphQL Query and Mutation section:
    mutation removeStar ($repoId: String) {
      addStar(input: {
        starrableId: $repoId
      }) {
        clientMutationId
      }
    }
  4. Here, you can see that the $repoId variable is used. You have to declare that variable in the named mutation and then you use it in the mutation's argument as shown in the following code block:
    {
      "repoId": "MDEwOlJlcG9zaXRvcnkyOTMyOTU5NDA="
    }