<\/div>\n

Merhaba,<\/p>\n

Azure Functions yaz\u0131 serisi<\/a>nin bu onbirinci makalesinde, bir Azure Function \u00fczerinde Dependency Injection<\/a> design pattern’\u0131n\u0131n nas\u0131l kullan\u0131labildi\u011fini inceleyece\u011fiz.<\/p>\n

Ba\u015flarken<\/h4>\n
Visual Studio edit\u00f6r\u00fc arac\u0131l\u0131\u011f\u0131yla bir Http Trigger t\u00fcr\u00fcnden Azure Function olu\u015fturunuz. Ard\u0131ndan Azure function \u00fczerinde dependency injection yapmam\u0131z\u0131 sa\u011flayacak olan Microsoft.Azure.Functions.Extensions<\/a> k\u00fct\u00fcphanesini ilgili projeye y\u00fckleyiniz.
\n $\"Azure$ <\/a><\/p>\n

Kurulum&Entegrasyon<\/h4>\n

Hat\u0131rlarsan\u0131z e\u011fer, klasik Asp.NET Core uygulamalar\u0131nda bir servisin entegrasyonu i\u00e7in ‘Startup.cs’ dosyas\u0131 kullan\u0131lmaktad\u0131r. \u0130\u015fte Azure function uygulamalar\u0131nda da entegrasyon sorumlulu\u011funu \u00fcstlenecek olan ayn\u0131 mahiyette bir dosyaya ihtiyac\u0131m\u0131z vard\u0131r. Bunun i\u00e7in bir .cs uzant\u0131l\u0131 dosya ekleyerek ad\u0131na yine ‘Startup’ diyebilir ve i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi in\u015fa edebilirsiniz.<\/p>\n

