Full description not available
M**S
The book needs a glossary but it’s good
Overall I think the book is probably one of the best you can get today. The book quickly takes you through pieces to help you get up to speed with spring boot, where it’s been, what you can do today and where it’s going . It was written so that you have a fairly decent background and what’s being accomplished . My biggest complaint is the lacking of the glossary . This would help people who have already started playing with reactive spring a whole lot.
M**R
As a Spring Developer I found this book extremely helpful
There are a few different approaches a programming book can take. One approach is more textual explaining the concepts with small little snippets of code, another is to fill the book with so much code samples that you can see how everything works in the real world and of course a nice mix of both.In Josh Long's book Reactive Spring, he takes the approach of presenting every piece of real world sample code he can provide. It is really great stuff from a Spring FLUX/MVC approach that many are already familiar with to a configuration routing to handlers approach which matches approaches other projects take. Even command line apps that act as servers handling requests and responses. Since there are so many ways you can use Spring Reactive in your projects, you need a book like this that can show you how to use it correctly in your project.Josh has a great way to really describe the code and what is going on, so that you don't have to rack your brain deciphering it. The code is very clean. He explains all the concepts well to also go along with the code. It also comes with Josh's great sense of humor, so much his voice that I literally heard his voice in my head reading the book to me as I read along.If you really want to learn everything about Spring Reactive projects, then this is the book you should get.
E**C
Some Good Some Bad
Initially I really enjoyed reading this book, I even didn't mind the first few chapters which were a basic intro to Spring, which is something I'd generally skip over, but read it anyways because I enjoyed how it was written. Passed the Spring intro and reactive intro, I started to see a few problems when diving into the heart of the book:0) Josh sells reactive hard, but I think that's a tough pill to swallow. Even 2 years after the publication of the book, I think spring reactive is still a little rough around the edges. For example, at one point R2DBC is mentioned as an experimental feature. I was glad to learn about it, until I learned even now R2DBC (relational database connectivity i.e reactive jdbc) has no production ready db drivers.1) One repeating theme of the book is, "That was Easy!". Sure, you can understand and implement the examples, but let's be honest reactive can get pretty complicated. Many of the "simple" examples are really non-trivial when you actually look closely.2) I'm not a fan of how the chapter examples are structured. I think examples should be like tests, from the standpoint what you see is what you get. In some chapters there is a separate common module which performs setup tasks. The problem is, some of those setup tasks are only used by a single example in the chapter (ie. a ton of setup to handle RSocket headers, which is only used by 2 examples).3) It was annoying that it wasn't mentioned that Thread.currentThread().join() was added to the Main class in RSocketRequester and WebClient examples. I can't be the only one who spent too long getting a trivial example to work only to realize that the user thread was exiting before the daemon thread performing the request could complete. For concurrency work, this is kind of basic, but with all of Springs abstraction away of the Threads, I really think this deserved discussion.Final thoughts. I don't regret reading this book. I will only use Reactive if I absolutely have to, and am looking forward to other projects that make it obsolete. I enjoy Josh's writing, but I do think up he could clean up his examples to avoid internal dependencies.
B**O
Print quality is terrible
This book may cause eye strain. Print quality is very poor
S**I
Touches variety of Spring modules that are Reactive but assumes knowledge of Spring config beans
Better read the book "Unraveling Project Reactor" by Esteban Herrera to focus on just learning reactive programming with Project Reactor before reading this book.This book spends just 2 chapters on Reactor concepts and then jumps to show the reactive support in Spring.The author introduces reactive configuration beans and libraries like Resilience4j as if the reader can make sense of them immediately without going into much detail. I found it difficult to follow such code examples without knowing what each line of code does.
G**O
Great intro to reactive spring
This book has given me all the info I need to get started with reactive Spring. Josh does a great job at explaining the core concepts and making the examples easy to follow and try out.
H**N
Can't believe I paid $46.99 for this.
- of the hundreds of books I own, this one has the weird size and the worst print quality. When I open the book I thought it should be illegal to sell something of this quality. I feel scammed.- now the content, where is the error handling when you handle reactive stream? Is it because there should be no issue?
K**N
Expected a more in depth book
This book is oke for what it is. It explains the basic. But doesn't go in real depth and complex situations which is a shame. This makes it not that useful as I had hoped.
M**S
Expected better
This book is fine, the content covers what it says on the tin but does not blow your mind if you are familiar with webflux.As a book it could be tighter, there is a lot of repition in the text.The code is also really hard to read.Spelling mistakes as well make it feel like more time should have been spent on the editing.
Trustpilot
1 month ago
3 weeks ago