Kepiye carane dependency injection gumana ing .NET?

Question

Accepted Answer

**Dependency Injection (DI)** wis dibangun ing .NET modern — framework kasebut kalebu sawijining DI container sing sacara otomatis nggawe kelas lan **nyuntiki dependensi-dependensine**. Sampeyan ngdaftar layanan (memetaake interface menyang implementasi) lan container ngresolusi iki, ngamungkinake kode sing renggang-gandhul, lan mudah diuji. Iki dadi fondasi kanggo ASP.NET Core. ## Ngdaftar layanan ```csharp // in Program.cs — register services with a LIFETIME builder.Services.AddScoped(); // interface → implementation builder.Services.AddSingleton(); builder.Services.AddTransient(); ``` Sampeyan ngdaftar saben pemetaan layanan sawijining **interface menyang implementasi** karo umur. Banjur apa wae sing gumantung ing interface bakal oleh implementasi sing wis didaftar. ## Constructor injection (pola standar) ```csharp public class UserService { private readonly IUserRepository _repo; private readonly IEmailSender _email; // dependencies are declared in the constructor — the container INJECTS them automatically public UserService(IUserRepository repo, IEmailSender email) { _repo = repo; _email = email; } } // you never `new UserService(...)` manually — the container builds it, resolving the chain ``` Dependensi dinyatakake minangka parameter konstruktor (diapit minangka interface); container nggawe kelas lan nyuntiki implementasi sing didaftar, ngresolusi kabeh grafik dependensi kanthi otomatis. ## Umur layanan (penting kanggo milih kanthi bener) ```text Singleton → ONE instance for the entire app lifetime (shared; must be thread-safe) Scoped → one instance PER request (the common default for web — e.g. DbContext) Transient → a NEW instance every time it's requested (lightweight, stateless services) → Choosing wrong (e.g. a singleton capturing a scoped DbContext) causes subtle bugs. ``` ## Keuntungan: pasangan renggang lan testabilitas ```csharp // because UserService depends on INTERFACES, you can inject MOCKS in tests var service = new UserService(mockRepo, mockEmail); // no real DB/email needed ``` ## Apa iki penting Dependency injection iku dadi fondasi .NET modern — iku **dibangun menyang framework** lan iku tulang punggung ASP.NET Core, dadi paham iki iku penting kanggo aplikasi pangembangan C# modern apa wae. Container DI bawaan framework kasebut sacara otomatis nggawe kelas lan nyuntiki dependensi-dependensine (ngresolusi kabeh grafik dependensi), dadi sampeyan ngdaftar layanan lan biarake container nyambung kabeh bebarengan tinimbang nglelun instantiate dependensi. Keuntungan inti iku signifikan lan utama kanggo apa DI dikakake: **pasangan renggang** (gumantung ing interface tinimbang kelas konkret, dadi implementasi bisa ditukar) lan luwih-luwih **testabilitas** (nyuntiki implementasi mock ing tes tinimbang dependensi nyata kaya basis data utawa layanan email — nggawe uji unit sing lengkap praktis). Nalusuk kepiye carane ngdaftar layanan (memetaake interface menyang implementasi), constructor injection (pola standar), lan — penting — **umur layanan** (`Singleton`, `Scoped`, `Transient`) iku penting: milih umur sing salah nyebabake kumbara sing halus, susah-debugging (contone singleton sing ngandhung `DbContext` scoped, utawa masalah thread-safety karo singleton sing dibagi), dadi nalusuk kapan saben umur utawa (Scoped saben-layar kanggo bakal kaya DbContext, Singleton kanggo layanan sing renggang stateless, Transient kanggo bakal enteng) iku kritis. // (amarga DI dibangun menyang .NET, dadi bawah-bangun ASP.NET Core, lan dadi kunci kanggo nulis kode sing renggang-gandhul, testabel, nalusuk iki — container, constructor injection, desain berbasis-interface, lan luwih-luwih umur layanan — iku penting, sering-ditrapake panggetosan senior kanggo nggawe aplikasi C# modern sing terawat, testabel, lan topik wawancara umum.