\r\nusing Microsoft.Azure.Functions.Extensions.DependencyInjection;\r\nusing Microsoft.Extensions.DependencyInjection;\r\n\r\n[assembly: FunctionsStartup(typeof(ExampleFunction.Startup))]\r\nnamespace ExampleFunction\r\n{\r\n    public class Startup : FunctionsStartup\r\n    {\r\n        public override void Configure(IFunctionsHostBuilder builder)\r\n        {\r\n            builder.Services.AddSingleton<IMyService, MyService>();\r\n        }\r\n    }\r\n}\r\n<\/pre>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere, olu\u015fturulan ‘Startup’ s\u0131n\u0131f\u0131n\u0131n ‘FunctionsStartup’ abstract class’\u0131n\u0131 implement etmesi gerekmekte ve override neticesinde uygulanan ‘Configure’ metodu i\u00e7erisinde dependency injection servisine ilgili enjeksiyonlar ger\u00e7ekle\u015ftirilmektedir. Ayriyetten ‘namespace’e odaklan\u0131rsan\u0131z e\u011fer ‘assembly’ target’\u0131 e\u015fli\u011finde ‘FunctionsStartsup’ attribute’u ile i\u015faretlenerek ‘Startup’ s\u0131n\u0131f\u0131n\u0131n verilmesi ile namespace seviyesinde bir bildirimde bulunulmas\u0131 gerekmektedir.<\/p>\nDependency Injection Kullan\u0131m\u0131<\/h4>\nOlu\u015fturulan ‘Startup’ class’\u0131n\u0131n, namespace seviyesinde ‘FunctionsStartup’ attribute’u ile i\u015faretlenerek bildirilmesi neticesinde art\u0131k ayn\u0131 namespace alt\u0131nda bulunan t\u00fcm functionlar i\u00e7in ilgili entegrasyonun sa\u011fland\u0131\u011f\u0131 anlam\u0131na gelmektedir. Haliyle bu a\u015famadan sonra herhangi bir function’da a\u015fa\u011f\u0131daki gibi bir dependency injection talebinde bulunabilirsiniz.
\n<\/a>
\nBurada dikkat edilirse e\u011fer constructor \u00fczerinden dependency injection neticesinde elde edilen servise eri\u015febilmek i\u00e7in hem class’\u0131n hem de function’\u0131n direkt olarak i\u015faretli geldi\u011fi static keyword\u00fcn\u00fcn kald\u0131r\u0131lmas\u0131 gerekmektedir.<\/p>\n
Function Seviyesinde Dependency Injection Ger\u00e7ekle\u015ftirme<\/h4>\nEntekte edilmi\u015f ba\u011f\u0131ml\u0131l\u0131klar\u0131 her daim constructor \u00fczerinden talep etmek istemeyebilirsiniz. Bazen fonksiyon \u00fczerinden de bu ihtiyac\u0131 gidermek daha efektif olabilecektir. Bunun i\u00e7in bir\u00e7ok yol\/yordam mevcuttur, lakin bu yollar\u0131n bir \u00e7o\u011fu anti-patern olarak de\u011ferlendirilmektedir. \u015eimdi konuyu g\u00fczel bir y\u00f6ntem olan Autofac k\u00fct\u00fcphanesiyle birlikte ele alal\u0131m.<\/p>\nAsp.NET Core uygulamalar\u0131nda kulland\u0131\u011f\u0131m\u0131z ‘FromServices’ attribute’u Azure Function’lar i\u00e7in ge\u00e7erli de\u011fildir…<\/em><\/p><\/blockquote>\nFunction seviyesinde dependency injection talebinde bulunabilmek i\u00e7in AzureFunctions.Autofac<\/a> k\u00fct\u00fcphanesinden faydalanaca\u011f\u0131z.
\n<\/a><\/p>\n
\u0130lk olarak a\u015fa\u011f\u0131daki gibi bir yap\u0131land\u0131rma dosyas\u0131 eklemeniz gerekmektedir.<\/p>\n
\r\n      public class DIConfig\r\n    {\r\n        public DIConfig(string functionName)\r\n        {\r\n            DependencyInjection.Initialize(builder => builder.RegisterType<MyService>().As<IMyService>(), functionName);\r\n        }\r\n    }\r\n<\/pre>\nArd\u0131ndan a\u015fa\u011f\u0131daki gibi function seviyesinde ilgili servisi enjekte edebilir, talebinizi yapabilirsiniz.<\/p>\n\r\n    [DependencyInjectionConfig(typeof(DIConfig))]\r\n    static public class Function1\r\n    {\r\n        [FunctionName("Function1")]\r\n        static public async Task<IActionResult> Run(\r\n            [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] HttpRequest req,\r\n            ILogger log, [Inject] IMyService myService)\r\n        {\r\n.\r\n.\r\n.\r\n<\/pre>\nBurada ilgili function’\u0131 ‘DependencyInjectionConfig’ attribute’u ile i\u015faretleyerek yap\u0131land\u0131rma dosyas\u0131n\u0131 bildirmeniz ve ard\u0131ndan ‘Inject’ attribute’u ile servisi talep etmeniz yeterli olacakt\u0131r.<\/p>\nOptions Pattern Kullan\u0131m\u0131<\/h4>\nOptions pattern<\/a>, Asp.NET Core mimarisinde ‘appsettings.json’ dosyas\u0131ndaki verileri yap\u0131land\u0131r\u0131lm\u0131\u015f bir \u015fekilde nesnel olarak bizlere sunan bir tasar\u0131m desenidir. Benzer mant\u0131kla Azure function’da ise ‘local.settings.json’ dosyas\u0131ndaki verileri yap\u0131land\u0131rmam\u0131z\u0131 sa\u011flamakta ve b\u00f6ylece s\u00fcrece efektiflik kazand\u0131rmaktad\u0131r.<\/p>\n
Tasar\u0131m\u0131n modellenmesi \u015fu \u015fekildedir;
\n‘local.settings.json’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi veri tan\u0131mlan\u0131r.<\/p>\n
\r\n{\r\n  "IsEncrypted": false,\r\n  "Values": {\r\n    "AzureWebJobsStorage": "UseDevelopmentStorage=true",\r\n    "FUNCTIONS_WORKER_RUNTIME": "dotnet",\r\n    "Datas": {\r\n      "MyData": "Sende ba\u015f\u0131n\u0131 al\u0131p gitme ne olur..."\r\n    }\r\n  }\r\n}\r\n<\/pre>\nArd\u0131ndan bu veriye kar\u015f\u0131l\u0131k entity olu\u015fturulur.<\/p>\n
\r\n    public class Datas\r\n    {\r\n        public string MyData { get; set; }\r\n    }\r\n<\/pre>\nVe ‘FunctionsStartup’ abstract class’\u0131ndan t\u00fcreyen ve bizimde ‘Startup’ ismini verdi\u011fimiz class i\u00e7erisinde a\u015fa\u011f\u0131daki gibi ilgili veriler options pattern ile service provider’\u0131na ilgili entity ile e\u015fle\u015ftirilerek dahil edilir.<\/p>\n
\r\n    public class Startup : FunctionsStartup\r\n    {\r\n        public override void Configure(IFunctionsHostBuilder builder)\r\n        {\r\n            builder.Services.AddSingleton<IMyService, MyService>();\r\n            builder.Services.AddOptions<Datas>()\r\n                .Configure<IConfiguration>((datas, configuration) =>\r\n            {\r\n                configuration.GetSection("Datas").Bind(datas);\r\n            });\r\n        }\r\n    }\r\n<\/pre>\nBurada ‘Bind’ operasyonunun i\u015flevine de\u011finirsek e\u011fer; ‘Bind’, verilen section i\u00e7erisindeki de\u011ferleri entity’de uygun property kar\u015f\u0131l\u0131klar\u0131na ba\u011flayan bir fonksiyondur.<\/p>\n
Nihai olarak ilgili data ‘IOptions’ interface’i ile a\u015fa\u011f\u0131daki gibi dependency injection ile talep edilir.<\/p>\n
\r\n    public class Function1\r\n    {\r\n        readonly Datas _datas;\r\n        public Function1(IOptions<Datas> datas)\r\n        {\r\n            _datas = datas.Value;\r\n        }\r\n.\r\n.\r\n.\r\n<\/pre>\n\u0130\u015fte Azure Function \u00fczerinde bu \u015fekilde dependency injection ger\u00e7ekle\u015ftirilmektedir \ud83d\ude42<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…
\n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, Azure Functions yaz\u0131 serisinin bu onbirinci makalesinde, bir Azure Function \u00fczerinde Dependency Injection design pattern’\u0131n\u0131n nas\u0131l kullan\u0131labildi\u011fini inceleyece\u011fiz. Ba\u015flarken Visual Studio edit\u00f6r\u00fc arac\u0131l\u0131\u011f\u0131yla bir Http Trigger t\u00fcr\u00fcnden Azure Function olu\u015fturunuz. Ard\u0131ndan Azure function...<\/p>\n","protected":false},"author":1,"featured_media":17011,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3121],"tags":[3686,3729,3731,946,3730],"class_list":["post-17341","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","tag-azure-function","tag-azure-function-dependency-injection","tag-azurefunctions-autofac","tag-dependency-injection","tag-microsoft-azure-functions-extensions"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=17341"}],"version-history":[{"count":18,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17341\/revisions"}],"predecessor-version":[{"id":17362,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17341\/revisions\/17362"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/17011"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=17341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=17341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=17341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}