Win a copy of Rust Web Development this week in the Other Languages forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Why DI explanation needs a 352 pages book?

 
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
author
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

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): http://manning.com/prasanna

Dhanji.
 
reply
    Bookmark Topic Watch Topic
  • New Topic