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 10: gRPC Fundamentals

gRPC is an open source framework for general-purpose Remote Procedure Calls (RPCs) across a network. RPC allows a remote procedure (hosted on a different machine) to call as if it is calling a local procedure in connected systems without coding the remote interaction details. RPC has a constant meaning in gRPC abbreviation. It seems logical that the g in gRPC would refer to Google because it was initially developed there. But the meaning of the g has changed with every release. For its first release, version 1.0, the g in gRPC stood for gRPC itself. That is, in version 1, it stands for gRPC Remote Procedure Call. You are going to use gRPC version 1.37, in which the g stands for gilded. Therefore, you can refer to gRPC as gilded Remote Procedure Call (for version 1.37). You can find out all the meanings of the g for different versions at https://github.com/grpc/grpc/blob/master/doc/g_stands_for.md.

In this chapter, you'll learn the fundamentals...