Spring, Hibernate, Data Modeling, REST and TDD book

[Ale Guerrero]

Dear Amritendu De,

first of all, congratulations for your new book. It’s the kind of book I’d like to read because it seems that offers a whole insight of different technologies working together. This approach contrasts with those books which are specifically focused in one particular technology. In my opinion, presenting a book in your way it’s more related to the real work environment, which makes it more interesting and “profitable”.

My question is about how you treat the different topics covered in the book: do you explain briefly each technology and quickly start working with the code? So, it’s completely necessary that the reader codes as well in order to deeply understand the explained concepts. Or by contrast, the lecture is so detailed that it’s possible to read your book just following the given examples without entering any code. In short, the reader needs to show an active or passive attitude?

Best regards.

[Amritendu De]

Actually it depends on the reader. I have chosen an architecture which is widely used nowadays and shown you the design areas you need go through when developing a relational database web application. The entire code is given as a download. So you can keep reading one chapter and browse the whole code for that chapter till you get every bit of it. I think that's the way the reader would be able to appreciate the design concepts and apply the same when designing or developing the applications in a similar architecture or a different architecture. You will find lot of articles on the net covering entity design or a full stack CRUD design. In this book I have covered all the relationships and shown you how to design the entity, business service, data access and presentation tiers. Also the user interface using JSP and JQuery/Ajax/JSON. Once you get the entire concept in this book, you can apply the same in a different technology of your choice. In conventional bottom up design model, we come up with the domain model first and then we develop on top of it using domain driven design.