architecture – How much is too much Dependency Injection? – Software Engineering Stack Exchange
Posted by jpluimers on 2019/04/02
Mark Seeman posted a great answer with insights into how to architect applications: [WayBack] architecture – How much is too much Dependency Injection? – Software Engineering Stack Exchange
Some topics covered:
- small code bases
- pure DI over DI container
- cases for both coarse and fine-grained DI
- favour functional programming over OOP
- both functional and DI ports and adapters
It links to a ton of other good reads for a quiet long weekend as well:
- [WayBack] When to use a DI Container
- [WayBack] Code rant: The Configuration Complexity Clock
- [Archive.is] Design Patterns: Elements of Reusable Object-Oriented Software 1st Edition by Erich Gamma (Author), Richard Helm (Author), Ralph Johnson (Author), John Vlissides (Author), Grady Booch (Foreword)
- [Archive.is] Dependency Injection in .NET 1st Edition by Mark Seemann (Author)
- [Archive.is] Integration Tests Are a Scam
- [WayBack] Introducing BDD | Dan North & Associates (Behaviour Driven Development)
- [WayBack] Test-induced design damage (DHH)
- [WayBack] Functional design is intrinsically testable
- [WayBack] SOLID: the next step is Functional
- [WayBack] Functional architecture is Ports and Adapters
- [WayBack] Layers, Onions, Ports, Adapters: it’s all the same
- [WayBack] Dependency rejection
- [WayBack] Partial application is dependency injection
- [WayBack] Feedback mechanisms and tradeoffs
–jeroen
via: [WayBack] Favour Pure DI – Linas Naginionis – Google+
The Wiert Corner - irregular stream of stuff 
Leave a comment