Thank You for your answers.
Yes I am aware that a lot of things changed since 2005. But I thought that this book could give good spring behind the scenes understanding. Like Head First Java is really outdated too, but it gave me such a good understanding of OOP principles, and understanding threads, not just with code examples, but with pictures and diagrams of what's really happening. But now I think, that maybe it isn't good option to invest my time into this book, and start learning principles from more up to date sources.
Yes I'm aware of spring documentation, it's really great. Also I like javabrains youtube channel. He is really good at explaining principles how everything is working, not just commenting on he's code.
In addition to that I want to read a book too. To see everything blend in a real life application. For example jms/rabbit messaging. Udemy/youtube tutorials just gives you how to implement classes for messaging and
develops a Hello World application with it. I now how to implement messaging services, I can write listeners, senders and etc. myself, but I need to understand what's the use of it in real world application, what we are sending, why we are sending, what we can do next when we receive it, and how ti affects application, that's where I lack knowledge.
And one more thing I really want to understand what is synchronous and asynchronous, blocking and non-blocking. Most of books I looked at, just says that blocking blocks, and non-blocking doesn't, but that is in their definition, it doesn't really say how non blocking is working compared to blocking and begins to implement methods with <Mono> or <Flux>. I didn't find good source to learn that, it would be great to find diagrams or something to show how it really works, not just theoretical approach.
Learning Spring Boot 2.0 book has a much content about messaging and blocking/non blocking. Don't now if it's good at explaining things, but maybe I should give it a try?
Second book is .
Getting started with Spring Framework
I like it's aproach. It's starts chapters with application’s requirements, what our application will do, what we need to do to implement this. Also has many diagrams, that I find useful.