{"id":4251,"date":"2023-02-01T20:54:50","date_gmt":"2023-02-01T19:54:50","guid":{"rendered":"https:\/\/gokhan-gokalp.com\/?p=4251"},"modified":"2023-02-01T22:46:09","modified_gmt":"2023-02-01T21:46:09","slug":"building-microservices-by-using-dapr-and-net-with-minimum-effort-02-azure-container-apps","status":"publish","type":"post","link":"https:\/\/gokhan-gokalp.com\/tr\/building-microservices-by-using-dapr-and-net-with-minimum-effort-02-azure-container-apps\/","title":{"rendered":"Dapr ve .NET Kullanarak Minimum Efor ile Microservice’ler Geli\u015ftirmek – 02 (Azure Container Apps)"},"content":{"rendered":"

Bir \u00f6nceki makale serisinde Dapr<\/em><\/strong> projesinden ve faydalar\u0131ndan bahsedip, local ortamda self-hosted mode olarak .NET 6<\/em> ile iki adet \u00f6rnek microservice geli\u015ftirmi\u015ftik. (E\u011fer ilk seriyi okumad\u0131 iseniz, buradan<\/a> <\/em>ula\u015fabilirsiniz.)<\/p>\n

Bu makale kapsam\u0131nda ise bir \u00f6nceki makalede geli\u015ftirmi\u015f oldu\u011fumuz \u00f6rnek ShoppingCart<\/em> ve Recommendation<\/em> microservice’lerinin default olan Dapr<\/em> component’lerini Azure<\/strong><\/em> resource’lar\u0131 ile de\u011fi\u015ftirerek, Azure Container Apps<\/strong><\/em> \u00fczerine deployment i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n

\u00d6ncelikle konuya Azure Container Apps<\/em> ile ilgili k\u00fc\u00e7\u00fck bir giri\u015f yaparak ba\u015flayal\u0131m.<\/p>\n

Azure Container Apps<\/h2>\n

Azure Container Apps<\/em>, Microsoft<\/em>‘un May\u0131s 2022’de GA<\/em> olarak duyurdu\u011fu uygulama odakl\u0131 olarak geli\u015ftirilmi\u015f bir fully managed serverless container runtime’\u0131d\u0131r.<\/p>\n

Azure Kubernetes Service<\/em> \u00fczerinde \u00e7al\u0131\u015f\u0131yor olup, temelinde KEDA<\/em><\/strong>, Envoy<\/em><\/strong> ve Dapr<\/em><\/strong> gibi g\u00fc\u00e7l\u00fc projeler bulunmaktad\u0131r. Yani Azure Container Apps<\/em> kullanarak, t\u00fcm Dapr API<\/em>‘lar\u0131ndan managed<\/strong> bir \u015fekilde yararlanabilmekteyiz. Bu sayede bizlere g\u00fcvenli<\/strong>, mod\u00fcler<\/strong> ve \u00f6l\u00e7eklenebilir<\/strong> bir alt yap\u0131 sa\u011flayarak, bizlerin daha \u00e7ok uygulama taraf\u0131na odaklanabilmesini sa\u011flamaktad\u0131r. Ayr\u0131ca KEDA<\/em> sayesinde bizlere event-driven auto scaling<\/strong> ve zero-scaling<\/strong> sa\u011flayarak cost optimizasyonu yapabilmemize de olanak tan\u0131maktad\u0131r.<\/p>\n

Bildi\u011fimiz gibi kubernetes<\/em> taraf\u0131nda HPA<\/em>, CPU<\/strong> ve memory<\/strong> gibi resource metriclerine dayanarak horizontally auto scaling sa\u011flamaktad\u0131r. KEDA<\/em> ile ise birden \u00e7ok metri\u011fi baz alarak horizontally auto scaling ger\u00e7ekle\u015ftirebilmekteyiz. KEDA<\/em> hakk\u0131nda bilgi edinebilmek i\u00e7in ise, daha \u00f6nce burada<\/a> <\/em>ele alm\u0131\u015f oldu\u011fum makaleye bir g\u00f6z atabilirsiniz.<\/p>\n

E\u011fer sizlerde benim gibi aktif olarak uygulamalar\u0131n\u0131z\u0131 kubernetes<\/em> ortam\u0131nda manage ediyorsan\u0131z, g\u00fczel noktalar\u0131n\u0131 es ge\u00e7ersek, infrastructure management ve configuration k\u0131sm\u0131n\u0131n u\u011fra\u015ft\u0131r\u0131c\u0131 oldu\u011funu biliyorsunuzdur. Azure Container Apps<\/em> ise kubernetes<\/em> taraf\u0131ndaki complexity’i ve gereken learning curve minimize edilerek, bizlere microservice-based uygulamalar\u0131m\u0131z\u0131 kolayca build ve host edebilece\u011fimiz fully managed bir ortam sa\u011flamaktad\u0131r.<\/p>\n

Azure Container Apps<\/em>‘i bir kubernetes<\/em> pod’u gibi d\u00fc\u015f\u00fcnebiliriz asl\u0131nda. Her bir Azure Container App <\/em>i\u00e7erisinde ayn\u0131 life-cycle’\u0131 payla\u015fan birden \u00e7ok container bar\u0131nd\u0131r\u0131labilmektedir. Ayr\u0131ca revision’lar ile de versioning sa\u011flanmaktad\u0131r. K\u0131sacas\u0131 bir container app deploy etti\u011fimizde, otomatik olarak bir revision olu\u015fturulmaktad\u0131r. Ayr\u0131ca herhangi bir de\u011fi\u015fiklik veya update i\u015flemi ger\u00e7ekle\u015ftirdi\u011fimizde de revision’lar olu\u015fturulmaktad\u0131r. Olu\u015fturulan revision’lar ise immutable’d\u0131r. Birden \u00e7ok farkl\u0131 revision’\u0131 ayn\u0131 anda \u00e7al\u0131\u015ft\u0131rabilmek ve trafi\u011fi istedi\u011fimiz gibi aralar\u0131nda b\u00f6lebilmek de m\u00fcmk\u00fcnd\u00fcr. Default olarak ise single revision mode’unda \u00e7al\u0131\u015fmaktad\u0131r.<\/p>\n

\"\"<\/a><\/p>\n

Ayr\u0131ca monitoring ve observability ise Log Analytics<\/em> arac\u0131l\u0131\u011f\u0131yla kolay bir \u015fekilde ger\u00e7ekle\u015ftirilebilmektedir. \u00d6zetle Azure Container Apps<\/em> kullanarak cloud infra management veya container orchestration gibi konulara kafa yormadan, microservice-based uygulamalar\u0131m\u0131z\u0131 kolay bir \u015fekilde build ve host edebiliriz.<\/p>\n

Component’ler ile Ba\u015flayal\u0131m<\/h2>\n

Bir \u00f6nceki makalede state-store<\/strong> ve pub\/sub<\/strong> i\u00e7in default gelen component’leri kullanm\u0131\u015ft\u0131k. Dapr<\/em>‘\u0131n pluggable bir yap\u0131ya sahip oldu\u011fundan ve component’leri herhangi bir kod de\u011fi\u015fikli\u011fi yapmadan bir ba\u015fka component ile de\u011fi\u015ftirebilmece\u011fimizden de bahsetmi\u015ftik.<\/p>\n

\u015eimdi ise state-store i\u00e7in Azure Cosmos DB<\/em>‘yi, pub\/sub i\u00e7in ise Azure Service Bus<\/em>‘\u0131 kullanaca\u011f\u0131z. Azure Service Bus<\/em>‘\u0131 olu\u015fturabilmek i\u00e7in buray\u0131<\/a><\/em>, Azure<\/em> Cosmos DB<\/em>‘yi olu\u015fturabilmek i\u00e7in ise buray\u0131<\/a><\/em> takip edebilirsiniz. Azure Cosmos DB<\/em>‘yi olu\u015ftururken “NoSQL API’<\/em>” se\u00e7ene\u011fini se\u00e7elim ve ard\u0131ndan “DaprShop<\/em>” database’ini ve “ShoppingCart<\/em>” container’\u0131n\u0131 da olu\u015ftural\u0131m. Ayr\u0131ca partition key olarak ise “\/id” se\u00e7ti\u011fimizden emin olal\u0131m. Ayr\u0131ca Dapr<\/em>‘\u0131n pub\/sub component’i i\u00e7in topic’lere ihtiyac\u0131m\u0131z olaca\u011f\u0131 i\u00e7in, Azure Service Bus<\/em>‘\u0131 olu\u015ftururken ise tier olarak “standard” \u0131 se\u00e7memiz gerekmektedir.<\/p>\n

Azure<\/em> service’lerini olu\u015fturduktan sonra \u00f6ncelikle \u00f6rnek projenin root klas\u00f6r\u00fc olan “DaprShop<\/em>” klas\u00f6r\u00fc alt\u0131nda “Components<\/em>” ad\u0131nda bir yeni klas\u00f6r olu\u015ftural\u0131m. Bu klas\u00f6r i\u00e7erisinde microservice’lerimiz \u00f6zelinde ihtiyac\u0131m\u0131z olan component’leri tan\u0131mlayaca\u011f\u0131z.<\/p>\n

\u0130lk olarak pub\/sub component’i ile ba\u015flayal\u0131m. Bunun i\u00e7in klas\u00f6r i\u00e7erisinde “pubsub.yaml<\/em>” ad\u0131nda a\u015fa\u011f\u0131daki gibi bir dosya olu\u015ftural\u0131m.<\/p>\n

componentType: pubsub.azure.servicebus\r\nversion: v1\r\nmetadata:\r\n  - name: connectionString\r\n    secretRef: connection-string-key\r\nsecrets:\r\n- name: connection-string-key\r\n  value: \"Endpoint=sb:\/\/dapr-poc-sbus.servicebus.windows.net\/;SharedAccessKeyName=YOUR_SHARED_ACCESS_KEU_NAME;SharedAccessKey=YOUR_SHARED_ACCESS_KEY\"<\/pre>\n
E\u011fer Dapr<\/em> component schema’s\u0131n\u0131 bir \u00f6nceki makaleden hala hat\u0131rl\u0131yorsak, bu sefer schema’n\u0131n biraz daha sade oldu\u011funu fark etmi\u015fizdir. Azure Container Apps<\/em> daha sadele\u015ftirilmi\u015f bir component schema’s\u0131 kullanmaktad\u0131r.<\/p>\n
NOT<\/strong>: <\/em>Schema ile ilgili daha detayl\u0131 kullan\u0131m bilgilerine ise, buradan<\/a><\/em> eri\u015febilirsiniz.<\/p><\/blockquote>\n
Olu\u015fturmu\u015f oldu\u011fumuz bu pub\/sub component’i i\u00e7erisinde tek g\u00fcncellememiz gereken nokta, Azure Service Bus<\/em>‘\u0131n “connectionStringKey<\/em>” bilgisidir.<\/p>\n
Ayr\u0131ca Azure-hosted<\/em> resource’lara eri\u015firken dilersek managed identity<\/strong> de kullanabiliriz. Azure-hosted<\/em> olmayan resource’lar i\u00e7in ise, Dapr<\/em> secret store component’inden yararlanabilir ve Azure Key Vault<\/em> integration’\u0131 ile birlikte secret’lar\u0131 kolay bir \u015fekilde y\u00f6netebiliriz. B\u00f6ylece secret bilgilerini component i\u00e7erisinde a\u00e7\u0131k bir \u015fekilde tan\u0131mlamam\u0131za gerek kalmayacakt\u0131r.<\/p>\n
\u015eimdi ise “statestore.yaml<\/em>” ad\u0131nda bir dosya olu\u015ftural\u0131m.<\/p>\n
componentType: state.azure.cosmosdb\r\nversion: v1\r\nmetadata:\r\n- name: url\r\n  value: https:\/\/dapr-poc-cosmosstate.documents.azure.com:443\/\r\n- name: masterkey\r\n  secretRef: cosmos-master-key\r\n- name: database\r\n  value: DaprShop\r\n- name: collection\r\n  value: ShoppingCart\r\nsecrets:\r\n- name: cosmos-master-key\r\n  value: \"YOUR_COSMOS_MASTER_KEY\"<\/pre>\n
Burada ise olu\u015fturmu\u015f oldu\u011fumuz Azure Cosmos DB<\/em>‘nin ilgili “url<\/em>“, “masterKey<\/em>“, “database<\/em>” ve “collection<\/em>” gibi bilgilerini belirtmemiz, state-store olarak kullanabilmemiz i\u00e7in yeterli olacakt\u0131r.<\/p>\n
G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi farkl\u0131 component’leri tan\u0131mlayabilmek bu kadar kolay. Ayr\u0131ca component’ler \u00f6zelinde “scope” lar belirleyebilmek de m\u00fcmk\u00fcnd\u00fcr. B\u00f6ylece Dapr<\/em> sidecar sadece ilgili scope’daki container app’ler i\u00e7in ilgili component’leri load etmektedir. Bu i\u015flemi ise a\u015fa\u011f\u0131daki \u015fekilde ger\u00e7ekle\u015ftirebiliriz.<\/p>\n
scopes:\r\n  - [DAPR-APP-ID-1]\r\n  - [DAPR-APP-ID-2]<\/pre>\n
Scope belirtilmedi\u011finde ise ayn\u0131 environment i\u00e7erisindeki Azure Container App’ler<\/em> deploy edilmi\u015f t\u00fcm component’leri default olarak load etmektedir.<\/p>\n
\u015eimdi Azure Container Apps<\/em> environment ve Azure Container App<\/em> olu\u015fturma i\u015flemlerine ge\u00e7ebiliriz ve ard\u0131ndan olu\u015fturmu\u015f oldu\u011fumuz component’lerin ve microservice’lerimizin deployment i\u015flemlerini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n
Azure Container Apps Env ve Container App Olu\u015ftural\u0131m<\/h2>\n
Deployment’a ba\u015flamadan \u00f6nce ilk olarak bir Azure Container Apps<\/em> environment’\u0131 olu\u015fturmam\u0131z gerekmektedir. Azure Container Apps<\/em> environment’\u0131 birden \u00e7ok Azure Container App<\/em> bar\u0131nd\u0131ran bir secure boundary olarak d\u00fc\u015f\u00fcnebiliriz. Ayn\u0131 environment i\u00e7erisine deploy edilen Azure Container App<\/em>‘ler, ayn\u0131 virtual network i\u00e7erisine deploy olmaktad\u0131rlar ve ayn\u0131 Azure Log Analytics<\/em> workspace’ini payla\u015fmaktad\u0131rlar.<\/p>\n
\"\"<\/a>\u015eimdi \u00f6ncelikle a\u015fa\u011f\u0131daki gibi CLI<\/em> \u00fczerinden bir resource grup olu\u015ftural\u0131m.<\/p>\n
az group create --name daprshop-rg --location \"westeurope\"<\/pre>\n
Ard\u0131ndan Azure Container Apps<\/em> environment’\u0131n\u0131 olu\u015ftural\u0131m.<\/p>\n
az containerapp env create \\\r\n--name daprshop-env \\\r\n--resource-group daprshop-rg \\\r\n--location \"westeurope\"<\/pre>\n
NOT<\/strong><\/em>: E\u011fer daha \u00f6nce “containerapp<\/em>” extension’\u0131na sahip olmad\u0131ysan\u0131z, yukar\u0131daki komut \u00f6ncelikle bu extension’\u0131n kurulumunu ger\u00e7ekle\u015ftirecektir. Dilerseniz bu i\u015flemi \u00f6ncesinde de ger\u00e7ekle\u015ftirebilirsiniz. “az extension add –name containerapp –upgrade<\/em>“<\/p><\/blockquote>\n
\"\"<\/a><\/p>\n
\u015eimdi olu\u015fturmu\u015f oldu\u011fumuz “daprshop-env<\/em>” isimli Azure Container Apps<\/em> environment’\u0131 i\u00e7erisinde yukar\u0131da tan\u0131mlam\u0131\u015f oldu\u011fumuz pub\/sub ve state-store component’lerini configure edelim.<\/p>\n
Bunun i\u00e7in CLI<\/em> \u00fczerinden “DaprShop<\/em>” klas\u00f6r\u00fc alt\u0131nda bulunan “Components<\/em>” path’ine gidelim ve a\u015fa\u011f\u0131daki komutlar\u0131 kullanarak ilgili component’leri olu\u015fturmu\u015f oldu\u011fumuz environment i\u00e7in configure edelim.<\/p>\n
az containerapp env dapr-component set \\\r\n--name daprshop-env \\\r\n--resource-group daprshop-rg \\\r\n--dapr-component-name statestore \\\r\n--yaml statestore.yaml<\/pre>\n
az containerapp env dapr-component set \\\r\n--name daprshop-env \\\r\n--resource-group daprshop-rg \\\r\n--dapr-component-name pubsub \\\r\n--yaml pubsub.yaml<\/pre>\n
Ayr\u0131ca daha \u00f6nce \u00f6rnek projemiz i\u00e7erisinde bu component’lere eri\u015firken default olan “statestore<\/em>” ve “pubsub<\/em>” isimlerini kulland\u0131\u011f\u0131m\u0131z i\u00e7in, bu environment i\u00e7erisinde de isimlerini “statestore<\/em>” ve “pubsub<\/em>” olarak ayn\u0131 \u015fekilde koruyoruz.<\/p>\n
\u0130lgili env i\u00e7in configure edilen component’lere ister a\u015fa\u011f\u0131daki komutu kullanarak, istersek de Azure<\/em> portal \u00fczerinden Container Apps Environment<\/em> resource’una giderek eri\u015febiliriz.<\/p>\n
az containerapp env dapr-component list  \\\r\n--name \"daprshop-env\" \\\r\n--resource-group \"daprshop-rg\"<\/pre>\n
Bu noktaya kadar Azure Container Apps<\/em> environment’\u0131n\u0131 kullanmak istedi\u011fimiz Dapr<\/em> component’leri ile birlikte haz\u0131rlam\u0131\u015f olduk. \u015eimdi ise geriye sadece \u00f6rnek projelerimiz olan ShoppingCart<\/em> ve Recommendation <\/em>microservice’lerinin Azure Container App<\/em>‘e deployment i\u015flemleri kald\u0131.<\/p>\n
Deployment i\u015flemine ge\u00e7meden \u00f6nce \u00f6rnek microservice’lerimizi containerize bir hale getirmemiz ve bir container registry’e push etmemiz gerekmektedir. Ben bu i\u015flemi daha \u00f6nce olu\u015fturmu\u015f oldu\u011fum Azure Container Registry<\/em> \u00fczerinden ger\u00e7ekle\u015ftirece\u011fim. E\u011fer sizde bir container registry olu\u015fturmak isterseniz, buraya<\/a><\/em> g\u00f6z atabilirsiniz.<\/p>\n
Ek olarak ShoppingCart<\/em> ve Recommendation<\/em> microservice’lerinin “Program.cs<\/em>” dosyas\u0131na gidelim ve “app.Run();” komutu i\u00e7erisinde daha \u00f6nce yazd\u0131\u011f\u0131m\u0131z specific portlar\u0131 silelim ve microservice’lerin default port 80 \u00fczerinden \u00e7al\u0131\u015fabilmelerine izin verelim.<\/p>\n
Ayr\u0131ca kullanacak oldu\u011fum Dockerfile’lar<\/em> ise a\u015fa\u011f\u0131daki gibidir.<\/p>\n
Recommendation.API<\/strong><\/p>\n
FROM mcr.microsoft.com\/dotnet\/aspnet:6.0 AS base\r\nWORKDIR \/app\r\nEXPOSE 80\r\n\r\nFROM mcr.microsoft.com\/dotnet\/sdk:6.0 AS build\r\nWORKDIR \/src\r\nCOPY [\"DaprShop.Recommendation.API\/DaprShop.Recommendation.API.csproj\", \"DaprShop.Recommendation.API\/\"]\r\nCOPY [\"DaprShop.Contracts\/DaprShop.Contracts.csproj\", \"DaprShop.Contracts\/\"]\r\nRUN dotnet restore \"DaprShop.Recommendation.API\/DaprShop.Recommendation.API.csproj\"\r\nCOPY . .\r\nWORKDIR \"\/src\/DaprShop.Recommendation.API\"\r\nRUN dotnet build \"DaprShop.Recommendation.API.csproj\" -c Release -o \/app\/build\r\n\r\nFROM build AS publish\r\nRUN dotnet publish \"DaprShop.Recommendation.API.csproj\" -c Release -o \/app\/publish \/p:UseAppHost=false\r\n\r\nFROM base AS final\r\nWORKDIR \/app\r\nCOPY --from=publish \/app\/publish .\r\nENTRYPOINT [\"dotnet\", \"DaprShop.Recommendation.API.dll\"]\r\n<\/pre>\n
ShoppingCart.API<\/strong><\/p>\n
FROM mcr.microsoft.com\/dotnet\/aspnet:6.0 AS base\r\nWORKDIR \/app\r\nEXPOSE 80\r\n\r\nFROM mcr.microsoft.com\/dotnet\/sdk:6.0 AS build\r\nWORKDIR \/src\r\nCOPY [\"DaprShop.ShoppingCart.API\/DaprShop.ShoppingCart.API.csproj\", \"DaprShop.ShoppingCart.API\/\"]\r\nCOPY [\"DaprShop.Contracts\/DaprShop.Contracts.csproj\", \"DaprShop.Contracts\/\"]\r\nRUN dotnet restore \"DaprShop.ShoppingCart.API\/DaprShop.ShoppingCart.API.csproj\"\r\nCOPY . .\r\nWORKDIR \"\/src\/DaprShop.ShoppingCart.API\"\r\nRUN dotnet build \"DaprShop.ShoppingCart.API.csproj\" -c Release -o \/app\/build\r\n\r\nFROM build AS publish\r\nRUN dotnet publish \"DaprShop.ShoppingCart.API.csproj\" -c Release -o \/app\/publish \/p:UseAppHost=false\r\n\r\nFROM base AS final\r\nWORKDIR \/app\r\nCOPY --from=publish \/app\/publish .\r\nENTRYPOINT [\"dotnet\", \"DaprShop.ShoppingCart.API.dll\"]<\/pre>\n
Containerization i\u015flemini her iki \u00f6rnek microservice i\u00e7in ger\u00e7ekle\u015ftirdikten sonra, a\u015fa\u011f\u0131daki gibi s\u0131ras\u0131yla Azure Container App<\/em> ‘e deployment i\u015flemlerini ger\u00e7ekle\u015ftirebiliriz.<\/p>\n
az containerapp create \\\r\n  --name \"recommendation-api\"  \\\r\n  --resource-group \"daprshop-rg\" \\\r\n  --environment \"daprshop-env\" \\\r\n  --image \"YOUR_ACR_NAME.azurecr.io\/daprshop.recommendationapi:01\" \\\r\n  --registry-server \"YOUR_ACR_NAME.azurecr.io\" \\\r\n  --target-port 80 \\\r\n  --ingress 'external' \\\r\n  --min-replicas 1 \\\r\n  --max-replicas 1 \\\r\n  --enable-dapr \\\r\n  --cpu 0.25 \\\r\n  --memory 0.5Gi \\\r\n  --dapr-app-id recommendationapi \\\r\n  --dapr-app-port 80<\/pre>\n
  az containerapp create \\\r\n  --name \"shoppingcart-api\"  \\\r\n  --resource-group \"daprshop-rg\" \\\r\n  --environment \"daprshop-env\" \\\r\n  --image \"YOUR_ACR_NAME.azurecr.io\/daprshop.shoppingcartapi:01\" \\\r\n  --registry-server \"YOUR_ACR_NAME.azurecr.io\" \\\r\n  --target-port 80 \\\r\n  --ingress 'external' \\\r\n  --min-replicas 1 \\\r\n  --max-replicas 1 \\\r\n  --enable-dapr \\\r\n  --cpu 0.25 \\\r\n  --memory 0.5Gi \\\r\n  --dapr-app-id shoppingcartapi \\\r\n  --dapr-app-port 80<\/pre>\n
Yukar\u0131daki parametrelerin baz\u0131lar\u0131n\u0131 k\u0131saca a\u00e7\u0131klamak gerekirse;<\/p>\n