Spring, Jakarta EE, CDI and Other Pathologies
summary
Argues that frameworks like Spring, Jakarta EE and CDI cause harm by using dependency injection, runtime proxies and AOP that create classes with 18–40 hidden dependencies, conceal state/behavior and make transactions silently fail on internal method calls. Presents real incidents (exam scoring errors, production outages) and recommends avoiding app servers and large frameworks in favor of manual wiring, constructor injection, libraries instead of frameworks and small functional components.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:21Dependency injection basics
- 27:13Spring proxy magic
- 39:19Spring hidden trap
- 44:59Framework vs library
- 48:31Summary
related talks
01h 00mFantastic Frameworks and How to Avoid Them
46mSlaying Sacred Cows: Deconstructing Dependency Injection
44mKeep Spring at Arm's Length!
55mOn Annotations — Time to Stop the Demons
46mThe Case Against Frameworks
49mWhat Every Spring Developer Should Know About Jakarta EE
49mOn @annotations - liberate yourselves from demons
40m6 tips for your JavaEE project be less depressing
