Book Image

Modern API Development with Spring 6 and Spring Boot 3 - Second Edition

By : Sourabh Sharma
1 (1)
Book Image

Modern API Development with Spring 6 and Spring Boot 3 - Second Edition

1 (1)
By: Sourabh Sharma

Overview of this book

Spring is a powerful and widely adopted framework for building scalable and reliable web applications in Java, complemented by Spring Boot, a popular extension to the framework that simplifies the setup and configuration of Spring-based applications. This book is an in-depth guide to harnessing Spring 6 and Spring Boot 3 for web development, offering practical knowledge of building modern robust web APIs and services. The book covers a wide range of topics that are essential for API development, including RESTful web service fundamentals, Spring concepts, and API specifications. It also explores asynchronous API design, security, designing user interfaces, testing APIs, and the deployment of web services. In addition to its comprehensive coverage, this book offers a highly contextual real-world sample app that you can use as a reference for building different types of APIs for real-world applications. This sample app will lead you through the entire API development cycle, encompassing design and specification, implementation, testing, and deployment. By the end of this book, you’ll have learned how to design, develop, test, and deploy scalable and maintainable modern APIs using Spring 6 and Spring Boot 3, along with best practices for bolstering the security and reliability of your applications and improving your application's overall functionality.
Table of Contents (21 chapters)
1
Part 1 – RESTful Web Services
7
Part 2 – Security, UI, Testing, and Deployment
12
Part 3 – gRPC, Logging, and Monitoring
16
Part 4 – GraphQL

Understanding the basic structure of OAS

The OpenAPI definition structure can be divided into the following sections (all are keywords and case-sensitive):

  • openapi (version)
  • info
  • externalDocs
  • servers
  • tags
  • paths
  • components

All the preceding terms are part of root. The first three sections (openapi, info, and externalDocs) are used to define the metadata of the API.

You can place an API’s definition either in a single file or divided into multiple files. OAS supports both. We’ll use a single file to define the sample e-commerce API.

Instead of discussing all the sections theoretically and then writing the e-commerce API definitions, we’ll do both together. First, we’ll cover each section definition of the e-commerce API, and then we’ll discuss why we have used it and what it implies.

The metadata sections of OAS

Let’s have a look at the metadata sections of the e-commerce API definitions:

...