https://www.itsnothing.de/tags/backend/Recent content in Backend on It's NothingHugoenThu, 05 Feb 2026 10:00:00 +0200https://www.itsnothing.de/post/from-service-locator-to-composition-root/Thu, 05 Feb 2026 10:00:00 +0200https://www.itsnothing.de/post/from-service-locator-to-composition-root/<p>After working for a while on the Node.js/Express backend for <strong>MatchPicks</strong>, I ran into a classic architectural challenge: as the application expanded to over 30 services and repositories, how could I wire them together without creating a tangled web of imports, hiding dependencies, or getting stuck in circular dependency loops?</p> <p>From earlier experience I knew a Unity/Zenject codebase for dependency injection (DI). While Zenject is powerful, it eventually felt like a massive, hard-to-trace &ldquo;black box&rdquo; where it was difficult to see how dependencies were resolved at runtime. When deciding how to approach this for the Node.js and TypeScript stack, I wanted to avoid bringing in heavy DI container libraries that add complexity and overhead. I also wanted to focus on building the app first without adding a new heavy framework like NestJS to my learning curve. Once I have built this system a few times manually and have more experience with the architectural patterns, I might consider adopting them, but for now, less is more.</p>