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

Consuming APIs using Fetch

Let's create the first component—that is, the Product Listing Page. Create a new file in the src/components directory with the name ProductList.js. This is the parent component of the Product Listing page.

This component fetches the products from the backend server and passes them to the child component, Products (It create a new Products.js file under the components directory).

Products contain the logic of fetched product list iterations. Each iteration renders the card UI for each product. ProductCard is another component, therefore you'll create another file, ProductCard.js, under src/components. You can write the product card logic inside products, but to single out the responsibility it's better to create a new component.

The ProductCard component has a Buy now button and an Add to bag link. These links should only work if the user is logged in, else it should redirect the user to the login page.

You now have an idea...