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 11 – gRPC-Based API Development and Testing

  1. Because, unlike HTTP libraries, gRPC libraries also provide the following features:

    a. Interaction with flow control at the application layer

    b. Cascading call cancellation

    c. Load balancing and failover

  2. Yes, we can. You can use the metadata as shown in the next code block. However, making use of com.google.rpc.Status allows you to use the details (with a type of Any) object, which can capture more information:
    Metadata.Key<SourceId.Response> key =
        ProtoUtils.keyForProto(SourceId.Response.getDefaultInstance);
     
    Metadata metadata = new Metadata();
    metadata.put(key, sourceIdResponse);
    respObserver.onError(Status.INVALID_ARGUMENT
       .withDescription("Invalid Source ID")
       .asRuntimeException(metadata));
  3. com.google.rpc.Status can include details of type Any, which can be used to provide more error details. io.grpc.Status does not have a field that...