Book Image

Learning Spring Boot 3.0 - Third Edition

By : Greg L. Turnquist
Book Image

Learning Spring Boot 3.0 - Third Edition

By: Greg L. Turnquist

Overview of this book

Spring Boot 3 brings more than just the powerful ability to build secure web apps on top of a rock-solid database. It delivers new options for testing, deployment, Docker support, and native images for GraalVM, along with ways to squeeze out more efficient usage of existing resources. This third edition of the bestseller starts off by helping you build a simple app, and then shows you how to secure, test, bundle, and deploy it to production. Next, you’ll familiarize yourself with the ability to go “native” and release using GraalVM. As you advance, you’ll explore reactive programming and get a taste of scalable web controllers and data operations. The book goes into detail about GraalVM native images and deployment, teaching you how to secure your application using both routes and method-based rules and enabling you to apply the lessons you’ve learned to any problem. If you want to gain a thorough understanding of building robust applications using the core functionality of Spring Boot, then this is the book for you. By the end of this Spring Boot book, you’ll be able to build an entire suite of web applications using Spring Boot and deploy them to any platform you need.
Table of Contents (17 chapters)
1
Part 1: The Basics of Spring Boot
3
Part 2: Creating an Application with Spring Boot
8
Part 3: Releasing an Application with Spring Boot
12
Part 4: Scaling an Application with Spring Boot

Using custom finders

To create a custom finder, go back to the repository we created earlier, VideoRepository, and add the following method definition:

List<VideoEntity> findByName (String name);

The preceding code can be explained as follows:

  • The findByName(String name) method is called a custom finder. We never have to implement this method. Spring Data will do it for us as described in this section.
  • The return type is List<VideoEntity>, indicating it must return a list of the repository’s domain type.

This interface method is all we need to write a query. The magic of Spring Data is that it will parse the method name. All repository methods that start with findBy are flagged as queries. After that, it looks for field names (Name) with some optional qualifiers (Containing and/or IgnoreCase). Since this is a field, it expects there to be a corresponding argument (String name). The name of the argument doesn’t matter.

Spring Data...