Bu makale kapsam\u0131ndaki konu ba\u015fl\u0131klar\u0131m\u0131z ise s\u0131ras\u0131yla a\u015fa\u011f\u0131daki gibi olacakt\u0131r.<\/p>\n
- \n
- Messaging Architecture<\/li>\n
- \u00d6rnek Senaryo<\/li>\n
- ESB Nedir ve MassTransit’e Giri\u015f<\/li>\n
- RabbitMQ ile MassTransit Implementasyonu<\/li>\n<\/ol>\n
Messaging concept’leri hakk\u0131nda di\u011fer makalelerimde de sizlere olabildi\u011fince bahsetmeye \u00e7al\u0131\u015ft\u0131\u011f\u0131m i\u00e7in dilerseniz bu bilgileri hat\u0131rlamak ad\u0131na, Messaging Architecture’a genel bir bak\u0131\u015f atal\u0131m.<\/p>\n
1) Messaging Architecture<\/h4>\n
![\"message-queue\"](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
<\/a><\/p>\nMessaging yap\u0131lar\u0131 ile uygulamalar\u0131 loosely coupled<\/strong> olarak, asenkron<\/strong> bir \u015fekilde birbirleri ile ileti\u015fime ge\u00e7irebildi\u011fimizden daha \u00f6nceki konularda bahsetmi\u015ftim. Daha \u00e7ok\u00a0enterprise\u00a0d\u00fczeyde geli\u015ftirilen ve ihtiya\u00e7lar do\u011frultusunda birbirlerinden ba\u011f\u0131ms\u0131z platformlarda yer alan\u00a0uygulamalar, distributed<\/strong> bir \u015fekilde g\u00fcn\u00fcm\u00fczde \u00e7al\u0131\u015ft\u0131r\u0131lmaktad\u0131r. Messaging yap\u0131lar\u0131n\u0131n\u00a0tercih edilmesinin key point’i olarak,\u00a0scalability<\/strong>\u00a0ve flexibility<\/strong> diyebilirim en az\u0131ndan kendi ad\u0131ma.<\/p>\n
Scalability taraf\u0131ndan bakt\u0131\u011f\u0131m\u0131zda olaya b\u00fcy\u00fck verilerle \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z ortamlarda, bu verileri process eden uygulamay\u0131 single instance<\/strong> ve ayn\u0131 ortamda\u00a0<\/strong>host etmek yerine farkl\u0131 ortamdaki service’lere da\u011f\u0131tarak, distributed bir \u015fekilde i\u015flemleri hem daha h\u0131zl\u0131 hem de\u00a0daha az y\u00fckle\u00a0scale edebilmek\u00a0m\u00fcmk\u00fcn oluyor. Monolith\u00a0architecture’lar gibi her \u015feyi tek bir instance’a y\u00fckleyerek yapmak, b\u00fcy\u00fck \u00f6l\u00e7ekli enterprise uygulamalar i\u00e7in \u00e7ok efektif olmayacakt\u0131r.<\/p>\n
Messaging architecture basic concept olarak gayet basittir.\u00a0Message’lar\u0131 queue ya g\u00f6nderen bir adet client vard\u0131r ve Producer<\/strong> olarak adland\u0131r\u0131l\u0131r. Birde queue’daki message’lar\u0131 dinleyip, process eden bir uygulama vard\u0131r, buda Consumer<\/strong> olarak adland\u0131r\u0131l\u0131r. Messaging architecture implementasyon k\u0131s\u0131mlar\u0131nda ise referans olarak al\u0131nabilecek\u00a0Enterprise\u00a0Integration Patterns<\/a><\/strong><\/em> olarak adland\u0131r\u0131lan, \u00e7e\u015fitli pattern ve messaging channel’lar mevcuttur.\u00a0Biz ise ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rne\u011fimizdeki ihtiya\u00e7dan dolay\u0131, messaging channel olarak Publish-Subscribe<\/strong> pattern’\u0131n\u0131 implemente edece\u011fiz.<\/p>\n
2)\u00a0\u00d6rnek Senaryo<\/h4>\n
Messaging architecture ile ilgili concept’i genel olarak tazelememizin ard\u0131ndan, makale konusunda ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rnek senaryomuza bir bakal\u0131m.<\/p>\n
<\/a><\/p>\nKonunun daha iyi anla\u015f\u0131labilmesi i\u00e7in en \u00e7ok transactional i\u015flemlerin ger\u00e7ekle\u015fti\u011fi, e-commerce sistemlerindeki sipari\u015f olu\u015fturma\u00a0\u00f6rne\u011fini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n
Bu tarz i\u015flemlerde genelde bir sipari\u015f olu\u015fur, kullan\u0131c\u0131ya bir e-mail g\u00f6nderilir ve faturaland\u0131rma gibi vb. servisler \u00e7al\u0131\u015f\u0131r. Biz ise ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rnekte\u00a0yukar\u0131daki flowchart’a bakt\u0131\u011f\u0131m\u0131zda, producer g\u00f6revini \u00fcstlenecek olan bir Order UI olacak. Bu ekrandan d\u00fc\u015fen sipari\u015fler bir queue’ya aktar\u0131lacak. Bu queue’yu ise consume edecek olan bir OrderService olacak. OrderService ise gerekli order i\u015flemlerini ger\u00e7ekle\u015ftirecek. Bu aradaki iki uygulama, tamamen birbirlerinden ba\u011f\u0131ms\u0131z bir \u015fekilde haberle\u015feceklerdir.<\/p>\n
Makalenin 2. serisinde\u00a0yer vermeyi d\u00fc\u015f\u00fcnd\u00fc\u011f\u00fcm bir di\u011fer senaryoya de\u011finmek gerekirse, OrderService ilgili order i\u015flemini ger\u00e7ekle\u015ftirir ve sonra bir event f\u0131rlat\u0131r. Bu event ile ilgilenen herhangi bir XService, bu event’\u0131 yakalar ve ilgili i\u015flemlerini tamamlar. \u00d6rne\u011fin order i\u015flemi OrderService taraf\u0131ndan ger\u00e7ekle\u015ftirildikten sonra, ilgili kullan\u0131c\u0131ya bir bilgilendirme e-mail’\u0131 g\u00f6nderilebilmesi i\u00e7in, NotificationService’e bir event f\u0131rlat\u0131l\u0131r. NotificationService bu event’\u0131 yakalar ve ilgili e-mail g\u00f6nderim i\u015flemini ger\u00e7ekle\u015ftirir.<\/p>\n
Bu tarz n say\u0131da farkl\u0131 servis, birbirleri ile loosely coupled bir \u015fekilde haberle\u015febilmektedirler.<\/p>\n
3)\u00a0ESB Nedir ve MassTransit’e Giri\u015f<\/h4>\n
<\/a><\/p>\nEnterprise Service Bus (ESB) i\u00e7in genel olarak transport i\u015flemleri i\u00e7in bir gateway’dir diyebiliriz. ESB’nin g\u00f6revi asl\u0131nda high level olarak \u00f6z\u00fcnde, transport i\u015flemlerini\u00a0higher abstraction seviyesinde client api i\u00e7in halletmektedir.<\/p>\n
Olaya biraz daha anla\u015f\u0131l\u0131r bir bak\u0131\u015f a\u00e7\u0131s\u0131ndan da bakmak gerekirse, SOA mimarilerinin kolay ve reliable bir \u015fekilde uygulanabilmesi i\u00e7in i\u00e7erisinde bir \u00e7ok altyap\u0131sal fonksiyonlar\u0131 bar\u0131nd\u0131ran bir altyap\u0131 mimarisidir diyebiliriz. Bunlara ek olarak\u00a0distributed olan\u00a0uygulamalar\u0131 \u00e7al\u0131\u015ft\u0131rmay\u0131 ve\u00a0y\u00f6netebilmeyi de kolayla\u015ft\u0131rmaktad\u0131r.<\/p>\n
\u015euanda .Net stack’i alt\u0131nda pop\u00fcler olan NServiceBus ve MassTransit gibi ESB’ler mevcuttur. MassTransit open-source bir projedir ve bir \u00e7ok MQ sistemine deste\u011fi de bulunmaktad\u0131r. Makale i\u00e7eri\u011finde ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rnekte MassTransit ile ilerleyece\u011fimiz i\u00e7in, dilerseniz sa\u011fl\u0131yor oldu\u011fu baz\u0131 benefit’lere bir bakal\u0131m.<\/p>\n
MassTransit Benetifs:<\/strong><\/p>\n
- \n
- Transport i\u015flemlerinin\u00a0complexity’sini gizler<\/li>\n
- Multiple transport deste\u011fi sunar<\/li>\n
- Build-in olarak i\u00e7erisinde retries policy’leri mevcuttur (ki MQ yap\u0131lar\u0131nda olmazsa olmaz bir yap\u0131d\u0131r)<\/li>\n
- Failure management sa\u011flar<\/li>\n
- MassTransit Test Framework paketi ile kolay unit testing sa\u011flar<\/li>\n
- Message\u00a0\u00a0scheduling mevcuttur. (periodic ve publishing yap\u0131labilmektedir)<\/li>\n
- Request\/Response pattern’lar\u0131n\u0131 destekler<\/li>\n
- Verimlilik i\u00e7in kendisi exchange’leri y\u00f6netir<\/li>\n<\/ul>\n
gibi faydalar\u0131 bulunmaktad\u0131r. Bunlara ek olarak da message’lar\u0131 intercept edebilmeye de olanak sa\u011flamaktad\u0131r.<\/p>\n
3)\u00a0RabbitMQ ile MassTransit Implementasyonu<\/h4>\n
Gerekli concept’lere g\u00f6z att\u0131ktan sonra, art\u0131k yava\u015f yava\u015f implementasyon i\u015flemlerine ge\u00e7ebiliriz. “LightMessagingCore.Boilerplate” isminde bo\u015f bir solution olu\u015fturarak, ilk ad\u0131m\u0131m\u0131z\u0131 atal\u0131m. Solution i\u00e7erisine “LightMessagingCore.Boilerplate.Common” isminde bir class library ekleyelim ve burada bus i\u00e7in configuration i\u015flemlerimizi ger\u00e7ekle\u015ftirmeye ba\u015flayal\u0131m.<\/p>\n
“MqConstants” isminde bir class ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n
using System.Configuration;\r\n\r\nnamespace LightMessagingCore.Boilerplate.Common\r\n{\r\n public class MqConstants\r\n {\r\n public static string RabbitMQUri => ConfigurationManager.AppSettings[\"RabbitMQUri\"];\r\n public static string RabbitMQUserName => ConfigurationManager.AppSettings[\"RabbitMQUserName\"];\r\n public static string RabbitMQPassword => ConfigurationManager.AppSettings[\"RabbitMQPassword\"];\r\n }\r\n}<\/pre>\nTan\u0131mlam\u0131\u015f oldu\u011fumuz bu class’da, daha sonra ihtiya\u00e7 duyaca\u011f\u0131m\u0131z baz\u0131 property’leri ekledik. Burada kullanacak oldu\u011fumuz RabbitMQ broker’\u0131\u00a0i\u00e7in URI adresi, varsa credential bilgileri ve bir queue ismi yer almaktad\u0131r.<\/p>\n
MassTransit implementasyonuna ba\u015flamadan \u00f6nce hemen Nuget Package Manager \u00fczerinden a\u015fa\u011f\u0131daki gibi “MassTransit.RabbitMQ” paketini kural\u0131m.<\/p>\n
<\/a><\/p>\nPaket kurulumunu tamamlad\u0131ktan sonra art\u0131k ESB configuration’lar\u0131n\u0131 ger\u00e7ekle\u015ftirecek oldu\u011fumuz “BusConfigurator” class’\u0131n\u0131 a\u015fa\u011f\u0131daki gibi\u00a0kodlamaya ba\u015flayal\u0131m.<\/p>\n
using System;\r\nusing MassTransit;\r\nusing MassTransit.RabbitMqTransport;\r\n\r\nnamespace LightMessagingCore.Boilerplate.Common\r\n{\r\n public class BusConfigurator\r\n {\r\n private static readonly Lazy<BusConfigurator> _Instance = new Lazy<BusConfigurator>(() => new BusConfigurator());\r\n\r\n private BusConfigurator()\r\n {\r\n\r\n }\r\n\r\n public static BusConfigurator Instance => _Instance.Value;\r\n\r\n public IBusControl ConfigureBus(\r\n Action<IRabbitMqBusFactoryConfigurator, IRabbitMqHost> registrationAction = null)\r\n {\r\n return Bus.Factory.CreateUsingRabbitMq(cfg =>\r\n {\r\n var host = cfg.Host(new Uri(MqConstants.RabbitMQUri), hst =>\r\n {\r\n hst.Username(MqConstants.RabbitMQUserName);\r\n hst.Password(MqConstants.RabbitMQPassword);\r\n });\r\n\r\n registrationAction?.Invoke(cfg, host);\r\n });\r\n }\r\n }\r\n}<\/pre>\nSingleton olarak tasarlad\u0131\u011f\u0131m\u0131z “BusConfigurator” class’\u0131 i\u00e7erisinde, “ConfigureBus” method’u ile MassTransit’in “IBusControl” interface’ini implemente eden bir RabbitMQ BusControl instance’\u0131 olu\u015fturuyoruz. Bu i\u015flem i\u00e7in ise “Bus.Factory.CreateUsingRabbitMq” method’unu call ederek, “IRabbitMqBusFactoryConfigurator” tipinde bir action olu\u015fturuyoruz ve i\u00e7erisinde RabbitMQ’ya connect olabilmek i\u00e7in gerekli olan host credential bilgilerini tan\u0131ml\u0131yoruz.<\/p>\n
Bir di\u011fer yandan\u00a0“registrationAction” parametresi ile ise “ConfigureBus” method’unu \u00e7a\u011f\u0131r\u0131rken ihtiya\u00e7 duyuldu\u011fu noktalarda, RabbitMQ bus’\u0131 i\u00e7in gerekli olan “queue name”, “endpoint” ve “consumer” gibi bilgileri veriyor olaca\u011f\u0131z.<\/p>\n
En basit haliyle “BusConfigurator” class’\u0131 \u015fimdilik bu kadar.<\/p>\n
Not<\/strong>: Makale i\u00e7erisinde ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rne\u011fi, sonras\u0131nda lightweight bir messaging core boilerplate’i olarak github \u00fczerinden ilerletmeyi d\u00fc\u015f\u00fcn\u00fcyorum. En k\u0131sa zamanda bus configurator i\u00e7in retries policy’leri<\/em>, circuit breaker<\/em>, rate limiter<\/em> vb. gibi \u00f6zellikleri de fluent bir \u015fekilde implemente etmeyi d\u00fc\u015f\u00fcn\u00fcyorum.<\/p><\/blockquote>\n
\u015eimdi producer ve consumer’\u0131n exchange i\u015flemi s\u0131ras\u0131nda kullanacak oldu\u011fu, messaging interface’lerini tan\u0131mlamaya ba\u015flayabiliriz. Bunun i\u00e7in \u00f6ncelikle solution \u00fczerine “LightMessagingCore.Boilerplate.Messaging” isminde bir class library daha ekleyelim.<\/p>\n
Library eklemeyi tamamlad\u0131ktan sonra i\u00e7erisine a\u015fa\u011f\u0131daki gibi “IOrderCommand” isminde bir interface tan\u0131mlayal\u0131m.<\/p>\n
namespace LightMessagingCore.Boilerplate.Messaging\r\n{\r\n public interface IOrderCommand\r\n {\r\n int OrderId { get; set; }\r\n string OrderCode { get; set; }\r\n }\r\n}<\/pre>\nOlu\u015fturmu\u015f oldu\u011fumuz bu interface sadece “OrderId” ve “OrderCode” bilgilerini tutmaktad\u0131r.<\/p>\n
Not<\/strong>: Bu k\u0131s\u0131mda \u00f6nemli bir nokta bulunmaktad\u0131r. ESB<\/strong> olarak MassTransit kulland\u0131\u011f\u0131m\u0131z i\u00e7in, producer ve consumer’\u0131n ayn\u0131 messaging interface<\/strong>‘ini\u00a0exchange ediyor olmalar\u0131 \u00f6nemlidir. Aksi takdirde producer’\u0131n queue’ya g\u00f6nderdi\u011fi message’lar\u0131, consumer consume edemeyecektir. Bunun sebebi ise MassTransit’in verimlili\u011fi artt\u0131rabilmek i\u00e7in exchange’leri kendisinin y\u00f6netmesidir.\u00a0Y\u00f6netim i\u015flemini ise MassTransit, interface’lere g\u00f6re ger\u00e7ekle\u015ftirmektedir. Bu konuya makalenin ilerleyen b\u00f6l\u00fcmlerinde g\u00f6rsel olarak de\u011finece\u011fim.<\/p><\/blockquote>\n
3.1)\u00a0Producer’\u0131n Haz\u0131rlanmas\u0131<\/h4>\n
Producer k\u0131sm\u0131n\u0131 yani Order UI’\u0131 olu\u015fturabilmek i\u00e7in gerekli altyap\u0131m\u0131z haz\u0131r durumda. Solution \u00fczerine “LightMessagingCore.Boilerplate.OrderUI” isminde, template olarak ise empty se\u00e7ili bir \u00a0Asp.Net MVC projesi ekleyelim. Projenin ekleme i\u015fleminden sonra ise solution structure’\u0131n son hali a\u015fa\u011f\u0131daki gibi olacakt\u0131r.<\/p>\n
<\/a><\/p>\nProjeyi ekledikten sonra ise “Controllers” k\u0131sm\u0131na “OrderController” isminde, empty bir MVC controller’\u0131 ekleyelim.<\/p>\n
Not<\/strong>: “LightMessagingCore.Boilerplate” solution’\u0131 alt\u0131nda, sanki monolith architecture’a do\u011fru gidiyor gibi olabiliriz. Fakat ger\u00e7ek bir ortamda olu\u015fturmu\u015f oldu\u011fumuz “LightMessagingCore.Boilerplate.Common” ve ortak payla\u015fmam\u0131z gereken contract’\u0131n da oldu\u011fu “LightMessagingCore.Boilerplate.Messaging” library’lerini, nuget server’lar \u00fczerinden birer package olarak y\u00f6netebilmek m\u00fcmk\u00fcnd\u00fcr. Sonras\u0131nda ise producer ve consumer’lar monolithlikten \u00e7\u0131karak, birer microservice olarak geli\u015ftirilebilir.\u00a0Ben \u00f6rnek gere\u011fi tek bir solution \u00fczerinden ilerleyece\u011fim.<\/p><\/blockquote>\n
Art\u0131k projeye ilgili referanslar\u0131 eklemeye ba\u015flayabiliriz. “LightMessagingCore.Boilerplate.OrderUI” projesinin referans k\u0131sm\u0131na gelerek “LightMessagingCore.Boilerplate.Common”, “LightMessagingCore.Boilerplate.Messaging” library’lerini referans olarak ekleyelim\u00a0ve Nuget Package Manager \u00fczerinden de “MassTransit.RabbitMQ” paketini kural\u0131m.<\/p>\n
Referans ekleme i\u015flemlerinin ard\u0131ndan order model’ini olu\u015fturabiliriz. Order model’ine “LightMessagingCore.Boilerplate.Messaging” library’sinde olu\u015fturmu\u015f oldu\u011fumuz “IOrderCommand” interface’ini implemente edece\u011fiz. “Models” klas\u00f6r\u00fcne “OrderModel” isminde yeni bir class tan\u0131mlayal\u0131m ve “IOrderCommand” interface’ini a\u015fa\u011f\u0131daki gibi implemente edelim.<\/p>\n
using LightMessagingCore.Boilerplate.Messaging;\r\n\r\nnamespace LightMessagingCore.Boilerplate.OrderUI.Models\r\n{\r\n public class OrderModel : IOrderCommand\r\n {\r\n public string OrderCode { get; set; }\r\n\r\n public int OrderId { get; set; }\r\n }\r\n}<\/pre>\nImplementasyon i\u015fleminden sonra ise “OrderController” a gelerek, “Index” action’\u0131 \u00fczerine sa\u011f t\u0131klay\u0131p yeni bir view ekleyelim. View ekleme i\u015flemi s\u0131ras\u0131nda bize kolayl\u0131k sa\u011flayabilmesi ad\u0131na template<\/strong> olarak “Create” ve model class<\/strong> olarak ise olu\u015fturmu\u015f oldu\u011fumuz “OrderModel” class’\u0131n\u0131 se\u00e7elim.<\/p>\n
View’\u0131n eklenmesinin ard\u0131ndan “Views>Order>Index.cshtml” path’ini takip edelim ve a\u015fa\u011f\u0131daki gibi g\u00fcncelleyelim.<\/p>\n
@model LightMessagingCore.Boilerplate.OrderUI.Models.OrderModel\r\n\r\n@{\r\n ViewBag.Title = \"Order Create\";\r\n}\r\n\r\n<h2>Order Create<\/h2>\r\n\r\n\r\n@using (Html.BeginForm())\r\n{\r\n @Html.AntiForgeryToken()\r\n\r\n <div class=\"form-horizontal\">\r\n <h4>Order<\/h4>\r\n <hr \/>\r\n @Html.ValidationSummary(true, \"\", new { @class = \"text-danger\" })\r\n <div class=\"form-group\">\r\n @Html.LabelFor(model => model.OrderCode, htmlAttributes: new { @class = \"control-label col-md-2\" })\r\n <div class=\"col-md-10\">\r\n @Html.EditorFor(model => model.OrderCode, new { htmlAttributes = new { @class = \"form-control\" } })\r\n @Html.ValidationMessageFor(model => model.OrderCode, \"\", new { @class = \"text-danger\" })\r\n <\/div>\r\n <\/div>\r\n <div class=\"form-group\">\r\n @Html.LabelFor(model => model.OrderId, htmlAttributes: new { @class = \"control-label col-md-2\" })\r\n <div class=\"col-md-10\">\r\n @Html.EditorFor(model => model.OrderId, new { htmlAttributes = new { @class = \"form-control\" } })\r\n @Html.ValidationMessageFor(model => model.OrderId, \"\", new { @class = \"text-danger\" })\r\n <\/div>\r\n <\/div>\r\n\r\n <div class=\"form-group\">\r\n <div class=\"col-md-offset-2 col-md-10\">\r\n <input type=\"submit\" value=\"Create\" class=\"btn btn-default\" \/>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n}\r\n\r\n<div>\r\n @Html.ActionLink(\"Back to List\", \"Index\")\r\n<\/div>\r\n\r\n<script src=\"~\/Scripts\/jquery-1.10.2.min.js\"><\/script>\r\n<script src=\"~\/Scripts\/jquery.validate.min.js\"><\/script>\r\n<script src=\"~\/Scripts\/jquery.validate.unobtrusive.min.js\"><\/script><\/pre>\n\u0130lgili paketlerin ve view’\u0131n tamamlanmas\u0131n\u0131n ard\u0131ndan art\u0131k “OrderController” \u0131 kodlamaya devam edebiliriz. \u00a0“OrderController” \u0131 a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n
using System;\r\nusing System.Configuration;\r\nusing System.Web.Mvc;\r\nusing LightMessagingCore.Boilerplate.Common;\r\nusing LightMessagingCore.Boilerplate.OrderUI.Models;\r\nusing MassTransit;\r\n\r\nnamespace LightMessagingCore.Boilerplate.OrderUI.Controllers\r\n{\r\n public class OrderController : Controller\r\n {\r\n private readonly ISendEndpoint _bus;\r\n\r\n public OrderController()\r\n {\r\n var busControl = BusConfigurator.Instance.ConfigureBus();\r\n var sendToUri = new Uri($\"{MqConstants.RabbitMQUri}{ConfigurationManager.AppSettings[\"OrderQueueName\"]}\");\r\n\r\n _bus = busControl.GetSendEndpoint(sendToUri).Result;\r\n }\r\n\r\n \/\/ GET: Order\r\n public ActionResult Index(OrderModel orderModel)\r\n {\r\n if (orderModel.OrderId > 0)\r\n CreateOrder(orderModel);\r\n\r\n return View();\r\n }\r\n\r\n private void CreateOrder(OrderModel orderModel)\r\n {\r\n _bus.Send(orderModel).Wait();\r\n }\r\n }\r\n}<\/pre>\nBurada \u00f6ncelikle constructor \u00fczerinden “busControl” \u00fc initialize ediyoruz. Bu i\u015flem i\u00e7in common library’si \u00fczerinde olu\u015fturmu\u015f oldu\u011fumuz “BusConfigurator” class’\u0131n\u0131 kullan\u0131yoruz. Devam\u0131nda ise bir queue endpoint’i belirleyerek, “busControl” \u00fcn “GetSendEndpoint” method’una g\u00f6nderiyoruz. Bu i\u015flemin\u00a0ard\u0131ndan art\u0131k\u00a0t\u00fcm messaging i\u015flemleri, initialize etti\u011fimiz\u00a0“ISendEndpoint” i \u00fczerinden devam edecektir. “CreateOrder” method’una bakt\u0131\u011f\u0131m\u0131zda ise art\u0131k \u00e7ok straightforward bir hale geldi\u011fini g\u00f6rebiliriz. Art\u0131k tek yapmam\u0131z gereken bus \u00fczerindeki “Send” method’unu \u00e7a\u011f\u0131rarak, i\u00e7erisine ilgili “IOrderCommand” interface’ini implemente etmi\u015f model’i vermek yeterli olacakt\u0131r.<\/p>\n
Art\u0131k producer haz\u0131r durumdad\u0131r. Dilerseniz consumer k\u0131sm\u0131na ba\u015flamadan \u00f6nce “MqConstants” ve “OrderController” i\u00e7erisinde tan\u0131mlam\u0131\u015f oldu\u011fumuz key’leri, config\u00a0dosyas\u0131na a\u015fa\u011f\u0131daki gibi ekleyelim.<\/p>\n
<add key=\"RabbitMQUri\" value=\"rabbitmq:\/\/localhost\/\"\/>\r\n<add key=\"RabbitMQUserName\" value=\"guest\"\/>\r\n<add key=\"RabbitMQPassword\" value=\"guest\"\/>\r\n<add key=\"OrderQueueName\" value=\"lightmessagingcore.boilerplate.order\"\/><\/pre>\n
Not<\/strong>: Bu makale kapsam\u0131nda RabbitMQ kurulumuna de\u011finmeyece\u011fim. Buradan<\/a> daha \u00f6nce yazm\u0131\u015f oldu\u011fum makaleye ula\u015farak,windows \u00fczerine kurulum bilgilerine eri\u015febilirsiniz veya docker \u00fczerine kurup, kullanabilirsiniz.<\/p><\/blockquote>\n
3.2)\u00a0Consumer’\u0131n Haz\u0131rlanmas\u0131<\/h4>\n
Consumer\u00a0i\u00e7in solution \u00fczerine “LightMessagingCore.Boilerplate.OrderService” isminde bir console application ekleyelim. Bu k\u0131s\u0131m microservice yakla\u015f\u0131m\u0131nda olup, olduk\u00e7a lightweight tutmaya \u00e7al\u0131\u015faca\u011f\u0131z. Di\u011fer projelerde oldu\u011fu gibi buraya da “LightMessagingCore.Boilerplate.Common”, “LightMessagingCore.Boilerplate.Messaging” library’lerini referans olarak ekeyerek, Nuget Package Manager \u00fczerinden “MassTransit.RabbitMQ” paketini de dahil edelim.<\/p>\n
\u015eimdi “Program.cs” e gelelim ve burada bus control’\u00fc initialize edelim.<\/p>\n
using System;\r\nusing LightMessagingCore.Boilerplate.Common;\r\nusing System.Configuration;\r\nusing MassTransit;\r\n\r\nnamespace LightMessagingCore.Boilerplate.OrderService\r\n{\r\n class Program\r\n {\r\n static void Main(string[] args)\r\n {\r\n Console.Title = \"OrderService\";\r\n\r\n var bus = BusConfigurator.Instance\r\n .ConfigureBus((cfg, host) =>\r\n {\r\n cfg.ReceiveEndpoint(host, ConfigurationManager.AppSettings[\"OrderQueueName\"], e =>\r\n {\r\n e.Consumer<OrderCommandConsumer>();\r\n });\r\n });\r\n\r\n bus.Start();\r\n\r\n Console.WriteLine(\"Listening order command..\");\r\n Console.ReadLine();\r\n }\r\n }\r\n}<\/pre>\nBurada da common projesi i\u00e7erisinde\u00a0daha \u00f6nce olu\u015fturmu\u015f oldu\u011fumuz “BusConfigurator” class’\u0131n\u0131 kullanarak, yeni bir bus initialize ediyoruz. Bu sefer farkl\u0131 olarak initializing k\u0131sm\u0131nda bir action method kullan\u0131yoruz ve olu\u015fturuyor oldu\u011fumuz configuration’\u0131n message’lar\u0131 consume edece\u011fi endpoint’i, “ReceiveEndpoint” method’u ile set ediyoruz ve ard\u0131ndan endpoint’in hangi consumer arac\u0131l\u0131\u011f\u0131 ile consuming i\u015flemini ger\u00e7ekle\u015ftirece\u011fini belirliyoruz. Konuyu toplamak gerekirse bu k\u0131s\u0131m art\u0131k bu uygulaman\u0131n kendisine set edilen endpoint \u00fczerinden, “OrderCommandConsumer” type’\u0131 ile consume i\u015flemini ger\u00e7ekle\u015ftirece\u011fini g\u00f6steriyor.<\/p>\n
Dilerseniz \u015fimdi “OrderCommandConsumer” \u0131 a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n
using System;\r\nusing System.Threading.Tasks;\r\nusing LightMessagingCore.Boilerplate.Messaging;\r\nusing MassTransit;\r\n\r\nnamespace LightMessagingCore.Boilerplate.OrderService\r\n{\r\n public class OrderCommandConsumer : IConsumer<IOrderCommand>\r\n {\r\n public async Task Consume(ConsumeContext<IOrderCommand> context)\r\n {\r\n var orderCommand = context.Message;\r\n\r\n await Console.Out.WriteAsync($\"Order code: {orderCommand.OrderCode} Order id: {orderCommand.OrderId}\");\r\n\r\n \/\/do something..\r\n }\r\n }\r\n}<\/pre>\nG\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi bu k\u0131s\u0131mda olduk\u00e7a basit bir durumda. Tek yapmam\u0131z gereken \u015fey MassTransit i\u00e7erisinde bulunan “IConsumer<T>” interface’ini, ilgili contract’\u0131m\u0131z ile implemente etmektir. “Consume” method’u ile de consume i\u015flemlerini ger\u00e7ekle\u015ftirmektedir.<\/p>\n
3.3)\u00a0Test<\/h4>\n
Evet consumer’da \u015fuan haz\u0131r durumdad\u0131r. Sizlerde fark ettiyseniz e\u011fer, MassTransit bir \u00e7ok konuda bizlere kolayl\u0131k ve h\u0131z sa\u011flamaktad\u0131r. Dilerseniz art\u0131k test i\u015flemlerine ge\u00e7ebiliriz. Bunun i\u00e7in solution ayarlar\u0131ndan multiple startup projects olarak, “OrderService” ve “OrderUI” projelerini se\u00e7elim ve start tu\u015funa basal\u0131m.<\/p>\n
Bu i\u015flemin ard\u0131ndan \u00f6ncelikle consumer g\u00f6revini g\u00f6recek olan “LightMessagingCore.Boilerplate.OrderService” projesi, a\u015fa\u011f\u0131daki gibi a\u00e7\u0131lacakt\u0131r.<\/p>\n
<\/a><\/p>\nOrder service art\u0131k “IOrderCommand” interface’ine sahip message’lar\u0131, consume durumundad\u0131r. Consumer’\u0131n ve Producer’\u0131n initialize olmas\u0131yla beraber dilerseniz RabbitMQ Management ekran\u0131 \u00fczerinden, exchange’lere bir bakal\u0131m.<\/p>\n
<\/a><\/p>\nBiz her iki uygulamada da sadece queue name olarak “lightmessagingcore.boilerplate.order” set etmi\u015ftik.<\/p>\n
Makalenin \u00fcst k\u0131s\u0131mlar\u0131nda hat\u0131rlarsak MassTransit’in verimlilik i\u00e7in, exchange’leri kendisinin y\u00f6netti\u011finden bahsetmi\u015ftik. \u0130\u015fte bu noktada yukar\u0131daki g\u00f6rselde oldu\u011fu gibi “LightMessagingCore.Boilerplate.Messaging:IOrderCommand” isimli exchange’i olu\u015fturmu\u015ftur. Burada “IOrderCommand” contract’\u0131 ile gelen message’lar\u0131 otomatik olarak kendisi a\u015fa\u011f\u0131da bulunan queue’ya bind etmektedir.<\/p>\n
<\/a><\/p>\n\u015eimdi “OrderUI” \u0131n oldu\u011fu tab’a gelelim ve a\u015fa\u011f\u0131daki gibi bir order create edelim.<\/p>\n
<\/a><\/p>\nCreate i\u015fleminin ard\u0131ndan “OrderService” ilgili message’\u0131 yakalay\u0131p, consume i\u015flemini a\u015fa\u011f\u0131daki gibi ger\u00e7ekle\u015ftirmi\u015ftir.<\/p>\n
![\"message-queue\"](\"\/wp-content\/uploads\/2016\/11\/message-queue.png\")
<\/a><\/p>\n