File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes OO, Patterns, UML and Refactoring and the fly likes Why DI explanation needs a 352 pages book? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Why DI explanation needs a 352 pages book?" Watch "Why DI explanation needs a 352 pages book?" New topic

Why DI explanation needs a 352 pages book?

Hong Anderson
Ranch Hand

Joined: Jul 05, 2005
Posts: 1936
Hi Dhanji,
I cannot say that I'm an expert in DI. But I've done DI quite a lot using Spring. And for me concept of DI is quite straightforward and easy to understand.
Frameworks like Spring also make it easy to implement DI. So I'm wondering will people who are already familiar with DI get any benefits from reading Dependency Injection book?

SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Dhanji Prasanna
Ranch Hand

Joined: Aug 30, 2009
Posts: 38

That's a fair question. As I said in another post elsewhere on this forum and the welcome thread, this is mainly a software engineering, design patterns and best practices book. The approach to designing applications and architecture is constrained through the lens of DI, using it as a tool to illustrate many common pitfalls and use cases. So really the book is more about architecture and the background is DI and examples using real world libraries and tools.

You may want to look at some of the sample chapters posted on the book's website to get a taste of how things are explained (for example, modularity, concurrency, lifecycle management and so on):


Software Engineer at Google
I agree. Here's the link:
subject: Why DI explanation needs a 352 pages book?
It's not a secret anymore!