Great book for a quick overview of Spring fundamentals as well as some other commonly used technologies (e.g. HikariCP) and Spring projects (such as Spring Data). The exposition is generally clear and easy to follow, albeit somewhat repetitive, because a common theme is that similar information is mentioned in a paragraph, in the figure or image accompanying the paragraph, and in the caption of the image. Had that been condensed, then the book could be a bit more concise, but I ended up learning to skim and skip whenever I saw the pattern coming.
Some details I think could be improved for a future edition are:
* When going over session scoped beans and using one in a singleton, it's never properly explained that what Spring is injecting is actually a proxy, and that's how redirecting to the right session-scoped bean is achieved, because using @SessionScope includes proxyMode TARGET_CLASS). One could get the wrong idea that using @Scope("session") would be the same, when it wouldn't.
* Though it warns against misuse of Aspects, it doesn't provide much guidance as to when they are appropriate. In particular, there is no mention of "cross-cutting concerns", which are their raison d'etre.
* When going over unit tests, it shows examples where dependencies such as a DAO are mocked. This follows the so called London school of testing, where the unit is a class and all but immutable dependencies should be mocked. I don't agree with this since I think that Vladimir Khorikov expressed a solid case against it in his book "Unit Testing: Principles, Practices, and Patterns". But proponents of this won't agree, so let's just leave it at that.
* It recommends the usage of an in-memory DB such as H2. A better recommendation is testing against the exact same DBMS used in production by using testcontainers. Most of the time a DB such as H2 or HSQLDB is fine, but from time to time there are small discrepancies with other databases such as MySQL or SQL Server, which cause either false positives or false negatives. Using testcontainers to test against the same database used in production avoids these issues and provides better assurance.
These things aside, I highly recommend it as a first book on Spring.