\r\napiVersion: dapr.io\/v1alpha1\r\nkind: Configuration\r\nmetadata:\r\n  name: daprsystem\r\n  namespace: dapr-system\r\nspec:\r\n  mtls:\r\n    enabled: true\r\n    workloadCertTTL: "24h"\r\n    allowedClockSkew: "15m"\r\n<\/pre>\n<\/div>\nDapr Observability\/\u0130zleme\/G\u00f6zlenebilirlik<\/h4>\n<\/a>Bir uygulaman\u0131n, en hayati noktalar\u0131ndan birisi \u00e7al\u0131\u015fma zaman\u0131nda nas\u0131l davrand\u0131\u011f\u0131n\u0131 izleyebilmektir. \u00d6zellikle uygulama \u00e7a\u011fr\u0131lar\u0131n\u0131n g\u00f6zlenebilmesi, performans durumunun \u00f6l\u00e7\u00fcmlenebilmesi yahut meydana gelen beklenmeyen problemlerin an\u0131nda \u00e7\u00f6z\u00fclebilmesi, hatalar\u0131n ay\u0131klanabilmesi veya olu\u015facak darbo\u011fazlar\u0131n(bottlenecks) anla\u015f\u0131labilmesi i\u00e7in g\u00f6zlenebilirlik olduk\u00e7a \u00f6nem arz etmektedir. Evet, biliyorsunuz ki bu herhangi bir sistem i\u00e7in zordur lakin bir istek neticesinde k\u00fc\u00e7\u00fck mikro servisler aras\u0131nda ak\u0131\u015f silsilesinin s\u00f6z konusu oldu\u011fu distributed bir sistem i\u00e7in daha da zordur.<\/p>\n
Bir uygulamayla ilgili bellek t\u00fcketimi, CPU kullan\u0131m\u0131 vs. gibi temel seviyedeki metrikler rahatl\u0131kla al\u0131nabiliyor olsa da as\u0131l \u00f6nemli olan bir \u00e7a\u011fr\u0131 s\u00fcrecinde uygulaman\u0131n davran\u0131\u015f\u0131na dair anlaml\u0131 bilgilerin toplanmas\u0131d\u0131r. Ve bu da geli\u015ftirici a\u00e7\u0131s\u0131ndan ihtiya\u00e7 noktalar\u0131na kodsal m\u00fcdahalelerde bulunulmas\u0131 gerekti\u011fi anlam\u0131na gelmektedir. \u00c7o\u011fu zaman toplanan bu metrikler t\u00fcrl\u00fc ara\u00e7larla g\u00f6rselle\u015ftirilerek monit\u00f6r edilirler.<\/p>\n
\u015eimdi mant\u0131ken olaya bakt\u0131\u011f\u0131m\u0131zda uygulamalar\u0131n business logic’inin bir par\u00e7as\u0131 olmayan bu \u00e7al\u0131\u015fmalar\u0131 ger\u00e7ekle\u015ftirmek geli\u015ftiriciler a\u00e7\u0131s\u0131ndan ciddi bir y\u00fckt\u00fcr ve hatta bu y\u00fck bu ara\u00e7lar\u0131n SDK’lerini kullanma, API’lerini anlama vs. gibi durumlar\u0131 gerektirdik\u00e7e daha da ciddi hale gelebilmektedir.<\/p>\n
Bir \u00e7a\u011fr\u0131m sonucu mikro servisler aras\u0131nda ak\u0131\u015f\u0131n ba\u015flad\u0131\u011f\u0131 durumlarda Dapr bu distributed senaryolarda g\u00f6zlenebilirlik a\u00e7\u0131s\u0131ndan avantaj sa\u011flamakta ve yayg\u0131n olarak kabul g\u00f6ren Open Telemetry (OTEL) veya Zipkin protokolleri ile metrikleri toplayabildi\u011fi i\u00e7in bir\u00e7ok g\u00f6rselle\u015ftirme arac\u0131yla kolayca entegre edilebilmektedir.<\/p>\n
Ayr\u0131ca Dapr, kullan\u0131c\u0131lar\u0131n sorunlar\u0131n\u0131 tan\u0131mlamas\u0131na ve hata ay\u0131klama yapmas\u0131na yard\u0131mc\u0131 olmak i\u00e7in i\u00e7erisinde uyar\u0131, hata ve bilgi mesajlar\u0131 bar\u0131nd\u0131ran log<\/strong>‘larla birlikte, sistemin durumunu kontrol edebilmek i\u00e7in bir Health Check<\/strong> mekanizmas\u0131 da bar\u0131nd\u0131rmaktad\u0131r.<\/p>\n
Dapr Nas\u0131l Y\u00fcklenir?<\/h4>\nDapr’\u0131 kullanabilmek i\u00e7in \u00f6ncelikle Dapr CLI’\u0131 bilgisayar\u0131n\u0131za kurman\u0131z gerekmektedir. Bunun i\u00e7in \u015fu adresteki<\/a> \u00f6nergeleri s\u0131ras\u0131yla takip etmeniz yeterlidir.<\/p>\n
Powershell \u00fczerinden Dapr’\u0131 y\u00fckleyiniz.
\n<\/a>Ard\u0131ndan dapr<\/code> komutuyla y\u00fcklenip, y\u00fcklenmedi\u011fini do\u011frulay\u0131n\u0131z.<\/a>Self-hosted modda Dapr’\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n\u0131z.<\/a>Ve Dapr container’lar\u0131n\u0131 listeleyip nihai kontrolde bulununuz.<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Dapr temel olarak ‘Redis’, ‘Openzipkin\/Zipkin’ ve ‘Daprio\/Dapr’ olmak \u00fczere \u00fc\u00e7 container ile ba\u015flang\u0131\u00e7 sa\u011flamaktad\u0131r. ‘Openzipkin\/Zipkin’ container’\u0131 ile metrikleri toplarken, ‘Redis’ ile state-store ve messaging operasyonlar\u0131n\u0131 y\u00fcr\u00fctmektedir. Ayr\u0131ca bu component’lerin Windows i\u015fletim sistemlerinde C:\\Users\\[name]\\.dapr<\/code> klas\u00f6r\u00fc alt\u0131nda tan\u0131mland\u0131klar\u0131n\u0131 bilmenizde fayda vard\u0131r. (Linux’da ise $HOME\/.dapr<\/code> dizininde tan\u0131mlanmaktad\u0131r)<\/p>\n
Dapr \u0130le Basit D\u00fczeyde Servislerin Haberle\u015fmesi<\/h4>\n\u015eimdi ise son olarak Dapr ile basit seviyede iki servisin haberle\u015fmesini inceleyerek i\u00e7eri\u011fimizi nihayete erdirelim istiyorum. Bunun i\u00e7in bo\u015f bir solution’da ‘Dapr.Basic.ServiceA’ ve ‘Dapr.Basic.ServiceB’ isimlerinde olmak \u00fczere iki Asp.NET Core API uygulamas\u0131n\u0131 a\u015fa\u011f\u0131daki gibi olu\u015fturunuz.
\n<\/a>
\n\u015eimdi bu servisler aras\u0131nda publish edilmi\u015f event \u00fczerinden haberle\u015fmeyi sa\u011flayabilmek i\u00e7in herhangi bir k\u00fct\u00fcphane, teknoloji vs. d\u00fc\u015f\u00fcnmeksizin direkt olarak Dapr ile bu i\u015flemi ger\u00e7ekle\u015ftirebilece\u011fiz.<\/p>\n
Burada ‘Dapr.Basic.ServiceA’ servisi ile event publish edilirken ‘Dapr.Basic.ServiceB’ servisi ile de bu event’i dinleyecek ve gerekli i\u015flemleri ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n
Tabi bu i\u015flemi SDK<\/strong> kullanarak yahut HTTP<\/strong> \u00fczerinden istekte bulunarak iki farkl\u0131 \u015fekilde ger\u00e7ekle\u015ftirebiliriz. \u015eimdi gelin her iki y\u00f6ntemle de nas\u0131l \u00e7al\u0131\u015fma sa\u011flayabiliriz s\u0131ras\u0131yla inceleyelim;<\/p>\n
\nSDK<\/strong>
\nSDK \u00fczerinden geli\u015ftirmeyi sa\u011flayabilmek i\u00e7in event publish edecek olan ‘Dapr.Basic.ServiceA’ isimli servise Dapr.Client<\/a> ve Dapr.AspNetCore<\/a> library’lerini, t\u00fcketici olan ‘Dapr.Basic.ServiceB’ isimli servise ise sadece Dapr.AspNetCore<\/a> library’sini y\u00fckleyiniz.<\/p>\nArd\u0131ndan ‘Dapr.Basic.ServiceA’da a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftiriniz.<\/p>\n\n\r\nusing Dapr.Client;\r\nusing Shared.Events;\r\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\nbuilder.Services.AddDaprClient();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/send-event\/{eventText}", async (string eventText, DaprClient client) =>\r\n{\r\n    await client.PublishEventAsync(pubsubName: "pubsub", topicName: "example.event", new Event(eventText));\r\n    Console.WriteLine(eventText);\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.MapControllers();\r\napp.Run("https:\/\/localhost:1000");\r\n<\/pre>\n<\/div>\nYukar\u0131daki kod blo\u011funda, 8.<\/strong> sat\u0131rda ‘AddDaprClient’ servisi uygulamaya dahil edilmekte ve 12<\/strong> ile 16.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise \/send-event\/{eventText}<\/code> endpoint’i i\u00e7erisinde ‘Event’ t\u00fcr\u00fcnden bir event publish edilmektedir. Burada ‘pubsubName’e C:\\Users\\[name]\\.dapr<\/code> dizininde bulunan ‘components’ klas\u00f6r\u00fc i\u00e7erisindeki ‘pubsub.yaml’ dosyas\u0131n\u0131n ‘metadata:name’ bilgisinin verildi\u011fine dikkatinizi \u00e7ekerim.<\/a>‘Dapr.Basic.ServiceB’ servisinde ise a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftiriniz.<\/p>\n
\n\r\nusing Dapr;\r\nusing Shared.Events;\r\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers().AddDapr();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapPost("\/get-event", [Topic("pubsub", "example.event")] (Event @event) =>\r\n{\r\n    Console.WriteLine(@event.Text);\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.UseCloudEvents();\r\napp.MapControllers();\r\napp.MapSubscribeHandler();\r\napp.Run("https:\/\/localhost:2000");\r\n<\/pre>\n<\/div>\nBurada da 6.<\/strong> sat\u0131rda Dapr ‘AddDapr’ extension’\u0131 sayesinde MVC pipeline’\u0131na dahil edilmektedir. 17.<\/strong> ve 19.<\/strong> sat\u0131rlarda ise s\u0131ras\u0131yla ‘UseCloudEvents’ ve ‘MapSubscribeHandler’ middleware’leri \u00e7a\u011fr\u0131lmaktad\u0131r. Dapr, publish edilen event’lar\u0131 CloudEvent format\u0131na \u00e7evirdi\u011fi i\u00e7in ayn\u0131 \u015fekilde event’i ilgili t\u00fcre d\u00f6n\u00fc\u015ft\u00fcrebilmek amac\u0131yla ‘UseCloudEvents’ middleware’i kullan\u0131lmaktad\u0131r. ‘MapSubscribeHandler’ middleware’i ise 11.<\/strong> sat\u0131rda yay\u0131nlanm\u0131\u015f olan event’i dinleyebilmek i\u00e7in kulland\u0131\u011f\u0131m\u0131z Topic<\/code> attribute’unu i\u015flevsel hale getirebilmek i\u00e7in \u00e7a\u011fr\u0131lmaktad\u0131r.<\/p>\nBu i\u015flemlerden sonra a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde Dapr \u00fczerinden servisleri aya\u011fa kald\u0131r\u0131n\u0131z ve ekran g\u00f6r\u00fcnt\u00fcs\u00fcndeki gibi teste tabi tutunuz.
\ndapr run --app-id servicea --app-ssl<\/span> --app-port 1000 -- dotnet run<\/strong><\/code>
\ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 -- dotnet run<\/strong><\/code>
\n(SSL connection kullanan uygulamalarda –app-ssl<\/span> parametresi ile Dapr’a g\u00fcvenli olmayan bir SSL ba\u011flant\u0131s\u0131  \u00fczerinden uygulamalar\u0131 aya\u011fa kald\u0131rmas\u0131 gerekti\u011fini s\u00f6ylemi\u015f oluyoruz.)<\/span>
\n<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Dapr sayesinde publish etti\u011fimiz event herhangi bir harici k\u00fct\u00fcphaneye ihtiya\u00e7 duymaks\u0131z\u0131n direkt subscribe olan bir consumer taraf\u0131ndan ba\u015far\u0131yla i\u015flenmektedir.\n<\/li>\n
HTTP<\/strong>
\nBenzer \u015fekilde iki servis aras\u0131ndaki haberle\u015fmeyi HTTP \u00fczerinden sa\u011flamak istiyorsan\u0131z burada birazc\u0131k farkl\u0131 davran\u0131\u015f sergilemeniz gerekmektedir.<\/p>\n‘Dapr.Basic.ServiceA’ servisinde a\u015fa\u011f\u0131daki gibi bir \u00e7al\u0131\u015fma ger\u00e7ekle\u015ftiriniz;<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\nbuilder.Services.AddDaprClient();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/send-event\/{eventText}", async (string eventText, DaprClient client) =>\r\n{\r\n    HttpClient httpClient = new();\r\n\r\n    Event @event = new(eventText);\r\n    string jsonData = JsonSerializer.Serialize(@event, options: new JsonSerializerOptions() { PropertyNamingPolicy = JsonNamingPolicy.CamelCase });\r\n\r\n    httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue(MediaTypeNames.Application.Json));\r\n    StringContent body = new(jsonData, Encoding.UTF8, MediaTypeNames.Application.Json);\r\n    var response = await httpClient.PostAsync($"http:\/\/localhost:2001\/v1.0\/publish\/pubsub\/example.event", body);\r\n\r\n    return Results.Ok($"Status Code : {response.StatusCode} | Event : {@event.Text}\\"");\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.MapControllers();\r\napp.Run("https:\/\/localhost:1000");\r\n<\/pre>\n<\/div>\nYukar\u0131daki kod blo\u011funu incelerseniz e\u011fer 11<\/strong> ile 20.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda HTTP protokol\u00fc \u00fczerinden bir event yay\u0131nlama i\u015flemi ger\u00e7ekle\u015ftirilmektedir. Bu i\u015flem i\u00e7in 18.<\/strong> sat\u0131rda http:\/\/localhost:2001\/v1.0\/publish\/pubsub\/example.event<\/code> adresine POST iste\u011fi g\u00f6nderilmektedir. Bu adreste nerden \u00e7\u0131kt\u0131 hoca la?<\/strong> diye sordu\u011funuzu duyar gibiyim… Tabi ki de kafam\u0131za g\u00f6re bir adres yaz\u0131p istekte bulunmad\u0131\u011f\u0131m\u0131z a\u015fikar. Dapr, HTTP \u00fczerinden ger\u00e7ekle\u015ftirilecek pub\/sub i\u015flemleri i\u00e7in a\u015fa\u011f\u0131daki formatta bir url’e istek g\u00f6ndermemiz gerekti\u011fini bizlere s\u00f6ylemektedir.
\nhttp:\/\/localhost:<daprPort><\/span>\/v1.0\/publish\/<pubsubname><\/span>\/<topic><\/span>[?<metadata>]<\/strong><\/code>
\nBu adres \u015femas\u0131ndaki <daprPort><\/span>, haberle\u015fme sa\u011flanmak istenen servisin birazdan nas\u0131l tan\u0131mlanabilece\u011fini g\u00f6rece\u011fimiz Dapr HTTP Port’una kar\u015f\u0131l\u0131k gelmektedir. <pubsubname><\/span>, hangi pub\/sub component’i kullan\u0131l\u0131yorsa onun ad\u0131na kar\u015f\u0131l\u0131k gelmektedir. Ve son olarak <topic><\/span> ise event’in publish edildi\u011fi topic ad\u0131na kar\u015f\u0131l\u0131k gelmektedir.<\/p>\n
HTTP protokol\u00fc \u00fczerinden \u00e7al\u0131\u015fma s\u00fcrecinde, yukar\u0131daki gibi bir event publish edildi\u011fi taktirde; Dapr, consumer g\u00f6revi g\u00f6ren serviste
\nhttp:\/\/localhost:<appPort>\/dapr\/subscribe<\/span><\/code> endpoint’ini GET request’i ile tetiklemektedir. B\u00f6ylece ilgili serviste bir event’in publish edildi\u011fine dair bilgilenilmi\u015f olunacakt\u0131r. \u015eimdi bu mant\u0131k do\u011frultusunda ‘Dapr.Basic.ServiceB’ servisini ise a\u015fa\u011f\u0131daki gibi geli\u015ftiriniz.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/dapr\/subscribe", () =>\r\n{\r\n    return Results.Json(new[] {new\r\n    {\r\n        PubSubName = "pubsub",\r\n        Topic = "example.event",\r\n        Route = "\/get-event"\r\n    } });\r\n});\r\n\r\napp.MapPost("\/get-event", (DaprData<Event> @event) =>\r\n{\r\n    Console.WriteLine(@event.Data.Text);\r\n});\r\n\r\napp.Run("https:\/\/localhost:2000");\r\nrecord DaprData<T>(T Data);\r\n<\/pre>\n<\/div>\nYukar\u0131daki \u00e7al\u0131\u015fmaya dikkat ederseniz, 4<\/strong> ile 12.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda herhangi bir event yay\u0131nland\u0131\u011f\u0131 taktirde Dapr taraf\u0131ndan tetiklenecek olan \/dapr\/subscribe<\/code> endpoint’ine kar\u015f\u0131l\u0131k bir minimal api tan\u0131mlanm\u0131\u015ft\u0131r. Bu action i\u00e7erisinde, JSON olarak ‘PubSubName’, ‘Topic’ ve ‘Route’ bilgilerini bar\u0131nd\u0131ran bir obje, \u00fcretilmi\u015f bir koleksiyona dahil olacak \u015fekilde geriye return edilmektedir. Burada ‘Route’ta tan\u0131ml\u0131 olan \/get-event<\/code> de\u011feri sayesinde publish edilmi\u015f olan event’\u0131n hangi endpoint i\u00e7erisinde handle edilece\u011fi ifade edilmektedir. Dolay\u0131s\u0131yla bu a\u015famadan sonra 14<\/strong> ile 17.<\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki action tetiklenecektir.<\/p>\n
\u0130lgili action’a g\u00f6z atarsan\u0131z e\u011fer 20.<\/strong> sat\u0131rda tan\u0131mlanm\u0131\u015f olan ‘DaprData<T>’ record t\u00fcr\u00fcnden bir parametre almaktad\u0131r. Burada T yerine ‘Event’ yaz\u0131larak gelen de\u011fer tam olarak elde edilmi\u015f olmaktad\u0131r. Bu tarz bir \u00e7al\u0131\u015fman\u0131n nedenini sorarsan\u0131z e\u011fer bu metota gelen verinin yap\u0131s\u0131n\u0131n a\u015fa\u011f\u0131daki gibi olmas\u0131d\u0131r.<\/p>\n\n\r\n{\r\n  "data": {\r\n    "text": "nevin"\r\n  },\r\n  "datacontenttype": "application\/json; charset=utf-8",\r\n  "id": "dfd6a336-b99f-4cc7-a384-b8a31ca4f791",\r\n  "pubsubname": "pubsub",\r\n  "source": "serviceb",\r\n  "specversion": "1.0",\r\n  "time": "2022-11-14T01:26:03+03:00",\r\n  "topic": "example.event",\r\n  "traceid": "00-97ecee8642fbcf8549f43db6f9d7074c-4b255f63bafe0b31-01",\r\n  "traceparent": "00-97ecee8642fbcf8549f43db6f9d7074c-4b255f63bafe0b31-01",\r\n  "tracestate": "",\r\n  "type": "com.dapr.event.sent"\r\n}\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bir\u00e7ok bilgi tek bir json datas\u0131 i\u00e7erisinde k\u00fcm\u00fclatif olarak gelmektedir. Haliyle burada publish edilmi\u015f event’i temsil edebilmek i\u00e7in bu json datas\u0131n\u0131n i\u00e7erisindeki ‘data’ parametresini alabilecek bir \u00e7al\u0131\u015fma yapmam\u0131z gerekecekti. Bunun i\u00e7in generic bir record ile gayet efektif bir \u00e7\u00f6z\u00fcm getirebildik kanaatindeyim \ud83d\ude42 Action tetiklendi\u011finde deserialize s\u00fcreci ba\u015flat\u0131lacak ve ‘DaprData<T>’ t\u00fcr\u00fcne g\u00f6re bir \u00e7\u0131kt\u0131 al\u0131nacakt\u0131r. Ee ‘DaprData<T>’ t\u00fcr\u00fc de i\u00e7erisinde ‘Data’ parametresi ald\u0131\u011f\u0131 i\u00e7in ilgili json i\u00e7erisindeki ‘data’ bu parametreyle e\u015fle\u015fecek ve bizlere direkt T parametresine verilen t\u00fcrde de\u011feri getirecektir.<\/p>\n
\u0130\u015fte bu kadar…<\/p>\nSon olarak a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde uygulamalar\u0131 Dapr \u00fczerinden aya\u011fa kald\u0131r\u0131p, testlerinizi ger\u00e7ekle\u015ftiriniz.
\ndapr run --app-id servicea --app-ssl<\/span> --app-port 1000 --dapr-http-port 1001<\/span> -- dotnet run<\/strong><\/code>
\ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 --dapr-http-port 2001<\/span> -- dotnet run<\/strong><\/code>
\n(–dapr-http-port …<\/span> parametresi aya\u011fa kald\u0131r\u0131lan uygulaman\u0131n Dapr’da HTTP \u00fczerinden eri\u015filebilen port’unu ifade etmektedir. Yukar\u0131larda bahsi ge\u00e7en <daprPort><\/span> alan\u0131na ilgili servisin –dapr-http-port bilgisi verilmelidir.)<\/span>
\n<\/a>Evet, b\u00f6ylece yine herhangi bir k\u00fct\u00fcphane kullanmaks\u0131z\u0131n Dapr ile HTTP \u00fczerinden iki servisin haberle\u015fmesini sa\u011flayabilmi\u015f bulunuyoruz.\n<\/li>\n<\/ul>\n
Component De\u011fi\u015ftirme<\/h4>\nDapr’\u0131n component’leri bar\u0131nd\u0131rd\u0131\u011f\u0131 default path’inin Windows i\u00e7in C:\\Users\\[name]\\.dapr<\/code>, Linux i\u00e7in ise $HOME\/.dapr<\/code> oldu\u011funu daha \u00f6nceki sat\u0131rlar\u0131m\u0131zda bildirmi\u015ftik.<\/p>\nBir component’i de\u011fi\u015ftirmek istedi\u011fimizde tek yap\u0131lmas\u0131 gereken ilgili YAML dosyas\u0131n\u0131n istenilen component i\u00e7eri\u011fi ile de\u011fi\u015ftirilmesidir. Misal olarak, i\u00e7eri\u011fimiz s\u00fcrecinde default olarak gelen ve pub\/sub componenti olarak kullanm\u0131\u015f oldu\u011fumuz Redis’i RabbitMQ component’i ile de\u011fi\u015ftirmek istiyorsak e\u011fer yapmam\u0131z gereken \u015furadan<\/a> RabbitMQ component’ine ait format\u0131 al\u0131p ilgili dizindeki ‘pubsub.yaml’ dosyas\u0131 i\u00e7erisindekilerle de\u011fi\u015ftirmektir.<\/p>\n
\n\r\napiVersion: dapr.io\/v1alpha1\r\nkind: Component\r\nmetadata:\r\n  name: rabbitmq-pubsub\r\nspec:\r\n  type: pubsub.rabbitmq\r\n  version: v1\r\n  metadata:\r\n  - name: host\r\n    value: "amqps:\/\/xfj***.rmq.cloudamqp.co**hzhsq"\r\n  - name: consumerID\r\n    value: myapp\r\n  - name: durable\r\n    value: false\r\n  - name: deletedWhenUnused\r\n    value: false\r\n  - name: autoAck\r\n    value: false\r\n  - name: deliveryMode\r\n    value: 0\r\n  - name: requeueInFailure\r\n    value: false\r\n  - name: prefetchCount\r\n    value: 0\r\n  - name: reconnectWait\r\n    value: 0\r\n  - name: concurrencyMode\r\n    value: parallel\r\n  - name: publisherConfirm\r\n    value: false\r\n  - name: backOffPolicy\r\n    value: exponential\r\n  - name: backOffInitialInterval\r\n    value: 100\r\n  - name: backOffMaxRetries\r\n    value: 16\r\n  - name: enableDeadLetter # Optional enable dead Letter or not\r\n    value: true\r\n  - name: maxLen # Optional max message count in a queue\r\n    value: 3000\r\n  - name: maxLenBytes # Optional maximum length in bytes of a queue.\r\n    value: 10485760\r\n  - name: exchangeKind\r\n    value: fanout\r\n<\/pre>\n<\/div>\nTabi burada RabbitMQ sunucusu cloud yahut docker ortamlar\u0131ndan hangisindeyse ona g\u00f6re host yolunun ve di\u011fer konfig\u00fcrasyonlar\u0131n yap\u0131n\u0131za g\u00f6re \u00f6zelle\u015ftirilmesi gerekmektedir.<\/p>\nVelhas\u0131l kelam, component de\u011fi\u015fikli\u011fini yapt\u0131ktan sonra Dapr’\u0131 kald\u0131r\u0131p Self-hosted modda tekrardan aya\u011fa kald\u0131rman\u0131z gerekmektedir.
\n<\/a><\/p>\n
Component Dizinini De\u011fi\u015ftirme<\/strong>
\nComponent dosyalar\u0131n\u0131(YAML) bulunduklar\u0131 default dizinin d\u0131\u015f\u0131nda istedi\u011fimiz herhangi bir path’e de ta\u015f\u0131yabiliriz. Misal olarak solution ile ayn\u0131 dizinde olan ‘Components’ isimli bir klas\u00f6r i\u00e7erisine koymak istedi\u011fimizi varsayarsak e\u011fer bunun i\u00e7in Dapr ile uygulamalar\u0131 aya\u011fa kald\u0131r\u0131rken a\u015fa\u011f\u0131daki gibi talimat s\u00fcrecinde –components-path<\/span> parametresi ile de\u011fer olarak ilgili path’i ge\u00e7meliyiz.<\/p>\n
dapr run --app-id servicea --app-ssl<\/span> --app-port 1000 --dapr-http-port 1001<\/span> --components-path ..\/components<\/span> -- dotnet run<\/strong><\/code>
\ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 --dapr-http-port 2001<\/span> --components-path ..\/components<\/span> -- dotnet run<\/strong><\/code><\/p>\n
Dapr Dashboard<\/h4>\nDapr, yap\u0131lan t\u00fcm \u00e7al\u0131\u015fmalar\u0131 sa\u011flam\u0131\u015f oldu\u011fu dashboard \u00fczerinden g\u00f6rselle\u015ftirerek bizlere sunmaktad\u0131r. Bunun i\u00e7in dapr dashboard<\/code> talimat\u0131n\u0131 vererek dashboard’u 8080 portunda aya\u011fa kald\u0131rabilir ve http:\/\/localhost:8080<\/a> adresi \u00fczerinden direkt eri\u015fim g\u00f6sterebilirsiniz.<\/a><\/a><\/p>\n
Dapr Observability\/Zipkin UI<\/h4>\nDapr, toplam\u0131\u015f oldu\u011fu \u00e7e\u015fitli metrikleri farkl\u0131 UI teknolojilerini de destekleyecek \u015fekilde default olarak Zipkin ile g\u00f6rselle\u015ftirmektedir. Zipkin UI’\u0131 a\u00e7abilmek i\u00e7in direkt localhost:9411<\/a> adresine taray\u0131c\u0131da istek g\u00f6ndermeniz yeterlidir.<\/a>Ekran g\u00f6r\u00fcnt\u00fcs\u00fcnden de anla\u015f\u0131laca\u011f\u0131 \u00fczere servisler aras\u0131 pub\/sub temelli haberle\u015fmelerden tutun, hemen hemen t\u00fcm bilgileri Dapr’\u0131n observability \u00f6zelli\u011fi sayesinde elde ederek, g\u00f6zlemleyebilmekteyiz.<\/p>\n
Dapr – Visual Studio Code Extension<\/h4>\n<\/a>Dapr, uygulamalar\u0131m\u0131z\u0131 daha iyi y\u00f6netmek ve debug edebilmemiz i\u00e7in Visual Studio Code \u00fczerinden bir extension sunmaktad\u0131r.<\/p>\n
\u0130lgili extension’a a\u015fa\u011f\u0131daki adresten eri\u015fim g\u00f6sterebilirsiniz.
\nhttps:\/\/docs.dapr.io\/developing-applications\/ides\/vscode\/vscode-dapr-extension\/<\/a><\/p>\n
Bu extension ile Dapr’da aya\u011fa kald\u0131r\u0131lm\u0131\u015f uygulamalara HTTP request’leri atabilir yahut event yay\u0131nlayarak testlerinizi ger\u00e7ekle\u015ftirebilirsiniz. <\/p>\n
Nihai olarak,
\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere, \u00e7a\u011f\u0131n gere\u011fi olarak yaz\u0131l\u0131msal operasyonlarda her ne kadar sorumluluklar\u0131 farkl\u0131 servislere b\u00f6lerek distributed yakla\u015f\u0131mlar sergiliyor olsakta ve bu sergiledi\u011fimiz yakla\u015f\u0131mlar neticesinde b\u00fct\u00fcnsel olarak yaz\u0131l\u0131m\u0131n performans\u0131 ve verimlili\u011fi i\u00e7in en efektif yollar\u0131 bulabilmek maksad\u0131yla t\u00fcrl\u00fc t\u00fcrl\u00fc \u00e7abalara ve teknolojilere ba\u015fvuruyor olsakta dikkat ederseniz bu da\u011f\u0131lm\u0131\u015fl\u0131\u011f\u0131n getirisi olan karma\u015f\u0131kl\u0131\u011f\u0131 y\u00f6netebilmek i\u00e7in yine tek elden \u00e7\u00f6z\u00fcmlere y\u00f6neliyoruz. Evet, ad\u0131na microservice diyoruz ama i\u015fin do\u011fas\u0131 gere\u011fi t\u00fcm bu par\u00e7alanm\u0131\u015f yap\u0131y\u0131 y\u00f6netebilmek i\u00e7in monolitik d\u00fc\u015f\u00fcnceden hala vazge\u00e7emiyoruz \ud83d\ude42 \u00c7\u00fcnk\u00fc dedi\u011fim gibi i\u015fin do\u011fas\u0131nda bu var… Da\u011f\u0131tmak lakin tek bir standart ile da\u011f\u0131tmak var…<\/p>\n
\u0130\u015fte bu standartlardan biri olan Dapr’\u0131 m\u00fcmk\u00fcn mertebe teferruatl\u0131 incelemeye ve pratiksel olarak tecr\u00fcbe etmeye \u00e7al\u0131\u015fm\u0131\u015f olduk…<\/p>\n
\u00dc\u015fenmeden okuyup, e\u015flik etti\u011finiz i\u00e7in te\u015fekk\u00fcr ederim…<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…
\n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n
Not : \u00d6rnek \u00e7al\u0131\u015fmay\u0131 a\u015fa\u011f\u0131daki github adresinden edinebilirsiniz.
\nhttps:\/\/github.com\/gncyyldz\/Dapr_Examining<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, Bu i\u00e7eri\u011fimizde microservice uygulamalar\u0131 geli\u015ftirirken cloud’da resilient ve portable bir \u015fekilde \u00e7e\u015fitli dillerde \u00e7al\u0131\u015fma olana\u011f\u0131 sa\u011flayan event-driven runtime olan Dapr(Distributed Application Runtime)’\u0131n ne oldu\u011fu, microservice uygulamalar\u0131 geli\u015ftirme s\u00fcre\u00e7lerindeki ya\u015fan\u0131lan zorluklar\u0131n \u00fcstesinden gelinmesi i\u00e7in...<\/p>\n","protected":false},"author":1,"featured_media":25874,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4698],"tags":[4701,4699,4711,4715,4700,4705,4717,4720,4719,4718,4713,4714,4706,4710,4716,4712,4704,4703,4702,4707,4708,4709],"class_list":["post-25814","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dapr","tag-building-blocks","tag-dapr","tag-dapr-api","tag-dapr-bindings","tag-dapr-building-blocks","tag-dapr-component","tag-dapr-configuration-stores","tag-dapr-dashboard","tag-dapr-locks","tag-dapr-middleware","tag-dapr-name-resolution","tag-dapr-pub-sub-brokers","tag-dapr-rabbitmq","tag-dapr-sdk","tag-dapr-secret-stores","tag-dapr-state-stores","tag-dapr-aspnetcore","tag-dapr-client","tag-microservice-dapr","tag-open-telemetry","tag-otel","tag-zipkin"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814","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=25814"}],"version-history":[{"count":28,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814\/revisions"}],"predecessor-version":[{"id":25873,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814\/revisions\/25873"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/25874"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=25814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=25814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=25814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Component Types<\/th>\n	Detail<\/th>\n<\/tr>\n<\/thead>\n
State stores<\/strong><\/td>\n	Veri depolar\u0131d\u0131r. $\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Name resolution<\/strong><\/td>\n	\n $\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Pub\/sub brokers<\/strong><\/td>\n	Pub\/sub i\u015flemlerini y\u00fcr\u00fcten message broker’lard\u0131r. $\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Bindings<\/strong><\/td>\n	$\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Secret stores<\/strong><\/td>\n	Gizli bilgileri depolamak i\u00e7in kullan\u0131l\u0131r. $\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Configuration stores<\/strong><\/td>\n	Uygulama konfig\u00fcrasyonel verilerini depolamak i\u00e7in kullan\u0131l\u0131rlar. De\u011fi\u015fiklik meydana geldi\u011finde bildirimde bulunurlar. $\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n
Locks<\/strong><\/td>\n	Distributed lock.\n<\/td>\n<\/tr>\n
Middleware<\/strong><\/td>\n	$\"Distributed$ <\/a>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Dapr Yap\u0131land\u0131rma<\/h4>\n Dapr bir YAML dosyas\u0131 \u00fczerinden kolayca yap\u0131land\u0131r\u0131labilmektedir. Misal olarak a\u015fa\u011f\u0131da Dapr’\u0131n metrik bilgilerinin nereye g\u00f6nderilece\u011fine ili\u015fkin bir endpoint konfig\u00fcrasyonu \u00f6rneklendirilmektedir.<\/p>\n \n \r\napiVersion: dapr.io\/v1alpha1\r\nkind: Configuration\r\nmetadata:\r\n name: daprConfig\r\n namespace: default\r\nspec:\r\n tracing:\r\n samplingRate: "1"\r\n zipkin:\r\n endpointAddress: "http:\/\/localhost:9411\/api\/v2\/spans"\r\n<\/pre>\n<\/div>\n Ayr\u0131ca a\u015fa\u011f\u0131daki ‘dapr-system’ namespace’inde ‘daprsystem’ olarak isimlendirilen Dapr konfig\u00fcrasyon \u00f6rne\u011fini de inceleyebilirsiniz.<\/p>\n \n \r\napiVersion: dapr.io\/v1alpha1\r\nkind: Configuration\r\nmetadata:\r\n name: daprsystem\r\n namespace: dapr-system\r\nspec:\r\n mtls:\r\n enabled: true\r\n workloadCertTTL: "24h"\r\n allowedClockSkew: "15m"\r\n<\/pre>\n<\/div>\n Dapr Observability\/\u0130zleme\/G\u00f6zlenebilirlik<\/h4>\n $\"Distributed$ <\/a>Bir uygulaman\u0131n, en hayati noktalar\u0131ndan birisi \u00e7al\u0131\u015fma zaman\u0131nda nas\u0131l davrand\u0131\u011f\u0131n\u0131 izleyebilmektir. \u00d6zellikle uygulama \u00e7a\u011fr\u0131lar\u0131n\u0131n g\u00f6zlenebilmesi, performans durumunun \u00f6l\u00e7\u00fcmlenebilmesi yahut meydana gelen beklenmeyen problemlerin an\u0131nda \u00e7\u00f6z\u00fclebilmesi, hatalar\u0131n ay\u0131klanabilmesi veya olu\u015facak darbo\u011fazlar\u0131n(bottlenecks) anla\u015f\u0131labilmesi i\u00e7in g\u00f6zlenebilirlik olduk\u00e7a \u00f6nem arz etmektedir. Evet, biliyorsunuz ki bu herhangi bir sistem i\u00e7in zordur lakin bir istek neticesinde k\u00fc\u00e7\u00fck mikro servisler aras\u0131nda ak\u0131\u015f silsilesinin s\u00f6z konusu oldu\u011fu distributed bir sistem i\u00e7in daha da zordur.<\/p>\n Bir uygulamayla ilgili bellek t\u00fcketimi, CPU kullan\u0131m\u0131 vs. gibi temel seviyedeki metrikler rahatl\u0131kla al\u0131nabiliyor olsa da as\u0131l \u00f6nemli olan bir \u00e7a\u011fr\u0131 s\u00fcrecinde uygulaman\u0131n davran\u0131\u015f\u0131na dair anlaml\u0131 bilgilerin toplanmas\u0131d\u0131r. Ve bu da geli\u015ftirici a\u00e7\u0131s\u0131ndan ihtiya\u00e7 noktalar\u0131na kodsal m\u00fcdahalelerde bulunulmas\u0131 gerekti\u011fi anlam\u0131na gelmektedir. \u00c7o\u011fu zaman toplanan bu metrikler t\u00fcrl\u00fc ara\u00e7larla g\u00f6rselle\u015ftirilerek monit\u00f6r edilirler.<\/p>\n \u015eimdi mant\u0131ken olaya bakt\u0131\u011f\u0131m\u0131zda uygulamalar\u0131n business logic’inin bir par\u00e7as\u0131 olmayan bu \u00e7al\u0131\u015fmalar\u0131 ger\u00e7ekle\u015ftirmek geli\u015ftiriciler a\u00e7\u0131s\u0131ndan ciddi bir y\u00fckt\u00fcr ve hatta bu y\u00fck bu ara\u00e7lar\u0131n SDK’lerini kullanma, API’lerini anlama vs. gibi durumlar\u0131 gerektirdik\u00e7e daha da ciddi hale gelebilmektedir.<\/p>\n Bir \u00e7a\u011fr\u0131m sonucu mikro servisler aras\u0131nda ak\u0131\u015f\u0131n ba\u015flad\u0131\u011f\u0131 durumlarda Dapr bu distributed senaryolarda g\u00f6zlenebilirlik a\u00e7\u0131s\u0131ndan avantaj sa\u011flamakta ve yayg\u0131n olarak kabul g\u00f6ren Open Telemetry (OTEL) veya Zipkin protokolleri ile metrikleri toplayabildi\u011fi i\u00e7in bir\u00e7ok g\u00f6rselle\u015ftirme arac\u0131yla kolayca entegre edilebilmektedir.<\/p>\n Ayr\u0131ca Dapr, kullan\u0131c\u0131lar\u0131n sorunlar\u0131n\u0131 tan\u0131mlamas\u0131na ve hata ay\u0131klama yapmas\u0131na yard\u0131mc\u0131 olmak i\u00e7in i\u00e7erisinde uyar\u0131, hata ve bilgi mesajlar\u0131 bar\u0131nd\u0131ran log<\/strong>‘larla birlikte, sistemin durumunu kontrol edebilmek i\u00e7in bir Health Check<\/strong> mekanizmas\u0131 da bar\u0131nd\u0131rmaktad\u0131r.<\/p>\n Dapr Nas\u0131l Y\u00fcklenir?<\/h4>\nDapr’\u0131 kullanabilmek i\u00e7in \u00f6ncelikle Dapr CLI’\u0131 bilgisayar\u0131n\u0131za kurman\u0131z gerekmektedir. Bunun i\u00e7in \u015fu adresteki<\/a> \u00f6nergeleri s\u0131ras\u0131yla takip etmeniz yeterlidir.<\/p>\n Powershell \u00fczerinden Dapr’\u0131 y\u00fckleyiniz. \n $\"Distributed$ <\/a>Ard\u0131ndan `dapr<\/code> komutuyla y\u00fcklenip, y\u00fcklenmedi\u011fini do\u011frulay\u0131n\u0131z.`<\/a>Self-hosted modda Dapr’\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n\u0131z.<\/a>Ve Dapr container’lar\u0131n\u0131 listeleyip nihai kontrolde bulununuz.<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Dapr temel olarak ‘Redis’, ‘Openzipkin\/Zipkin’ ve ‘Daprio\/Dapr’ olmak \u00fczere \u00fc\u00e7 container ile ba\u015flang\u0131\u00e7 sa\u011flamaktad\u0131r. ‘Openzipkin\/Zipkin’ container’\u0131 ile metrikleri toplarken, ‘Redis’ ile state-store ve messaging operasyonlar\u0131n\u0131 y\u00fcr\u00fctmektedir. Ayr\u0131ca bu component’lerin Windows i\u015fletim sistemlerinde C:\\Users\\[name]\\.dapr<\/code> klas\u00f6r\u00fc alt\u0131nda tan\u0131mland\u0131klar\u0131n\u0131 bilmenizde fayda vard\u0131r. (Linux’da ise $HOME\/.dapr<\/code> dizininde tan\u0131mlanmaktad\u0131r)<\/p>\n Dapr \u0130le Basit D\u00fczeyde Servislerin Haberle\u015fmesi<\/h4>\n\u015eimdi ise son olarak Dapr ile basit seviyede iki servisin haberle\u015fmesini inceleyerek i\u00e7eri\u011fimizi nihayete erdirelim istiyorum. Bunun i\u00e7in bo\u015f bir solution’da ‘Dapr.Basic.ServiceA’ ve ‘Dapr.Basic.ServiceB’ isimlerinde olmak \u00fczere iki Asp.NET Core API uygulamas\u0131n\u0131 a\u015fa\u011f\u0131daki gibi olu\u015fturunuz. \n<\/a> \n\u015eimdi bu servisler aras\u0131nda publish edilmi\u015f event \u00fczerinden haberle\u015fmeyi sa\u011flayabilmek i\u00e7in herhangi bir k\u00fct\u00fcphane, teknoloji vs. d\u00fc\u015f\u00fcnmeksizin direkt olarak Dapr ile bu i\u015flemi ger\u00e7ekle\u015ftirebilece\u011fiz.<\/p>\n Burada ‘Dapr.Basic.ServiceA’ servisi ile event publish edilirken ‘Dapr.Basic.ServiceB’ servisi ile de bu event’i dinleyecek ve gerekli i\u015flemleri ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n Tabi bu i\u015flemi SDK<\/strong> kullanarak yahut HTTP<\/strong> \u00fczerinden istekte bulunarak iki farkl\u0131 \u015fekilde ger\u00e7ekle\u015ftirebiliriz. \u015eimdi gelin her iki y\u00f6ntemle de nas\u0131l \u00e7al\u0131\u015fma sa\u011flayabiliriz s\u0131ras\u0131yla inceleyelim;<\/p>\n \nSDK<\/strong> \nSDK \u00fczerinden geli\u015ftirmeyi sa\u011flayabilmek i\u00e7in event publish edecek olan ‘Dapr.Basic.ServiceA’ isimli servise Dapr.Client<\/a> ve Dapr.AspNetCore<\/a> library’lerini, t\u00fcketici olan ‘Dapr.Basic.ServiceB’ isimli servise ise sadece Dapr.AspNetCore<\/a> library’sini y\u00fckleyiniz.<\/p>\nArd\u0131ndan ‘Dapr.Basic.ServiceA’da a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftiriniz.<\/p>\n\n\r\nusing Dapr.Client;\r\nusing Shared.Events;\r\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\nbuilder.Services.AddDaprClient();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/send-event\/{eventText}", async (string eventText, DaprClient client) =>\r\n{\r\n await client.PublishEventAsync(pubsubName: "pubsub", topicName: "example.event", new Event(eventText));\r\n Console.WriteLine(eventText);\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.MapControllers();\r\napp.Run("https:\/\/localhost:1000");\r\n<\/pre>\n<\/div>\nYukar\u0131daki kod blo\u011funda, 8.<\/strong> sat\u0131rda ‘AddDaprClient’ servisi uygulamaya dahil edilmekte ve 12<\/strong> ile 16.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise \/send-event\/{eventText}<\/code> endpoint’i i\u00e7erisinde ‘Event’ t\u00fcr\u00fcnden bir event publish edilmektedir. Burada ‘pubsubName’e C:\\Users\\[name]\\.dapr<\/code> dizininde bulunan ‘components’ klas\u00f6r\u00fc i\u00e7erisindeki ‘pubsub.yaml’ dosyas\u0131n\u0131n ‘metadata:name’ bilgisinin verildi\u011fine dikkatinizi \u00e7ekerim.<\/a>‘Dapr.Basic.ServiceB’ servisinde ise a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftiriniz.<\/p>\n \n\r\nusing Dapr;\r\nusing Shared.Events;\r\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers().AddDapr();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapPost("\/get-event", [Topic("pubsub", "example.event")] (Event @event) =>\r\n{\r\n Console.WriteLine(@event.Text);\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.UseCloudEvents();\r\napp.MapControllers();\r\napp.MapSubscribeHandler();\r\napp.Run("https:\/\/localhost:2000");\r\n<\/pre>\n<\/div>\nBurada da 6.<\/strong> sat\u0131rda Dapr ‘AddDapr’ extension’\u0131 sayesinde MVC pipeline’\u0131na dahil edilmektedir. 17.<\/strong> ve 19.<\/strong> sat\u0131rlarda ise s\u0131ras\u0131yla ‘UseCloudEvents’ ve ‘MapSubscribeHandler’ middleware’leri \u00e7a\u011fr\u0131lmaktad\u0131r. Dapr, publish edilen event’lar\u0131 CloudEvent format\u0131na \u00e7evirdi\u011fi i\u00e7in ayn\u0131 \u015fekilde event’i ilgili t\u00fcre d\u00f6n\u00fc\u015ft\u00fcrebilmek amac\u0131yla ‘UseCloudEvents’ middleware’i kullan\u0131lmaktad\u0131r. ‘MapSubscribeHandler’ middleware’i ise 11.<\/strong> sat\u0131rda yay\u0131nlanm\u0131\u015f olan event’i dinleyebilmek i\u00e7in kulland\u0131\u011f\u0131m\u0131z Topic<\/code> attribute’unu i\u015flevsel hale getirebilmek i\u00e7in \u00e7a\u011fr\u0131lmaktad\u0131r.<\/p>\nBu i\u015flemlerden sonra a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde Dapr \u00fczerinden servisleri aya\u011fa kald\u0131r\u0131n\u0131z ve ekran g\u00f6r\u00fcnt\u00fcs\u00fcndeki gibi teste tabi tutunuz. \ndapr run --app-id servicea --app-ssl<\/span> --app-port 1000 -- dotnet run<\/strong><\/code> \ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 -- dotnet run<\/strong><\/code> \n(SSL connection kullanan uygulamalarda –app-ssl<\/span> parametresi ile Dapr’a g\u00fcvenli olmayan bir SSL ba\u011flant\u0131s\u0131 \u00fczerinden uygulamalar\u0131 aya\u011fa kald\u0131rmas\u0131 gerekti\u011fini s\u00f6ylemi\u015f oluyoruz.)<\/span> \n<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Dapr sayesinde publish etti\u011fimiz event herhangi bir harici k\u00fct\u00fcphaneye ihtiya\u00e7 duymaks\u0131z\u0131n direkt subscribe olan bir consumer taraf\u0131ndan ba\u015far\u0131yla i\u015flenmektedir.\n<\/li>\n HTTP<\/strong> \nBenzer \u015fekilde iki servis aras\u0131ndaki haberle\u015fmeyi HTTP \u00fczerinden sa\u011flamak istiyorsan\u0131z burada birazc\u0131k farkl\u0131 davran\u0131\u015f sergilemeniz gerekmektedir.<\/p>\n‘Dapr.Basic.ServiceA’ servisinde a\u015fa\u011f\u0131daki gibi bir \u00e7al\u0131\u015fma ger\u00e7ekle\u015ftiriniz;<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddControllers();\r\nbuilder.Services.AddEndpointsApiExplorer();\r\nbuilder.Services.AddDaprClient();\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/send-event\/{eventText}", async (string eventText, DaprClient client) =>\r\n{\r\n HttpClient httpClient = new();\r\n\r\n Event @event = new(eventText);\r\n string jsonData = JsonSerializer.Serialize(@event, options: new JsonSerializerOptions() { PropertyNamingPolicy = JsonNamingPolicy.CamelCase });\r\n\r\n httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue(MediaTypeNames.Application.Json));\r\n StringContent body = new(jsonData, Encoding.UTF8, MediaTypeNames.Application.Json);\r\n var response = await httpClient.PostAsync($"http:\/\/localhost:2001\/v1.0\/publish\/pubsub\/example.event", body);\r\n\r\n return Results.Ok($"Status Code : {response.StatusCode} \| Event : {@event.Text}\\"");\r\n});\r\n\r\napp.UseHttpsRedirection();\r\napp.MapControllers();\r\napp.Run("https:\/\/localhost:1000");\r\n<\/pre>\n<\/div>\nYukar\u0131daki kod blo\u011funu incelerseniz e\u011fer 11<\/strong> ile 20.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda HTTP protokol\u00fc \u00fczerinden bir event yay\u0131nlama i\u015flemi ger\u00e7ekle\u015ftirilmektedir. Bu i\u015flem i\u00e7in 18.<\/strong> sat\u0131rda http:\/\/localhost:2001\/v1.0\/publish\/pubsub\/example.event<\/code> adresine POST iste\u011fi g\u00f6nderilmektedir. Bu adreste nerden \u00e7\u0131kt\u0131 hoca la?<\/strong> diye sordu\u011funuzu duyar gibiyim… Tabi ki de kafam\u0131za g\u00f6re bir adres yaz\u0131p istekte bulunmad\u0131\u011f\u0131m\u0131z a\u015fikar. Dapr, HTTP \u00fczerinden ger\u00e7ekle\u015ftirilecek pub\/sub i\u015flemleri i\u00e7in a\u015fa\u011f\u0131daki formatta bir url’e istek g\u00f6ndermemiz gerekti\u011fini bizlere s\u00f6ylemektedir. \nhttp:\/\/localhost:<daprPort><\/span>\/v1.0\/publish\/<pubsubname><\/span>\/<topic><\/span>[?<metadata>]<\/strong><\/code> \nBu adres \u015femas\u0131ndaki <daprPort><\/span>, haberle\u015fme sa\u011flanmak istenen servisin birazdan nas\u0131l tan\u0131mlanabilece\u011fini g\u00f6rece\u011fimiz Dapr HTTP Port’una kar\u015f\u0131l\u0131k gelmektedir. <pubsubname><\/span>, hangi pub\/sub component’i kullan\u0131l\u0131yorsa onun ad\u0131na kar\u015f\u0131l\u0131k gelmektedir. Ve son olarak <topic><\/span> ise event’in publish edildi\u011fi topic ad\u0131na kar\u015f\u0131l\u0131k gelmektedir.<\/p>\n HTTP protokol\u00fc \u00fczerinden \u00e7al\u0131\u015fma s\u00fcrecinde, yukar\u0131daki gibi bir event publish edildi\u011fi taktirde; Dapr, consumer g\u00f6revi g\u00f6ren serviste \nhttp:\/\/localhost:<appPort>\/dapr\/subscribe<\/span><\/code> endpoint’ini GET request’i ile tetiklemektedir. B\u00f6ylece ilgili serviste bir event’in publish edildi\u011fine dair bilgilenilmi\u015f olunacakt\u0131r. \u015eimdi bu mant\u0131k do\u011frultusunda ‘Dapr.Basic.ServiceB’ servisini ise a\u015fa\u011f\u0131daki gibi geli\u015ftiriniz.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/dapr\/subscribe", () =>\r\n{\r\n return Results.Json(new[] {new\r\n {\r\n PubSubName = "pubsub",\r\n Topic = "example.event",\r\n Route = "\/get-event"\r\n } });\r\n});\r\n\r\napp.MapPost("\/get-event", (DaprData<Event> @event) =>\r\n{\r\n Console.WriteLine(@event.Data.Text);\r\n});\r\n\r\napp.Run("https:\/\/localhost:2000");\r\nrecord DaprData<T>(T Data);\r\n<\/pre>\n<\/div>\nYukar\u0131daki \u00e7al\u0131\u015fmaya dikkat ederseniz, 4<\/strong> ile 12.<\/strong> sat\u0131r aral\u0131\u011f\u0131nda herhangi bir event yay\u0131nland\u0131\u011f\u0131 taktirde Dapr taraf\u0131ndan tetiklenecek olan \/dapr\/subscribe<\/code> endpoint’ine kar\u015f\u0131l\u0131k bir minimal api tan\u0131mlanm\u0131\u015ft\u0131r. Bu action i\u00e7erisinde, JSON olarak ‘PubSubName’, ‘Topic’ ve ‘Route’ bilgilerini bar\u0131nd\u0131ran bir obje, \u00fcretilmi\u015f bir koleksiyona dahil olacak \u015fekilde geriye return edilmektedir. Burada ‘Route’ta tan\u0131ml\u0131 olan \/get-event<\/code> de\u011feri sayesinde publish edilmi\u015f olan event’\u0131n hangi endpoint i\u00e7erisinde handle edilece\u011fi ifade edilmektedir. Dolay\u0131s\u0131yla bu a\u015famadan sonra 14<\/strong> ile 17.<\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki action tetiklenecektir.<\/p>\n \u0130lgili action’a g\u00f6z atarsan\u0131z e\u011fer 20.<\/strong> sat\u0131rda tan\u0131mlanm\u0131\u015f olan ‘DaprData<T>’ record t\u00fcr\u00fcnden bir parametre almaktad\u0131r. Burada T yerine ‘Event’ yaz\u0131larak gelen de\u011fer tam olarak elde edilmi\u015f olmaktad\u0131r. Bu tarz bir \u00e7al\u0131\u015fman\u0131n nedenini sorarsan\u0131z e\u011fer bu metota gelen verinin yap\u0131s\u0131n\u0131n a\u015fa\u011f\u0131daki gibi olmas\u0131d\u0131r.<\/p>\n\n\r\n{\r\n "data": {\r\n "text": "nevin"\r\n },\r\n "datacontenttype": "application\/json; charset=utf-8",\r\n "id": "dfd6a336-b99f-4cc7-a384-b8a31ca4f791",\r\n "pubsubname": "pubsub",\r\n "source": "serviceb",\r\n "specversion": "1.0",\r\n "time": "2022-11-14T01:26:03+03:00",\r\n "topic": "example.event",\r\n "traceid": "00-97ecee8642fbcf8549f43db6f9d7074c-4b255f63bafe0b31-01",\r\n "traceparent": "00-97ecee8642fbcf8549f43db6f9d7074c-4b255f63bafe0b31-01",\r\n "tracestate": "",\r\n "type": "com.dapr.event.sent"\r\n}\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bir\u00e7ok bilgi tek bir json datas\u0131 i\u00e7erisinde k\u00fcm\u00fclatif olarak gelmektedir. Haliyle burada publish edilmi\u015f event’i temsil edebilmek i\u00e7in bu json datas\u0131n\u0131n i\u00e7erisindeki ‘data’ parametresini alabilecek bir \u00e7al\u0131\u015fma yapmam\u0131z gerekecekti. Bunun i\u00e7in generic bir record ile gayet efektif bir \u00e7\u00f6z\u00fcm getirebildik kanaatindeyim \ud83d\ude42 Action tetiklendi\u011finde deserialize s\u00fcreci ba\u015flat\u0131lacak ve ‘DaprData<T>’ t\u00fcr\u00fcne g\u00f6re bir \u00e7\u0131kt\u0131 al\u0131nacakt\u0131r. Ee ‘DaprData<T>’ t\u00fcr\u00fc de i\u00e7erisinde ‘Data’ parametresi ald\u0131\u011f\u0131 i\u00e7in ilgili json i\u00e7erisindeki ‘data’ bu parametreyle e\u015fle\u015fecek ve bizlere direkt T parametresine verilen t\u00fcrde de\u011feri getirecektir.<\/p>\n \u0130\u015fte bu kadar…<\/p>\nSon olarak a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde uygulamalar\u0131 Dapr \u00fczerinden aya\u011fa kald\u0131r\u0131p, testlerinizi ger\u00e7ekle\u015ftiriniz. \ndapr run --app-id servicea --app-ssl<\/span> --app-port 1000 --dapr-http-port 1001<\/span> -- dotnet run<\/strong><\/code> \ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 --dapr-http-port 2001<\/span> -- dotnet run<\/strong><\/code> \n(–dapr-http-port …<\/span> parametresi aya\u011fa kald\u0131r\u0131lan uygulaman\u0131n Dapr’da HTTP \u00fczerinden eri\u015filebilen port’unu ifade etmektedir. Yukar\u0131larda bahsi ge\u00e7en <daprPort><\/span> alan\u0131na ilgili servisin –dapr-http-port bilgisi verilmelidir.)<\/span> \n<\/a>Evet, b\u00f6ylece yine herhangi bir k\u00fct\u00fcphane kullanmaks\u0131z\u0131n Dapr ile HTTP \u00fczerinden iki servisin haberle\u015fmesini sa\u011flayabilmi\u015f bulunuyoruz.\n<\/li>\n<\/ul>\n Component De\u011fi\u015ftirme<\/h4>\nDapr’\u0131n component’leri bar\u0131nd\u0131rd\u0131\u011f\u0131 default path’inin Windows i\u00e7in C:\\Users\\[name]\\.dapr<\/code>, Linux i\u00e7in ise $HOME\/.dapr<\/code> oldu\u011funu daha \u00f6nceki sat\u0131rlar\u0131m\u0131zda bildirmi\u015ftik.<\/p>\nBir component’i de\u011fi\u015ftirmek istedi\u011fimizde tek yap\u0131lmas\u0131 gereken ilgili YAML dosyas\u0131n\u0131n istenilen component i\u00e7eri\u011fi ile de\u011fi\u015ftirilmesidir. Misal olarak, i\u00e7eri\u011fimiz s\u00fcrecinde default olarak gelen ve pub\/sub componenti olarak kullanm\u0131\u015f oldu\u011fumuz Redis’i RabbitMQ component’i ile de\u011fi\u015ftirmek istiyorsak e\u011fer yapmam\u0131z gereken \u015furadan<\/a> RabbitMQ component’ine ait format\u0131 al\u0131p ilgili dizindeki ‘pubsub.yaml’ dosyas\u0131 i\u00e7erisindekilerle de\u011fi\u015ftirmektir.<\/p>\n \n\r\napiVersion: dapr.io\/v1alpha1\r\nkind: Component\r\nmetadata:\r\n name: rabbitmq-pubsub\r\nspec:\r\n type: pubsub.rabbitmq\r\n version: v1\r\n metadata:\r\n - name: host\r\n value: "amqps:\/\/xfj*.rmq.cloudamqp.cohzhsq"\r\n - name: consumerID\r\n value: myapp\r\n - name: durable\r\n value: false\r\n - name: deletedWhenUnused\r\n value: false\r\n - name: autoAck\r\n value: false\r\n - name: deliveryMode\r\n value: 0\r\n - name: requeueInFailure\r\n value: false\r\n - name: prefetchCount\r\n value: 0\r\n - name: reconnectWait\r\n value: 0\r\n - name: concurrencyMode\r\n value: parallel\r\n - name: publisherConfirm\r\n value: false\r\n - name: backOffPolicy\r\n value: exponential\r\n - name: backOffInitialInterval\r\n value: 100\r\n - name: backOffMaxRetries\r\n value: 16\r\n - name: enableDeadLetter # Optional enable dead Letter or not\r\n value: true\r\n - name: maxLen # Optional max message count in a queue\r\n value: 3000\r\n - name: maxLenBytes # Optional maximum length in bytes of a queue.\r\n value: 10485760\r\n - name: exchangeKind\r\n value: fanout\r\n<\/pre>\n<\/div>\nTabi burada RabbitMQ sunucusu cloud yahut docker ortamlar\u0131ndan hangisindeyse ona g\u00f6re host yolunun ve di\u011fer konfig\u00fcrasyonlar\u0131n yap\u0131n\u0131za g\u00f6re \u00f6zelle\u015ftirilmesi gerekmektedir.<\/p>\nVelhas\u0131l kelam, component de\u011fi\u015fikli\u011fini yapt\u0131ktan sonra Dapr’\u0131 kald\u0131r\u0131p Self-hosted modda tekrardan aya\u011fa kald\u0131rman\u0131z gerekmektedir. \n<\/a><\/p>\n Component Dizinini De\u011fi\u015ftirme<\/strong> \nComponent dosyalar\u0131n\u0131(YAML) bulunduklar\u0131 default dizinin d\u0131\u015f\u0131nda istedi\u011fimiz herhangi bir path’e de ta\u015f\u0131yabiliriz. Misal olarak solution ile ayn\u0131 dizinde olan ‘Components’ isimli bir klas\u00f6r i\u00e7erisine koymak istedi\u011fimizi varsayarsak e\u011fer bunun i\u00e7in Dapr ile uygulamalar\u0131 aya\u011fa kald\u0131r\u0131rken a\u015fa\u011f\u0131daki gibi talimat s\u00fcrecinde –components-path<\/span> parametresi ile de\u011fer olarak ilgili path’i ge\u00e7meliyiz.<\/p>\n dapr run --app-id servicea --app-ssl<\/span> --app-port 1000 --dapr-http-port 1001<\/span> --components-path ..\/components<\/span> -- dotnet run<\/strong><\/code> \ndapr run --app-id serviceb --app-ssl<\/span> --app-port 2000 --dapr-http-port 2001<\/span> --components-path ..\/components<\/span> -- dotnet run<\/strong><\/code><\/p>\n Dapr Dashboard<\/h4>\nDapr, yap\u0131lan t\u00fcm \u00e7al\u0131\u015fmalar\u0131 sa\u011flam\u0131\u015f oldu\u011fu dashboard \u00fczerinden g\u00f6rselle\u015ftirerek bizlere sunmaktad\u0131r. Bunun i\u00e7in dapr dashboard<\/code> talimat\u0131n\u0131 vererek dashboard’u 8080 portunda aya\u011fa kald\u0131rabilir ve http:\/\/localhost:8080<\/a> adresi \u00fczerinden direkt eri\u015fim g\u00f6sterebilirsiniz.<\/a><\/a><\/p>\n Dapr Observability\/Zipkin UI<\/h4>\nDapr, toplam\u0131\u015f oldu\u011fu \u00e7e\u015fitli metrikleri farkl\u0131 UI teknolojilerini de destekleyecek \u015fekilde default olarak Zipkin ile g\u00f6rselle\u015ftirmektedir. Zipkin UI’\u0131 a\u00e7abilmek i\u00e7in direkt localhost:9411<\/a> adresine taray\u0131c\u0131da istek g\u00f6ndermeniz yeterlidir.<\/a>Ekran g\u00f6r\u00fcnt\u00fcs\u00fcnden de anla\u015f\u0131laca\u011f\u0131 \u00fczere servisler aras\u0131 pub\/sub temelli haberle\u015fmelerden tutun, hemen hemen t\u00fcm bilgileri Dapr’\u0131n observability \u00f6zelli\u011fi sayesinde elde ederek, g\u00f6zlemleyebilmekteyiz.<\/p>\n Dapr – Visual Studio Code Extension<\/h4>\n<\/a>Dapr, uygulamalar\u0131m\u0131z\u0131 daha iyi y\u00f6netmek ve debug edebilmemiz i\u00e7in Visual Studio Code \u00fczerinden bir extension sunmaktad\u0131r.<\/p>\n \u0130lgili extension’a a\u015fa\u011f\u0131daki adresten eri\u015fim g\u00f6sterebilirsiniz. \nhttps:\/\/docs.dapr.io\/developing-applications\/ides\/vscode\/vscode-dapr-extension\/<\/a><\/p>\n Bu extension ile Dapr’da aya\u011fa kald\u0131r\u0131lm\u0131\u015f uygulamalara HTTP request’leri atabilir yahut event yay\u0131nlayarak testlerinizi ger\u00e7ekle\u015ftirebilirsiniz. <\/p>\n Nihai olarak, \nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere, \u00e7a\u011f\u0131n gere\u011fi olarak yaz\u0131l\u0131msal operasyonlarda her ne kadar sorumluluklar\u0131 farkl\u0131 servislere b\u00f6lerek distributed yakla\u015f\u0131mlar sergiliyor olsakta ve bu sergiledi\u011fimiz yakla\u015f\u0131mlar neticesinde b\u00fct\u00fcnsel olarak yaz\u0131l\u0131m\u0131n performans\u0131 ve verimlili\u011fi i\u00e7in en efektif yollar\u0131 bulabilmek maksad\u0131yla t\u00fcrl\u00fc t\u00fcrl\u00fc \u00e7abalara ve teknolojilere ba\u015fvuruyor olsakta dikkat ederseniz bu da\u011f\u0131lm\u0131\u015fl\u0131\u011f\u0131n getirisi olan karma\u015f\u0131kl\u0131\u011f\u0131 y\u00f6netebilmek i\u00e7in yine tek elden \u00e7\u00f6z\u00fcmlere y\u00f6neliyoruz. Evet, ad\u0131na microservice diyoruz ama i\u015fin do\u011fas\u0131 gere\u011fi t\u00fcm bu par\u00e7alanm\u0131\u015f yap\u0131y\u0131 y\u00f6netebilmek i\u00e7in monolitik d\u00fc\u015f\u00fcnceden hala vazge\u00e7emiyoruz \ud83d\ude42 \u00c7\u00fcnk\u00fc dedi\u011fim gibi i\u015fin do\u011fas\u0131nda bu var… Da\u011f\u0131tmak lakin tek bir standart ile da\u011f\u0131tmak var…<\/p>\n \u0130\u015fte bu standartlardan biri olan Dapr’\u0131 m\u00fcmk\u00fcn mertebe teferruatl\u0131 incelemeye ve pratiksel olarak tecr\u00fcbe etmeye \u00e7al\u0131\u015fm\u0131\u015f olduk…<\/p>\n \u00dc\u015fenmeden okuyup, e\u015flik etti\u011finiz i\u00e7in te\u015fekk\u00fcr ederim…<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n Not : \u00d6rnek \u00e7al\u0131\u015fmay\u0131 a\u015fa\u011f\u0131daki github adresinden edinebilirsiniz. \nhttps:\/\/github.com\/gncyyldz\/Dapr_Examining<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Bu i\u00e7eri\u011fimizde microservice uygulamalar\u0131 geli\u015ftirirken cloud’da resilient ve portable bir \u015fekilde \u00e7e\u015fitli dillerde \u00e7al\u0131\u015fma olana\u011f\u0131 sa\u011flayan event-driven runtime olan Dapr(Distributed Application Runtime)’\u0131n ne oldu\u011fu, microservice uygulamalar\u0131 geli\u015ftirme s\u00fcre\u00e7lerindeki ya\u015fan\u0131lan zorluklar\u0131n \u00fcstesinden gelinmesi i\u00e7in...<\/p>\n","protected":false},"author":1,"featured_media":25874,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4698],"tags":[4701,4699,4711,4715,4700,4705,4717,4720,4719,4718,4713,4714,4706,4710,4716,4712,4704,4703,4702,4707,4708,4709],"class_list":["post-25814","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dapr","tag-building-blocks","tag-dapr","tag-dapr-api","tag-dapr-bindings","tag-dapr-building-blocks","tag-dapr-component","tag-dapr-configuration-stores","tag-dapr-dashboard","tag-dapr-locks","tag-dapr-middleware","tag-dapr-name-resolution","tag-dapr-pub-sub-brokers","tag-dapr-rabbitmq","tag-dapr-sdk","tag-dapr-secret-stores","tag-dapr-state-stores","tag-dapr-aspnetcore","tag-dapr-client","tag-microservice-dapr","tag-open-telemetry","tag-otel","tag-zipkin"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814","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=25814"}],"version-history":[{"count":28,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814\/revisions"}],"predecessor-version":[{"id":25873,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25814\/revisions\/25873"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/25874"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=25814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=25814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=25814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}