Design Pattern using Spring Boot instead of DTO, Dao, Service?

recently I started reading a book that explains in more detail the manipulation of databases, in terms of the relationships between them, especially. The problem is that this book is a bit old, from 2014 ... So I come with the following questions, to which you can clarify, please:

In the book we use Dao, Dto and Service pattern, but we can't use Jpa ... Spring Boot Repository or other new technologies to "replace" the old implementation that the book presents?

If so, can you give me an alternative to the code below, and how does it work? What could I improve, what could I give up, what should be completed, what should I learn, please!

Book divide the implementations of an Application in 2 teams:

• UserInterface (Data Transfer Object of the entity, singleton in Memory DB and Controller as Mock Service and view)

• Development Team (with creating the Entity and testing using TDD, creating DAO for that Entity, Business Service Tier and Presentation Tier

So, i can change this way of creating and manipulating the applications and Databases, if yes, how, and why? What i should use, how i should do it...

This is the git of the book i'm currently reading: https://github.com/Spring-Hibernate-Book/spring-hibernate-datamodeling-tdd-rest/tree/master/Spring-OODD/src

Thanks for your time, patience and wiling to help! And sorry for my low level english...