{"id":16322,"date":"2020-07-12T11:57:43","date_gmt":"2020-07-12T11:57:43","guid":{"rendered":"https:\/\/www.gencayyildiz.com\/blog\/?p=16322"},"modified":"2020-07-12T11:57:43","modified_gmt":"2020-07-12T11:57:43","slug":"event-driven-yontemi-ile-microservice-mimarisinde-haberlesme-rabbitmq-cap","status":"publish","type":"post","link":"https:\/\/www.gencayyildiz.com\/blog\/event-driven-yontemi-ile-microservice-mimarisinde-haberlesme-rabbitmq-cap\/","title":{"rendered":"Event Driven Y\u00f6ntemi \u0130le Microservice Mimarisinde Haberle\u015fme – RabbitMQ – CAP"},"content":{"rendered":"

<\/div>\n

Merhaba,<\/p>\n

Bu i\u00e7eri\u011fimizde Microservice<\/a> mimarilerde servislerin kendi aralar\u0131nda haberle\u015febilmesi i\u00e7in Event Driven y\u00f6nteminin nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve kullan\u0131ld\u0131\u011f\u0131n\u0131 ele alaca\u011f\u0131z.<\/p>\n

Microservice’lerde Event Driven Nedir?<\/h3>\n
Her bir servisin i\u015flevsel a\u00e7\u0131dan yapaca\u011f\u0131 operasyon neticesinde bir event’i fire ederek sonucu\/de\u011feri\/neticeyi herhangi bir message queue(RabbitMQ, Kafka vs.) sistemine atarak bu kuyruklar\u0131 dinleyen di\u011fer servisleri uyarmas\u0131d\u0131r.<\/p>\n
Event Driven’\u0131n Avantajlar\u0131 Nelerdir?<\/h3>\n
\n
Gev\u015fek ba\u011fl\u0131(loosely coupled) bir mimari olu\u015fturulmas\u0131na olanak sa\u011flar.<\/li>\n
Servisler aras\u0131nda asenkron bir ileti\u015fim sa\u011flanaca\u011f\u0131 i\u00e7in performans\u0131 artt\u0131r\u0131r.<\/li>\n
Servisler aras\u0131nda mesajla\u015fma sistemleri kullan\u0131laca\u011f\u0131ndan dolay\u0131, event fire edildi\u011fi taktirde consumer servis’e bir sebepten dolay\u0131 eri\u015filemezse e\u011fer kuyruk verinin kal\u0131c\u0131l\u0131\u011f\u0131n\u0131 sa\u011flayacak ve tekrar eri\u015filebilir olunca t\u00fcketim devam edecektir. B\u00f6ylece s\u00fcre\u00e7te veri kayb\u0131 ya\u015famaks\u0131z\u0131n sa\u011fl\u0131kl\u0131 i\u015flevsellik s\u00f6z konusu olacakt\u0131r.<\/li>\n
\u00d6l\u00e7eklenebilirlik(scalability) sa\u011flar.<\/li>\n<\/ul>\n
RabbitMQ Nedir? Nas\u0131l Kullanaca\u011f\u0131z?<\/h3>\n
RabbitMQ’nun ne oldu\u011fu ve nas\u0131l kullan\u0131ld\u0131\u011f\u0131na dair uzun uzun kaleme ald\u0131\u011f\u0131m\u0131z RabbitMQ yaz\u0131 dizisi<\/a>ni okuyabilirsiniz. Lakin bizler bu i\u00e7eri\u011fimizde RabbitMQ’yu Docker<\/a> ile kurup o \u015fekilde kullanmay\u0131 tercih edece\u011fiz. Bunun i\u00e7in Docker\u2019da RabbitMQ Aya\u011fa Kald\u0131rma<\/a> ba\u015fl\u0131kl\u0131 makalemi incelemenizi tavsiye ederim.<\/p>\n
CAP Nedir? Nas\u0131l Kullan\u0131l\u0131r?<\/h3>\n
$\"Event$ <\/a>
CAP k\u00fct\u00fcphanesinin mimarisi…<\/p><\/div>CAP, distributed sistemlerdeki producer-consumer yap\u0131s\u0131n\u0131n g\u00fcvenilirli\u011fi tam olarak garanti etmemesi durumuna istinaden, y\u00f6netilebilirlik a\u00e7\u0131s\u0131ndan kolayl\u0131k sa\u011flayan ve Event Bus i\u015flevine sahip olan, hafif, kolay ve verimli bir .NET tabanl\u0131 a\u00e7\u0131k kaynak(open source) k\u00fct\u00fcphanedir.<\/p>\n
Microservice yakla\u015f\u0131m\u0131n\u0131 benimseyen sistemlerde yukar\u0131da da bahsedildi\u011fi \u00fczere mesaj kuyruk sisteminin basit\u00e7e kullan\u0131lmas\u0131 g\u00fcvenilirli\u011fi garanti etmeyecektir. \u0130\u015fte bu olas\u0131 duruma istinaden da\u011f\u0131t\u0131lm\u0131\u015f sistemlerin birbirini \u00e7a\u011f\u0131rmas\u0131 s\u00fcrecinde olu\u015fabilecek istisnalar\u0131 \u00e7\u00f6z\u00fcmlemek i\u00e7in CAP’\u0131 kullanmay\u0131 tercih edece\u011fiz.<\/p>\n
CAP, microservice mimarisinde servislerin birbirleriyle ileti\u015fime ge\u00e7mesinde olu\u015facak istisnalar\u0131 \u00e7\u00f6z\u00fcmleyebilmek i\u00e7in mevcut veritaban\u0131 ile entegre \u00e7al\u0131\u015fan Local Message Table<\/em> yakla\u015f\u0131m\u0131n\u0131 benimsemi\u015f bir k\u00fct\u00fcphanedir.<\/strong><\/p><\/blockquote>\n
Nas\u0131l kullanaca\u011f\u0131z?<\/em> sorusuna gelirsek e\u011fer zaten bu i\u00e7eri\u011fimizde komple ilgili k\u00fct\u00fcphane \u00fczerine kurulu bir anlat\u0131m sergileyece\u011fiz \ud83d\ude42<\/p>\n
\u00d6rnek Senaryo<\/h3>\nServislerin Olu\u015fturulmas\u0131 ve CAP Entegrasyonu<\/h4>\n
\u0130lk olarak aralar\u0131nda ileti\u015fim kuracak olan ‘ProducerAPI’ ve ‘ConsumerAPI’ isminde iki adet servis olu\u015ftural\u0131m.
\n`dotnet new webapi --name producerAPI<\/code> \ndotnet new webapi --name consumerAPI<\/code> \nArd\u0131ndan her iki projeyede`DotNetCore.CAP<\/a> k\u00fct\u00fcphanesini \ndotnet add package DotNetCore.CAP<\/code> \nkomutuyla, kullanaca\u011f\u0131m\u0131z RabbitMQ mesaj kuyruk sistemi i\u00e7inse DotNetCore.CAP.RabbitMQ<\/a> k\u00fct\u00fcphanesini \ndotnet add package DotNetCore.CAP.RabbitMQ<\/code> \nkomutuyla ve son olarak servisler aras\u0131nda ileti\u015fim i\u00e7in yarat\u0131lan olaylar\u0131 loglayabilmek i\u00e7in DotNetCore.CAP.SqlServer<\/a> k\u00fct\u00fcphanesini \ndotnet add package DotNetCore.CAP.SqlServer<\/code> \nkomutu arac\u0131l\u0131\u011f\u0131yla y\u00fckleyiniz.<\/p>\n
`\u0130lgili k\u00fct\u00fcphaneleri y\u00fckledikten sonra her iki projeninde ‘Startup.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki konfig\u00fcrasyonlar\u0131n yap\u0131lmas\u0131 gerekmektedir;<\/p>\n`
\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n services.AddDbContext<ExampleContext>(options => options.UseSqlServer("Server=.;Database=MicroserviceExampleDB;Trusted_Connection=True;"));\r\n services.AddCap(options =>\r\n {\r\n options.UseEntityFramework<ExampleContext>();\r\n options.UseSqlServer("Server=.;Database=MicroserviceExampleDB;Trusted_Connection=True;");\r\n\r\n options.UseRabbitMQ(options =>\r\n {\r\n options.ConnectionFactoryOptions = options =>\r\n {\r\n options.Ssl.Enabled = false;\r\n options.HostName = "localhost";\r\n options.UserName = "guest";\r\n options.Password = "guest";\r\n options.Port = 5672;\r\n };\r\n });\r\n });\r\n services.AddControllers();\r\n }\r\n<\/pre>\nPort Ayarlamas\u0131<\/h4>\n\u00d6rneklendirmemizi localde ger\u00e7ekle\u015ftirece\u011fimizden dolay\u0131 her iki uygulaman\u0131nda farkl\u0131 portlarda aya\u011fa kald\u0131r\u0131lmas\u0131 gerekmektedir. Bunun i\u00e7in her iki projenin ‘launchSettings.json’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi port ayarlamas\u0131nda bulunulmas\u0131 gerekmektedir;<\/p>\n ProducerAPI;<\/p>\n\r\n "producerAPI": {\r\n "commandName": "Project",\r\n "launchBrowser": false,\r\n "applicationUrl": "https:\/\/localhost:5001;http:\/\/localhost:5000",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n<\/pre>\nConsumerAPI;<\/p>\n\r\n "consumerAPI": {\r\n "commandName": "Project",\r\n "launchBrowser": false,\r\n "applicationUrl": "https:\/\/localhost:5003;http:\/\/localhost:5002",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n<\/pre>\nMesaj Yay\u0131nlama<\/h4>\n\u015eimdi ProducerAPI servisi \u00fczerinden bir i\u015flem ger\u00e7ekle\u015ftirelim ve neticede ConsumerAPI servisini uyaral\u0131m. Bunun i\u00e7in ProducerAPI uygulamas\u0131nda a\u015fa\u011f\u0131daki gibi bir controller geli\u015ftirelim;<\/p>\n\r\n [ApiController]\r\n [Route("api\/[controller]")]\r\n public class ProducerController : ControllerBase\r\n {\r\n private readonly ICapPublisher _capPublisher;\r\n public ProducerController(ICapPublisher capPublisher)\r\n {\r\n _capPublisher = capPublisher;\r\n }\r\n public async Task<IActionResult> ProducerTransaction()\r\n {\r\n using ExampleContext context = new ExampleContext();\r\n using var transaction = context.Database.BeginTransaction(_capPublisher, autoCommit: true);\r\n var date = DateTime.Now;\r\n await _capPublisher.PublishAsync<DateTime>("producer.transaction", date);\r\n return Ok(date);\r\n }\r\n }\r\n<\/pre>\nDikkat ederseniz burada ‘ICapPublisher’ interface’i ile CAP k\u00fct\u00fcphanesi inject edilmekte ve context nesnesi \u00fczerinden ba\u015flat\u0131lan transactionda kullan\u0131lmaktad\u0131r. Ayr\u0131ca ilgili aray\u00fcz arac\u0131l\u0131\u011f\u0131yla ‘producer.transaction’ de\u011feri alt\u0131nda veri olarak o an\u0131n tarih bilgisini yay\u0131nlamaktad\u0131r.<\/p>\nMesaj Yakalama<\/h4>\nProducerAPI taraf\u0131ndan yay\u0131nlanan mesaj\u0131 ConsumerAPI’da elde edebilmek i\u00e7in ilgili projede a\u015fa\u011f\u0131daki gibi bir controller geli\u015ftirilmelidir;<\/p>\n\r\n [ApiController]\r\n [Route("[controller]")]\r\n public class ConsumerController : ControllerBase\r\n {\r\n [CapSubscribe("producer.transaction")]\r\n public void Consumer(DateTime date)\r\n {\r\n Console.WriteLine(date);\r\n }\r\n }\r\n<\/pre>\nYukar\u0131daki kod blo\u011funu incelerseniz e\u011fer consumer’\u0131n dinleyici fonksiyonunu ‘CapSubscribe’ attribute’u ile i\u015faretleyerek producer’de ki publish de\u011feri olan ‘producer.transaction’ ile ili\u015fkilendiriyor ve ilgili yay\u0131na abone yap\u0131yoruz. B\u00f6ylece producer bir mesaj yay\u0131nlad\u0131\u011f\u0131 an direkt olarak consumer haberdar ediliyor. \n<\/a><\/p>\n Business Logic Service’lerde Mesaja Yakalama<\/h4>\nE\u011fer ki yay\u0131nlanan mesaj\u0131 controllerda de\u011fil business logic’de yakalamak istiyorsan\u0131z ilgili s\u0131n\u0131f\u0131n a\u015fa\u011f\u0131daki gibi geli\u015ftirilmesi gerekmektedir.<\/p>\n\r\n public class ConsumerService : ICapSubscribe\r\n {\r\n [CapSubscribe("producer.transaction")]\r\n public void Consumer(DateTime date)\r\n {\r\n Console.WriteLine("Servis : " + date);\r\n }\r\n }\r\n<\/pre>\nBurada s\u0131n\u0131f\u0131 incelerseniz e\u011fer ‘ICapSubscribe’ interface’inden t\u00fcremesi gerekmekte ve ‘CapSubscribe’ attribute’u ile tekrardan ilgili producer de\u011ferini ta\u015f\u0131yacak \u015fekilde i\u015faretlenmesi gerekmektedir. Bu i\u015flemin ard\u0131ndan in\u015fa edilen ilgili s\u0131n\u0131f\u0131n uygulamaya a\u015fa\u011f\u0131daki gibi servis olarak eklenmesi gerekmektedir.<\/p>\n\r\n\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n .\r\n .\r\n .\r\n services.AddTransient<ConsumerService>();\r\n services.AddCap(options =>\r\n {\r\n .\r\n .\r\n .\r\n });\r\n .\r\n .\r\n .\r\n }\r\n<\/pre>\n<\/a><\/p>\n Abone Gruplar\u0131 Olu\u015fturma<\/h4>\nCAP, gelen bir mesaj\u0131 birden fazla gruba da\u011f\u0131tarak daha fazla servis yahut controller taraf\u0131ndan dinlenilmesini sa\u011flayabilmektedir. \u015e\u00f6yle ki; \nService;<\/p>\n\r\n [CapSubscribe("producer.transaction", Group = "group2")]\r\n public void Consumer(DateTime date)\r\n {\r\n Console.WriteLine("Servis : " + date);\r\n }\r\n<\/pre>\nController;<\/p>\n\r\n [ApiController]\r\n [Route("[controller]")]\r\n public class ConsumerController : ControllerBase\r\n {\r\n [CapSubscribe("producer.transaction", Group = "group1")]\r\n public void Consumer(DateTime date)\r\n {\r\n Console.WriteLine(date);\r\n }\r\n }\r\n<\/pre>\nAyn\u0131 gruba abone olan yap\u0131lardan sadece bir tanesi tetiklenmekte, bilakis farkl\u0131 gruplarda ise her biri ayr\u0131 ayr\u0131 tetiklenmektedir. \n<\/a><\/p>\n G\u00f6sterge Paneli Olu\u015fturma(Dashboard)<\/h4>\nCAP, g\u00f6nderilen ve al\u0131nan mesajlar\u0131 kolayca ger\u00e7ek zamanl\u0131 g\u00f6rebilmemiz i\u00e7in Dashboard \u00f6zelli\u011fi ta\u015f\u0131maktad\u0131r. Dashboard entegrasyonu i\u00e7in uygulamaya DotNetCore.CAP.Dashboard<\/a> k\u00fct\u00fcphanesini a\u015fa\u011f\u0131daki komutla y\u00fckleyiniz. \ndotnet add package DotNetCore.CAP.Dashboard<\/code> \nArd\u0131ndan ‘Startup.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki konfig\u00fcrasyonu ger\u00e7ekle\u015ftiriniz.<\/p>\n \r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n .\r\n .\r\n .\r\n services.AddCap(options =>\r\n {\r\n .\r\n .\r\n .\r\n options.UseDashboard(o => o.PathMatch = "\/cap-dashboard");\r\n .\r\n .\r\n .\r\n });\r\n .\r\n .\r\n .\r\n }\r\n<\/pre>\nYukar\u0131daki kod blo\u011funu incelerseniz e\u011fer ‘AddCap’ servisi alt\u0131nda ‘UseDashboard’ servisini uygulamaya dahil etmekte ve ‘\/cap-dashboard’ adresi alt\u0131nda eri\u015fim sa\u011flanabilece\u011fi bildirilmektedir. \n<\/a><\/p>\n CAP Faydas\u0131n\u0131 G\u00f6relim<\/h4>\nHer event veritaban\u0131 seviyesinde tutularak olas\u0131 hata yahut kesinti durumlar\u0131nda veri kayb\u0131n\u0131 \u00f6nlemekte ve ileti\u015fimin tekrar sa\u011fland\u0131\u011f\u0131 durumlarda mesaj kuyruk sistemine g\u00f6nderilmemi\u015f ve expire s\u00fcresi dolmayan mesajlar\u0131 tekrardan g\u00f6ndermekte ve b\u00f6ylece kullan\u0131lan mesaj kuyruk sistemi ve hatta hatalar yahut kesintilerden izole bir \u015fekilde geli\u015ftirme yap\u0131lmas\u0131na olanak sa\u011flamaktad\u0131r.<\/p>\n\u00d6rnek veritaban\u0131 g\u00f6r\u00fcnt\u00fcs\u00fc i\u00e7in a\u015fa\u011f\u0131daki ekran al\u0131nt\u0131s\u0131n\u0131 inceleyiniz; \n<\/a><\/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 indirmek i\u00e7in buraya<\/a> t\u0131klay\u0131n\u0131z.<\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Bu i\u00e7eri\u011fimizde Microservice mimarilerde servislerin kendi aralar\u0131nda haberle\u015febilmesi i\u00e7in Event Driven y\u00f6nteminin nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve kullan\u0131ld\u0131\u011f\u0131n\u0131 ele alaca\u011f\u0131z. Microservice’lerde Event Driven Nedir? Her bir servisin i\u015flevsel a\u00e7\u0131dan yapaca\u011f\u0131 operasyon neticesinde bir event’i fire...<\/p>\n","protected":false},"author":1,"featured_media":16524,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3573],"tags":[3592,3593,3594,2433,3591,3590,3589],"class_list":["post-16322","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microservices","tag-dotnetcore-cap","tag-dotnetcore-cap-rabbitmq","tag-dotnetcore-cap-sqlserver","tag-event-driven","tag-event-driven-cap","tag-event-driven-haberlesme","tag-microservice-event-driven"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16322","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=16322"}],"version-history":[{"count":85,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16322\/revisions"}],"predecessor-version":[{"id":16616,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/16322\/revisions\/16616"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/16524"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=16322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=16322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=16322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}