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

An overview of the e-commerce app

The e-commerce app is a simple online shopping application. It provides the following features:

  • A user can browse through the products.
  • A user can add/remove/update the products in the cart.
  • A user can place an order.
  • A user can modify the shipping address.
  • The application can only support a single currency.

E-commerce is a very popular domain. If we look at the features, we can divide the application into the following subdomains using bounded contexts:

  • Users: This subdomain is related to users. We'll add the users RESTful web service, which provides REST APIs for user management.
  • Carts: This subdomain is related to the cart. We'll add the carts RESTful web service, which provides REST APIs for cart management. Users can perform CRUD operations on cart items.
  • Products: This subdomain is related to the products catalog. We'll add the products RESTful web service, which provides REST APIs to search and retrieve the products.
  • Orders: This subdomain is related to orders. We'll add the orders RESTful web service, which provides REST APIs for users to place orders.
  • Payment: This subdomain is related to payments. We'll add the payment RESTful web service, which provides REST APIs for payment processing.
  • Shipping: This subdomain is related to shipping. We'll add the shipping RESTful web service, which provides REST APIs for order tracking and shipping.

Here's a visual representation of our app's architecture:

Figure 1.2 – The e-commerce app architecture

Figure 1.2 – The e-commerce app architecture

We'll implement a RESTful web service for each of the subdomains. We'll keep the implementation simple, and we will focus on learning these concepts throughout this book.