<\/div>\n

Merhaba,<\/p>\n

Bu i\u00e7eri\u011fimizde microservice yakla\u015f\u0131m\u0131n\u0131 benimseyen bir uygulamada, client taraf\u0131ndan gelen istekleri ilgili servislere y\u00f6nlendirme sorumlulu\u011funu \u00fcstlenen API Gateway yap\u0131lanmalar\u0131ndan a\u00e7\u0131k kaynak olan Ocelot k\u00fct\u00fcphanesiyle tan\u0131\u015facak ve nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 inceleyece\u011fiz.<\/p>\n

\n\u00d6ncelikle API Gateway Nedir?<\/em> sorusuna kar\u015f\u0131l\u0131k klavyeye alm\u0131\u015f oldu\u011fumuz Microservice Mimarisinde API Gateway Nedir?<\/a> ba\u015fl\u0131kl\u0131 makalemizi incelemenizi, ard\u0131ndan bu i\u00e7eri\u011fi okuman\u0131z\u0131 tavsiye ederim.<\/strong>\n<\/div>\n
Ocelot Nedir?<\/h3>\n
$\".NET$ <\/a>Microservice yap\u0131lanmas\u0131n\u0131 benimseyen uygulamalarda clientlardan gelen istekleri i\u015flevsel a\u00e7\u0131dan uygun servislere y\u00f6nlendirmekten sorumlu bir ge\u00e7i\u015f g\u00f6revi g\u00f6ren API Gateway k\u00fct\u00fcphanesidir. Ocelot, clienttan gelen istek neticesinde olu\u015fturulan HttpRequest nesnesini arkaplandaki servislere iletebilmek i\u00e7in HttpRequestMessage nesnesi olu\u015fturmakta ve bu \u015fekilde ula\u015ft\u0131rmakla g\u00f6revli middleware’dir. Ocelot, uygulaman\u0131n pipeline’\u0131nda ki son ara katmand\u0131r diyebiliriz ve bu y\u00fczden bir sonraki middleware \u00e7a\u011fr\u0131lmamaktad\u0131r.<\/p>\n
Ocelot’\u0131n Kullan\u0131ld\u0131\u011f\u0131 Deploy Tasar\u0131mlar\u0131<\/h3>\n
Ocelot a\u015fa\u011f\u0131daki gibi da\u011f\u0131t\u0131mlarda kullan\u0131lmaktad\u0131r.<\/p>\n\n\n\n\n\n\n
Basit
\nUygulamalarda<\/th>\n IdentityServer
\nKullan\u0131ld\u0131\u011f\u0131nda<\/th>\n \u00c7oklu Instance
\nDurumlar\u0131mda<\/th>\n<\/tr>\n<\/thead>\n
$\".NET$ <\/a><\/td>\n $\".NET$ <\/a><\/td>\n $\".NET$ <\/a><\/td>\n<\/tr>\n
Birden fazla service’in kullan\u0131ld\u0131\u011f\u0131 durumlarda client taraf\u0131ndan gelen istekleri ilgili servislere y\u00f6nlendirmektedir.<\/td>\n IdentityServer kullan\u0131lan bir uygulamada, Ocelot token talebi i\u00e7in gerekli y\u00f6nlendirmeyi yapmakta ve al\u0131nan token ile birlikte yap\u0131lan istekleri ba\u015far\u0131yla ilgili microservislere y\u00f6nlendirmektedir.<\/td>\n Load Balancer arac\u0131l\u0131\u011f\u0131yla birden fazla instance \u00fczerinden istekleri kar\u015f\u0131layabilmekte ve ilgili servislere da\u011f\u0131tabilmektedir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n
Consul Kullan\u0131ld\u0131\u011f\u0131nda<\/th>\n Service Fabric Kullan\u0131ld\u0131\u011f\u0131nda<\/th>\n<\/tr>\n<\/thead>\n
$\".NET$ <\/a><\/td>\n $\".NET$ <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Peki Ocelot Nerelerde Kullan\u0131lmaktad\u0131r?<\/h3>\n
Ocelot a\u015fa\u011f\u0131daki gibi bir\u00e7ok yetene\u011fe sahip olan bir k\u00fct\u00fcphanedir.<\/p>\n
\n
Routing<\/li>\n
Request Aggregation<\/li>\n
Service Discovery with Consul & Eureka<\/li>\n
Service Fabric<\/li>\n
Kubernetes<\/li>\n
WebSockets<\/li>\n
Authentication<\/li>\n
Authorisation<\/li>\n
Rate Limiting<\/li>\n
Caching<\/li>\n
Retry policies \/ QoS<\/li>\n
Load Balancing<\/li>\n
Logging \/ Tracing \/ Correlation<\/li>\n
Headers \/ Method \/ Query String \/ Claims Transformation<\/li>\n
Custom Middleware \/ Delegating Handlers<\/li>\n
Configuration \/ Administration REST API<\/li>\n
Platform \/ Cloud Agnostic<\/li>\n<\/ul>\n
Ocelot Nas\u0131l Kullan\u0131l\u0131r?<\/h3>\n
Ocelot k\u00fct\u00fcphanesinin kullan\u0131m\u0131n\u0131 \u00f6rneklendirebilmek i\u00e7in \u00f6ncelikle basit seviyede bir microservice \u00f6rneklendirmesinde bulunmam\u0131z gerekmektedir.<\/p>\n
\u00d6rnek Senaryo Haz\u0131rl\u0131\u011f\u0131<\/h4>\n
Bunun i\u00e7in a\u015fa\u011f\u0131daki gibi ‘ProductAPI’ ve ‘CostumerAPI’ olmak \u00fczere iki proje olu\u015ftural\u0131m.
\ndotnet new webapi --name productAPI<\/code> \ndotnet new webapi --name customerAPI<\/code><\/p>\n
\u015eimdi bu projelere i\u015flevsel \u00f6zellik kazand\u0131rabilmek i\u00e7in s\u0131ras\u0131yla ‘ProductController’ ve ‘CustomerController’ isimli controller s\u0131n\u0131flar\u0131 ekleyelim ve i\u00e7eriklerini a\u015fa\u011f\u0131daki gibi in\u015fa edelim.<\/p>\n
ProductAPI;<\/p>\n
\r\n [ApiController]\r\n [Route("api\/[controller]")]\r\n public class ProductController : ControllerBase\r\n {\r\n public IActionResult Get()\r\n {\r\n return Ok(new List<string> { "Kalem", "Kitap", "Silgi", "Defter" });\r\n }\r\n }\r\n<\/pre>\nCustomerAPI;<\/p>\n\r\n [ApiController]\r\n [Route("api\/[controller]")]\r\n public class CustomerController : ControllerBase\r\n {\r\n public IActionResult Get()\r\n {\r\n return Ok(new List<string> { "Hilmi Celayir", "Saniye Y\u0131ld\u0131z", "Nevin Y\u0131ld\u0131z", "Fatih Y\u0131lmaz" });\r\n }\r\n }\r\n<\/pre>\nArd\u0131ndan her iki projeye localde \u00e7al\u0131\u015f\u0131laca\u011f\u0131ndan dolay\u0131 uygun bir port tan\u0131mlayal\u0131m. Tabi bu i\u015flem i\u00e7in ister ‘Program.cs’ dosyas\u0131n\u0131 istersenizde ‘launchSettings.json’ dosyas\u0131ndaki profilleri kullanabilirsiniz. Ben \u00f6rneklendirme olarak ‘launchSettings.json’ dosyas\u0131n\u0131 se\u00e7iyorum.<\/p>\n ProductAPI;<\/p>\n\r\n "productAPI": {\r\n "commandName": "Project",\r\n "launchBrowser": true,\r\n "launchUrl": "weatherforecast",\r\n "applicationUrl": "https:\/\/localhost:5003;http:\/\/localhost:5002",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n<\/pre>\nCustomerAPI;<\/p>\n\r\n "customerAPI": {\r\n "commandName": "Project",\r\n "launchBrowser": true,\r\n "launchUrl": "weatherforecast",\r\n "applicationUrl": "https:\/\/localhost:5001;http:\/\/localhost:5000",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n<\/pre>\nEvet… Art\u0131k microservicelerimiz haz\u0131r. Bundan sonra clientlardan gelecek olan istekleri tek elden kar\u015f\u0131layabilecek ve iste\u011fe uygun ilgili servise y\u00f6nlendirecek olan api gateway projesini tasarlayal\u0131m.<\/p>\n Ocelot Entegrasyonu ve Konfig\u00fcrasyonu<\/h4>\n\u0130lk olarak ‘GatewayAPI’ isimli projemizi olu\u015ftural\u0131m. \ndotnet new webapi --name getwayAPI<\/code><\/p>\n Bu projemizde localde \u00e7al\u0131\u015faca\u011f\u0131ndan dolay\u0131 portuna el atal\u0131m;<\/p>\n \r\n "getwayAPI": {\r\n "commandName": "Project",\r\n "launchBrowser": true,\r\n "launchUrl": "weatherforecast",\r\n "applicationUrl": "https:\/\/localhost:5005;http:\/\/localhost:5004",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n<\/pre>\nArd\u0131ndan Ocelot k\u00fct\u00fcphanesini a\u015fa\u011f\u0131daki kodu terminalde \u00e7al\u0131\u015ft\u0131rarak ilgili projeye dahil edelim. (Nuget Ocelot<\/a>) \ndotnet add package Ocelot<\/code><\/p>\n Bu i\u015flemden sonra uygulaman\u0131n herhangi bir dizininde(genellikle root tercih edilir) yap\u0131land\u0131rmay\u0131 konfig\u00fcre edebilmek i\u00e7in ‘ocelot.json’ isminde bir dosya olu\u015ftural\u0131m ve i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi temel ve en sade bi\u00e7imde olacak \u015fekilde in\u015fa edelim. Bu kullan\u0131m Ocelot’a dair herhangi bir aktivite sergilemese de ilgili k\u00fct\u00fcphaneyi aktifle\u015ftirmek i\u00e7in yeterli olacakt\u0131r.<\/p>\n \r\n{\r\n "Routes": [],\r\n "GlobalConfiguration": {\r\n "BaseUrl": "https:\/\/localhost:5005"\r\n }\r\n}\r\n<\/pre>\nBurada ‘GlobalConfiguration’ i\u00e7erisindeki ‘BaseUrl’ api gateway uygulamas\u0131 i\u00e7in esas url’i bildirmektedir. Bu projenin Ocelot k\u00fct\u00fcphanesi arac\u0131l\u0131\u011f\u0131yla microservislere eri\u015fimi sa\u011flayabilmesi i\u00e7in a\u015fa\u011f\u0131daki gibi konfig\u00fcrasyonda bulunulmas\u0131 gerekmektedir.<\/p>\n\r\n{\r\n "Routes": [\r\n {\r\n "DownstreamPathTemplate": "\/api\/customer",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5001\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/api\/gateway\/customer",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n },\r\n {\r\n "DownstreamPathTemplate": "\/api\/product",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5003\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/api\/gateway\/product",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n }\r\n ],\r\n "GlobalConfiguration": {\r\n "BaseUrl": "https:\/\/localhost:5005"\r\n }\r\n}\r\n<\/pre>\nYukar\u0131daki konfig\u00fcrasyonu izah etmemiz gerekirse e\u011fer;<\/p>\n\nDownstreamPathTemplate<\/strong> \nY\u00f6nlendirme yap\u0131lacak microservice’in route’unu tutmaktad\u0131r.\n<\/li>\n DownstreamScheme<\/strong> \n\u0130lgili microservice’e yap\u0131lacak iste\u011fin hangi protokol \u00fczerinden ger\u00e7ekle\u015ftirilece\u011fini bildirmektedir.\n<\/li>\n DownstreamHostAndPorts<\/strong> \nMicroservice’in ‘Host’ ve ‘Port’ bilgilerini tutmaktad\u0131r.\n<\/li>\n UpstreamPathTemplate<\/strong> \nAPI Gateway \u00fczerinden microservice’e yap\u0131lacak y\u00f6nlendirmenin route’unu tutmaktad\u0131r.\n<\/li>\nUpstreamHttpMethod<\/strong> \nHangi isteklerin yap\u0131labilece\u011fi bildirilmektedir.\n<\/li>\n<\/ul>\n\u015feklinde tan\u0131mlama yapabiliriz.<\/p>\n Tabi i\u00e7erisini bu \u015fekilde konfig\u00fcre etti\u011fimiz ‘ocelot.json’ dosyas\u0131n\u0131 ‘Program.cs’ dosyas\u0131 \u00fczerinden uygulamaya a\u015fa\u011f\u0131daki gibi dahil etmemiz gerekmektedir.<\/p>\n\r\n public class Program\r\n {\r\n public static void Main(string[] args)\r\n {\r\n CreateHostBuilder(args).Build().Run();\r\n }\r\n\r\n public static IHostBuilder CreateHostBuilder(string[] args) =>\r\n Host.CreateDefaultBuilder(args)\r\n .ConfigureAppConfiguration((hosting, config) =>\r\n {\r\n config.AddJsonFile("ocelot.json", false, true);\r\n })\r\n .ConfigureWebHostDefaults(webBuilder =>\r\n {\r\n webBuilder.UseStartup<Startup>();\r\n });\r\n }\r\n<\/pre>\nAyriyetten ‘Startup.cs’ dosyas\u0131nda da programatik olarak servis entegrasyonunu ve middleware \u00e7a\u011fr\u0131s\u0131n\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\r\n public class Startup\r\n {\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n .\r\n .\r\n .\r\n services.AddOcelot();\r\n .\r\n .\r\n .\r\n }\r\n async public void Configure(IApplicationBuilder app, IWebHostEnvironment env)\r\n {\r\n .\r\n .\r\n .\r\n await app.UseOcelot();\r\n .\r\n .\r\n .\r\n }\r\n }\r\n<\/pre>\nTest Edelim<\/h4>\n\u015eu ana kadar yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmay\u0131 test edersek e\u011fer; \n<\/a> \n\u015feklinde bir sonu\u00e7la kar\u015f\u0131la\u015faca\u011f\u0131z.<\/p>\n Parametreli Y\u00f6nlendirme<\/h4>\nMicroservice rotalar\u0131n\u0131n parametre ald\u0131\u011f\u0131 durumlarda ilgili parametre de\u011feriyle birlikte y\u00f6nlendirmeyi ger\u00e7ekle\u015ftirebilmek i\u00e7in a\u015fa\u011f\u0131daki gibi route tan\u0131mlanmas\u0131 gerekmektedir.<\/p>\n\r\n {\r\n "DownstreamPathTemplate": "\/api\/product\/{id}",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5003\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/api\/gateway\/product\/{id}",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n }\r\n<\/pre>\nBu yap\u0131lanma \u00fczerinden a\u015fa\u011f\u0131daki gibi bir url \u00fczerinden istek g\u00f6nderildi\u011fi taktirde hedef servis tetiklenmektedir. \nhttps:\/\/localhost:5005\/api\/gateway\/product\/1<\/strong><\/code><\/p>\nT\u00fcm \u0130steklerin Yakalanmas\u0131<\/h4>\nA\u015fa\u011f\u0131daki gibi bir tasar\u0131m, yap\u0131lan t\u00fcm isteklerin do\u011frudan proxy \u00fczerinden y\u00f6nlendirilmesini sa\u011flayacakt\u0131r.<\/p>\n\r\n {\r\n "DownstreamPathTemplate": "\/{url}",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5003\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/{url}",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n }\r\n<\/pre>\n\u00d6rne\u011fin; \nhttps:\/\/localhost:5005\/api\/product<\/strong><\/code> adresine yap\u0131lan iste\u011fi https:\/\/localhost:5003\/api\/product<\/strong><\/code> adresine y\u00f6nlendirecektir.<\/p>\n Benzer mant\u0131kla;<\/p>\n\r\n {\r\n "DownstreamPathTemplate": "\/{url}",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5003\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/p\/{url}",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n },\r\n {\r\n "DownstreamPathTemplate": "\/{url}",\r\n "DownstreamScheme": "https",\r\n "DownstreamHostAndPorts": [\r\n {\r\n "Host": "localhost",\r\n "Port": 5001\r\n }\r\n ],\r\n "UpstreamPathTemplate": "\/c\/{url}",\r\n "UpstreamHttpMethod": [ "Get" ]\r\n }\r\n<\/pre>\nhttps:\/\/localhost:5005\/p\/api\/product<\/strong><\/code> adresine yap\u0131lan iste\u011fi https:\/\/localhost:5003\/api\/product<\/strong><\/code> adresine, https:\/\/localhost:5005\/c\/api\/customer<\/strong><\/code> adresine yap\u0131lan iste\u011fi https:\/\/localhost:5001\/api\/customer<\/strong><\/code> adresine y\u00f6nlendirilecektir.<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\nNot : \u00d6rnek dosyay\u0131 indirmek i\u00e7in buraya<\/a> t\u0131klay\u0131n\u0131z.<\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Bu i\u00e7eri\u011fimizde microservice yakla\u015f\u0131m\u0131n\u0131 benimseyen bir uygulamada, client taraf\u0131ndan gelen istekleri ilgili servislere y\u00f6nlendirme sorumlulu\u011funu \u00fcstlenen API Gateway yap\u0131lanmalar\u0131ndan a\u00e7\u0131k kaynak olan Ocelot k\u00fct\u00fcphanesiyle tan\u0131\u015facak ve nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 inceleyece\u011fiz. \u00d6ncelikle API Gateway Nedir?...<\/p>\n","protected":false},"author":1,"featured_media":16497,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3573],"tags":[3587,3579,3289,3588,3586,3585],"class_list":["post-16427","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microservices","tag-net-core-microservices","tag-api-gateway","tag-microservices","tag-ocelot-api-gateway","tag-ocelot-microservices","tag-ocelot-nedir"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16427","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=16427"}],"version-history":[{"count":65,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16427\/revisions"}],"predecessor-version":[{"id":16500,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16427\/revisions\/16500"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/16497"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=16427"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=16427"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=16427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Peki Ocelot Nerelerde Kullan\u0131lmaktad\u0131r?<\/h3>\nOcelot a\u015fa\u011f\u0131daki gibi bir\u00e7ok yetene\u011fe sahip olan bir k\u00fct\u00fcphanedir.<\/p>\n

Ocelot Nas\u0131l Kullan\u0131l\u0131r?<\/h3>\nOcelot k\u00fct\u00fcphanesinin kullan\u0131m\u0131n\u0131 \u00f6rneklendirebilmek i\u00e7in \u00f6ncelikle basit seviyede bir microservice \u00f6rneklendirmesinde bulunmam\u0131z gerekmektedir.<\/p>\n

Test Edelim<\/h4>\n\u015eu ana kadar yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmay\u0131 test edersek e\u011fer;\n<\/a>\n\u015feklinde bir sonu\u00e7la kar\u015f\u0131la\u015faca\u011f\u0131z.<\/p>\n

Ocelot Nas\u0131l Kullan\u0131l\u0131r?<\/h3>\n
Ocelot k\u00fct\u00fcphanesinin kullan\u0131m\u0131n\u0131 \u00f6rneklendirebilmek i\u00e7in \u00f6ncelikle basit seviyede bir microservice \u00f6rneklendirmesinde bulunmam\u0131z gerekmektedir.<\/p>\n

Test Edelim<\/h4>\n
\u015eu ana kadar yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmay\u0131 test edersek e\u011fer;
\n $\".NET$ <\/a>
\n\u015feklinde bir sonu\u00e7la kar\u015f\u0131la\u015faca\u011f\u0131z.<\/p>\n