Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Introducing Spring Framework: A Primer 1st ed. Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
About the Author
Felipe Gutierrez is an expert developer, engineer working at EMC-Pivotal, the makers and backers of the Spring Framework and platform. He is an active, expert Spring and enterprise Java applications developer
Browse award-winning titles. See more
Top customer reviews
I prefer a top down book and hence this book is not for me. If you're a very hands on kind of person and learn by doing, this might work for you. However, the lack of a solid theoretical foundation cannot be overlooked.
I have skimmed through the book for a few hours and hence this is not a detailed review.
This is what the book provides and does not provide.
The entire book seems to build an application based on Spring. The book does a good job on being up to date with technology and uses Spring 4 along with Spring Boot as well as gradle ( a build tool based on Maven) and groovy as well as MongoDB, BeanShell and a bit of Ruby. No prior knowledge of these is needed and the book shows you just what you need to know so you can keep pace.
So the first chapter gets you to write the traditional "Hello world" and then takes off after that.
The entire book spends time in developing a document repository and includes the standard CRUD methods for handling a repository.
The entire code on how to design and build this Spring based application is given in the book (and can be downloaded as well) so if the reader faithfully follows all the steps, he will have a functioning application.
So by following the text and coding, the reader can get to understand the one application that this entire book puts together.
The reasons the book doesn't work for ME:
1. I would like a strong theoretical foundation before getting into details.
2. There are too many other technologies (Ruby, groovy, gradle, MongoDB etc). This could be good or bad, since the Spring framework is so extensive. I would have preferred a book that sticks to the minimally needed technologies to show what Spring can support.
3. I would prefer small examples about each topic instead of one gargantuan application over the entire book. The downside of building a big application one step at a time, chapter over chapter, is that it makes it difficult to jump to a specific topic to get to know it.