Can you be specific concerning what kind of DI functionality you would expect to see out of the box? I am interested in the topic and would like to know what problem you are trying to solve.
Warning Heavily Opinionated Content: I am not a DW dev. I can't speak for the original design philosophy. What follows is all my personal opinion.I did a bunch of DI implementations in my own DW work several years ago. I did it because DI was "The Right Thing To Do." I used several DI containers including my own. I found all the DW specific implementations bloated and overly complex. An average CRUD-based DW API can be stood up very quickly. I found that DI is just not necessary. I am not a fan of Dependency Injection/Inversion Control. The vast majority of interfaces have a single implementation. The primary exception to this statement is found in mocks for Unit Testing. I'd also like to take this moment to point out that Unit Testing is also "The Right Thing To Do" and It's spirit can be accomplished much easier in most CRUD APIs via Dropwizard + Postgres + Postman but I Digress. We can easily get around this need for alternate implementations via Mocking libraries like Mockito. The second obvious exception are libraries that are designed to be consumed by masses. Now these libraries may be perfect candidates for DI. They may have legitimate, multiple and complex implementations of the same interfaces available at runtime. Many of us never have the opportunity to work on such projects. Our daily work are simple Interfaces and the like that only ever have a single implementation. At best maybe we have a few implementations that can better be served by a simple factory pattern and not a big fat bloated DI Container and all its overhead and related configuration. Again, this is all heavily opinionated. And I'm not a DW designer or dev. Just 2 cents from a guy who tried to wedge DI into his own DW work and found it to be a silly academic exercise at best. On Wed, Jul 29, 2020, 4:54 PM fazeem mohammed <fazeem.m...@gmail.com> wrote: > Hi, > > Is there any specific reason for dropwizard not having out of the box > dependency injection support? > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dropwizard-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dropwizard-dev/2f4a14ae-c5b5-48ca-9296-376d77080932o%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-dev/CAO%3DPp3%2BsuZLGMT5uTAU6Q4X3%3DdJqL3EU0t5NjW4WvG5bZACHxg%40mail.gmail.com.
