Her \u015feyden \u00f6nce yukar\u0131da olu\u015fturdu\u011fumuz projelere ilk ad\u0131m olarak a\u015fa\u011f\u0131daki k\u00fct\u00fcphanelerin y\u00fcklenmesi gerekmektedir;<\/p>\n

Servis<\/th>\n	T\u00fcr\u00fc<\/th>\n	A\u00e7\u0131klama<\/th>\n<\/tr>\n<\/thead>\n
Order.API<\/td>\n	Web API<\/td>\n	Kullan\u0131c\u0131 taraf\u0131ndan ba\u015flat\u0131lan sipari\u015fin al\u0131nmas\u0131n\u0131 ve sipari\u015fe dair stok ve \u00f6deme s\u00fcrecinin ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flayacak olan servistir.<\/td>\n<\/tr>\n
Order.Saga<\/td>\n	Worker Service<\/td>\n	\u0130lgili sipari\u015fe dair servisler aras\u0131ndaki ad\u0131m ad\u0131m i\u015fleyi\u015f neticesinin y\u00fcr\u00fct\u00fcld\u00fc\u011f\u00fc handler’lar\u0131n bar\u0131nd\u0131r\u0131laca\u011f\u0131 servistir. D\u00fc\u015f\u00fcnd\u00fc\u011f\u00fcn\u00fcz zaman bu servisin sorumlulu\u011funu direkt Order.API’\u0131n alabilece\u011fine ve sanki l\u00fczumsuz oldu\u011funa kanaat getirebilirsiniz. Ancak, Order.API’\u0131n kullan\u0131c\u0131yla etkile\u015fime girmekten ba\u015fka mesaj t\u00fcketme sorumlulu\u011funu \u00fcstlendirmek ilkelere ayk\u0131r\u0131 olaca\u011f\u0131ndan dolay\u0131 bu sorumlulu\u011fu farkl\u0131 bir servise y\u00fcklemek best practice a\u00e7\u0131s\u0131ndan daha uygun olacakt\u0131r.<\/td>\n<\/tr>\n
Stock.Service<\/td>\n	Worker Service<\/td>\n	Stok i\u015flemlerinin y\u00fcr\u00fct\u00fclece\u011fi servistir.<\/td>\n<\/tr>\n
Payment.Service<\/td>\n	Worker Service<\/td>\n	\u00d6deme i\u015flemlerinin y\u00fcr\u00fct\u00fclece\u011fi servistir.<\/td>\n<\/tr>\n
Shared<\/td>\n	Class Library<\/td>\n	Servisler aras\u0131nda kullan\u0131lacak t\u00fcm ortak message ve event yap\u0131lanmalar\u0131n\u0131 ve bunlar\u0131n yan\u0131nda belli ba\u015fl\u0131 queue isimleri gibi konfig\u00fcrasyonlar\u0131 bar\u0131nd\u0131racak olan ortak bir katmand\u0131r.<\/td>\n<\/tr>\n
Saga.Orchestration.Service<\/td>\n	Worker Service<\/td>\n	Servisler aras\u0131ndaki i\u015f ve g\u00f6rev s\u00fcrecini merkezi bir noktadan y\u00f6netmek \u00fczere tasarlanacak olan ve b\u00f6ylece Orchestration yakla\u015f\u0131m\u0131n\u0131 sa\u011flayacak olan servisin ta kendisidir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Ve bu servisler aras\u0131ndaki i\u015f ak\u0131\u015f\u0131 da a\u015fa\u011f\u0131daki gibi olacakt\u0131r;<\/p>\n \n Kullan\u0131c\u0131 `Order.API<\/code> \u00fczerinden bir sipari\u015f talebinde bulunacak ve s\u00fcreci ba\u015flatacakt\u0131r.<\/li>\n` `Order.API<\/code> sipari\u015fi veritaban\u0131na ekleyecek ve bunu Saga.Orchestration.Service<\/code>‘e bildirecektir.<\/li>\n` Saga.Orchestration.Service<\/code> ise olu\u015fturulan sipari\u015fe dair Stock.Service<\/code>‘e bilgide bulunacakt\u0131r. Stock.Service<\/code> sipari\u015fteki \u00fcr\u00fcnlere g\u00f6re stok \u00e7al\u0131\u015fmas\u0131 ger\u00e7ekle\u015ftirilecektir. Stok i\u015flemleri ba\u015far\u0131l\u0131 ya da ba\u015far\u0131s\u0131z olmak \u00fczere sonu\u00e7lanacak ve neticeye g\u00f6re Saga.Orchestration.Service<\/code>‘e bildiride bulunulacakt\u0131r.\n\nE\u011fer ki, Stock.Service<\/code> sipari\u015fe dair stok i\u015flemlerini ba\u015far\u0131yla ger\u00e7ekle\u015ftirdiyse o taktirde Payment.Service<\/code>‘e \u00f6deme i\u015flemleri i\u00e7in bilgide bulunacakt\u0131r.<\/li>\n Yok e\u011fer ba\u015far\u0131s\u0131z bir durum s\u00f6z konusuysa i\u015fte o taktirde Order.Saga<\/code> servisine sipari\u015fin ba\u015far\u0131yla sonu\u00e7lanamad\u0131\u011f\u0131na dair bilgi mesaj g\u00f6nderecek ve ilgili sipari\u015f iptal edilecektir.<\/li>\n<\/ol>\n<\/li>\n Payment.Service<\/code>‘te ise ilgili sipari\u015fe dair \u00f6deme ba\u015far\u0131l\u0131ysa e\u011fer bunun i\u00e7in Saga.Orchestration.Service<\/code>‘e bildiride bulunulacak ve o da, Order.Saga<\/code>‘ya sipari\u015fin ba\u015far\u0131yla sonu\u00e7land\u0131\u011f\u0131na dair mesaj yay\u0131nlayacakt\u0131r.<\/li>\n Yok e\u011fer \u00f6deme ger\u00e7ekle\u015ftirilemediyse hem sipari\u015fin iptal edilmesi hem de Stock.Service<\/code>‘te ilgili sipari\u015fe dair yap\u0131lan stok i\u015flemlerinin geri al\u0131nmas\u0131 i\u00e7in Saga.Orchestration.Service<\/code>‘e bildiride bulunacak, o da, sipari\u015fi iptal etmesi i\u00e7in Order.Saga<\/code>‘ya ve yap\u0131lan stok \u00e7al\u0131\u015fmalar\u0131n\u0131n geri al\u0131nmas\u0131 i\u00e7in de Stock.Service<\/code>‘e mesaj yollayacakt\u0131r.<\/li>\n<\/ol>\n\u0130lk Ad\u0131m<\/h5>\nHer \u015feyden \u00f6nce yukar\u0131da olu\u015fturdu\u011fumuz projelere ilk ad\u0131m olarak a\u015fa\u011f\u0131daki k\u00fct\u00fcphanelerin y\u00fcklenmesi gerekmektedir;<\/p>\n \nRebus.ServiceProvider<\/a> \nRebus.RabbitMq<\/a> \nRebus.SqlServer<\/a>\n<\/div>\nKazmay\u0131 Vural\u0131m<\/h5>\nProjelere ilgili k\u00fct\u00fcphaneleri y\u00fckledi\u011fimize g\u00f6re art\u0131k genel senaryonun in\u015fas\u0131na ba\u015flayabiliriz. Bunun i\u00e7in a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 s\u0131ras\u0131yla seyretmemiz yeterli olacakt\u0131r kanaatindeyim…<\/p>\n\nAd\u0131m 1<\/em><\/strong> Order.API – (Order Entity’sinin Olu\u015fturulmas\u0131, Veritaban\u0131 Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131 ve Migration \u0130\u015flemleri)<\/span> \n\u0130lk olarak kullan\u0131c\u0131 taraf\u0131ndan verilecek olan sipari\u015fin Order.API<\/code> taraf\u0131nda altyap\u0131s\u0131n\u0131 kurgulamam\u0131z gerekmektedir. Bunun i\u00e7in a\u015fa\u011f\u0131daki ‘Order’ entity’sinden istifade edebiliriz.<\/p>\n\n\r\n public class Order\r\n {\r\n public int Id { get; set; }\r\n public int BuyerId { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n public OrderStatus OrderStatus { get; set; }\r\n public DateTime CreatedDate { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nTabi bu entity i\u00e7erisindeki ‘OrderItem’ ve ‘OrderStatus’ t\u00fcrleri de a\u015fa\u011f\u0131daki gibi olacakt\u0131r.<\/p>\n\n\r\n public class OrderItem\r\n {\r\n public int Id { get; set; }\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public enum OrderStatus\r\n {\r\n Suspend,\r\n Completed,\r\n Fail\r\n }\r\n<\/pre>\n<\/div>\nSipari\u015f entity’sini olu\u015fturdu\u011fumuza g\u00f6re \u015fimdi s\u0131rada DbContext nesnesini olu\u015fturmam\u0131z gerekmektedir.<\/p>\n \n\r\n public class ApplicationDbContext : DbContext\r\n {\r\n public ApplicationDbContext(DbContextOptions options) : base(options)\r\n {\r\n }\r\n\r\n public DbSet<Order.API.Models.Entities.Order> Orders { get; set; }\r\n public DbSet<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nArd\u0131ndan olu\u015fturulan bu yap\u0131y\u0131 uygulaman\u0131n ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rmam\u0131z gerekmektedir.<\/p>\n \n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddDbContext<ApplicationDbContext>(options =>\r\n options.UseSqlServer(builder.Configuration.GetConnectionString("SQLServer")));\r\n\r\nvar app = builder.Build();\r\n.\r\n.\r\n.\r\napp.Run();\r\n<\/pre>\n<\/div>\nVe son olarak da add-migration mig_1<\/code> talimat\u0131yla migration basal\u0131m ve \nupdate-database<\/code> talimat\u0131yla da migrate ederek veritaban\u0131n\u0131 sunucuda olu\u015ftural\u0131m.<\/a>(Not: Bu ad\u0131m\u0131 uygularken s\u00fcre\u00e7te ihtiya\u00e7 olabilecek baz\u0131 k\u00fct\u00fcphanelerin y\u00fcklendi\u011fi varsay\u0131lm\u0131\u015ft\u0131r. Bu k\u00fct\u00fcphaneler; EF Core i\u00e7in Microsoft.EntityFrameworkCore<\/a>, EF Core’da SQL Server’\u0131n kullan\u0131labilmesi i\u00e7in Microsoft.EntityFrameworkCore.SqlServer<\/a> ve package manager console \u00fczerinden migration i\u015flemlerinin y\u00fcr\u00fct\u00fclebilmesi i\u00e7in Microsoft.EntityFrameworkCore.Tools<\/a> k\u00fct\u00fcphaneleridir.)<\/span>\n<\/li>\n Ad\u0131m 2<\/em><\/strong> Order.API – (Sipari\u015fin Olu\u015fturulmas\u0131)<\/span> \nKullan\u0131c\u0131dan gelecek olan sipari\u015f i\u00e7in temel altyap\u0131y\u0131 kurgulad\u0131\u011f\u0131m\u0131za g\u00f6re art\u0131k sipari\u015fin olu\u015fturulmas\u0131na odaklanabiliriz. Bunun i\u00e7in \u00f6ncelikle kullan\u0131c\u0131dan sipari\u015fin bilgilerini alabilece\u011fimiz a\u015fa\u011f\u0131daki viewmodel nesnelerini olu\u015ftural\u0131m.<\/p>\n\n\r\n public class CreateOrderVM\r\n {\r\n public int BuyerId { get; set; }\r\n public List<CreateOrderItemVM> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class CreateOrderItemVM\r\n {\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nArd\u0131ndan sipari\u015fin olu\u015fturulmas\u0131n\u0131 sa\u011flayacak olan endpoint’i a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n.\r\n.\r\n.\r\nvar app = builder.Build();\r\n.\r\n.\r\n.\r\napp.MapPost("\/create-order", async (ApplicationDbContext context, CreateOrderVM model) =>\r\n{\r\n Order.API.Models.Entities.Order order = new()\r\n {\r\n BuyerId = model.BuyerId,\r\n OrderItems = model.OrderItems.Select(oi => new OrderItem\r\n {\r\n Count = oi.Count,\r\n Price = oi.Price,\r\n ProductId = oi.ProductId\r\n }).ToList(),\r\n OrderStatus = OrderStatus.Suspend,\r\n TotalPrice = model.OrderItems.Sum(oi => oi.Count * oi.Price),\r\n CreatedDate = DateTime.Now\r\n };\r\n\r\n await context.Orders.AddAsync(order);\r\n await context.SaveChangesAsync();\r\n return Results.Created();\r\n});\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere sipari\u015fe dair distributed s\u00fcrecin tamamlanmas\u0131n\u0131 bekleyece\u011fimizden dolay\u0131 ilk etapta Suspend<\/em> olarak olu\u015fturmaktay\u0131z.\n<\/li>\nAd\u0131m 3<\/em><\/strong> Stock.Service – (MongoDB Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131 ve \u00dcr\u00fcn Stok Bilgilerine Dair Dummy Datalar\u0131n Eklenmesi)<\/span> \nGelecek olan sipari\u015fin stok i\u015flemlerine dair de Stock.Service<\/code>‘de bir altyap\u0131 olu\u015fturmam\u0131z gerekmektedir. Bu altyap\u0131 i\u00e7eri\u011fi zenginle\u015ftirmek maksad\u0131yla MongoDB \u00fczerine kurgulanm\u0131\u015f olacakt\u0131r. Bunun i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki ‘MongoDBService’i olu\u015ftural\u0131m.<\/p>\n\n\r\n public class MongoDBService\r\n {\r\n readonly IMongoDatabase _database;\r\n readonly IConfiguration _configuration;\r\n public MongoDBService(IConfiguration configuration)\r\n {\r\n _configuration = configuration;\r\n MongoClient client = new(_configuration["MongoDB:Server"]);\r\n _database = client.GetDatabase(_configuration["MongoDB:DatabaseName"]);\r\n }\r\n public IMongoCollection<T> GetCollection<T>() => _database.GetCollection<T>(typeof(T).Name.ToLowerInvariant());\r\n }\r\n<\/pre>\n<\/div>\nTabi bu servisi olu\u015fturabilmek i\u00e7in MongoDB.Driver<\/a> k\u00fct\u00fcphanesinin ilgili servise y\u00fcklenmesi gerekmektedir.<\/p>\n Ba\u011flant\u0131 sa\u011flayaca\u011f\u0131m\u0131z MongoDB sunucusu bilgilerini de a\u015fa\u011f\u0131daki gibi appsettings.json dosyas\u0131na kaydedelim.<\/p>\n \n\r\n "MongoDB": {\r\n "Server": "mongodb:\/\/localhost:27017",\r\n "DatabaseName": "SagaOrchestrationRebusDB"\r\n }\r\n<\/pre>\n<\/div>\nVe ard\u0131ndan ilgili servisi, projenin ‘Program.cs’ dosyas\u0131 \u00fczerinden a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rarak uygulaman\u0131n IoC Container’\u0131na ekleyelim.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddSingleton<MongoDBService>();\r\n\r\nvar host = builder.Build();\r\n.\r\n.\r\n.\r\nhost.Run();\r\n<\/pre>\n<\/div>\nDevam\u0131nda ise MongoDB veritaban\u0131nda stok bilgilerini tutacak a\u015fa\u011f\u0131daki entity’i olu\u015ftural\u0131m.<\/p>\n\n\r\n public class Stock\r\n {\r\n [BsonRepresentation(BsonType.ObjectId)]\r\n [BsonId]\r\n [BsonElement(Order = 0)]\r\n public ObjectId Id { get; set; }\r\n [BsonRepresentation(BsonType.Int64)]\r\n [BsonElement(Order = 1)]\r\n public int ProductId { get; set; }\r\n [BsonRepresentation(BsonType.Int64)]\r\n [BsonElement(Order = 2)]\r\n public int Count { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nVe bu entity e\u015fli\u011finde yukar\u0131da yap\u0131land\u0131rd\u0131\u011f\u0131m\u0131z servis sayesinde \u00fcr\u00fcnlerin stok bilgilerini bar\u0131nd\u0131ran dummy datalar\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddSingleton<MongoDBService>();\r\n\r\nvar host = builder.Build();\r\n\r\nusing var scope = builder.Services.BuildServiceProvider().CreateScope();\r\nvar mongoDbService = scope.ServiceProvider.GetRequiredService<MongoDBService>();\r\nif (!await (await mongoDbService.GetCollection<Stock.Service.Models.Stock>().FindAsync(x => true)).AnyAsync())\r\n{\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 1,\r\n Count = 200\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 2,\r\n Count = 300\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 3,\r\n Count = 50\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 4,\r\n Count = 10\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 5,\r\n Count = 60\r\n });\r\n}\r\n\r\nhost.Run();\r\n<\/pre>\n<\/div>\nArt\u0131k bu \u00e7al\u0131\u015fmalar e\u015fli\u011finde Stock.Service<\/code>‘in bir kere aya\u011fa kald\u0131r\u0131lmas\u0131 hem veritaban\u0131n\u0131n hem de dummy datalar\u0131n olu\u015fturulmas\u0131 a\u00e7\u0131s\u0131ndan yeterli olacakt\u0131r.<\/a>\n<\/li>\n Ad\u0131m 4<\/em><\/strong> Shared – (BaseCorrelation S\u0131n\u0131f\u0131n\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u0130\u00e7eri\u011fimizin sonraki ad\u0131mlar\u0131nda Rebus ile Saga Orchestration davran\u0131\u015f\u0131n\u0131 uygularken geli\u015ftirece\u011fimiz merkezi Saga yap\u0131lanmas\u0131nda, servislerden gelecek olan mesajlar\u0131 e\u015fle\u015ftirmemizi ve bu mesajlar\u0131n ayn\u0131 i\u015f ak\u0131\u015f\u0131 i\u00e7erisinde belirli bir sipari\u015fe kar\u015f\u0131l\u0131k ili\u015fkilendirmemizi sa\u011flayacak olan korelasyon yap\u0131s\u0131n\u0131 olu\u015fturmam\u0131z gerekmektedir. Bu yap\u0131, herhangi bir de\u011fer olabilir. Usul gere\u011fi m\u00fcmk\u00fcn mertebe unique olmas\u0131na \u00f6zen g\u00f6sterilmesi gerekece\u011finden dolay\u0131 biz bu ihtiyaca istinaden ‘BaseCorrelation’ s\u0131n\u0131f\u0131 ile \u00e7\u00f6z\u00fcm getiriyor olaca\u011f\u0131z. Haliyle ilgili s\u0131n\u0131f\u0131n i\u00e7eri\u011fini Shared<\/code> class library’sinde a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m;<\/p>\n\n\r\n [Serializable]\r\n public class BaseCorrelation\r\n {\r\n public BaseCorrelation() { }\r\n public BaseCorrelation(Guid correlationId)\r\n {\r\n CorrelationId = correlationId;\r\n }\r\n [DataMember]\r\n public Guid CorrelationId { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere ‘BaseCorrelation’ s\u0131n\u0131f\u0131 i\u00e7erisinde ‘Guid’ t\u00fcr\u00fcnden bir de\u011fer al\u0131nmakta ve bu ‘CorrelationId’ property’sinde saklanmaktad\u0131r. B\u00f6ylece sistemde olu\u015fturulacak t\u00fcm message ve event yap\u0131lanmalar\u0131n\u0131 bu s\u0131n\u0131ftan t\u00fcreterek, ayn\u0131 i\u015f ak\u0131\u015f\u0131ndaki farkl\u0131 olaylar\u0131 ve mesajlar\u0131, ortak bir ba\u011flam bilgisi olmas\u0131 amac\u0131yla \u00fcretilmi\u015f olan korelasyon de\u011feri \u00fczerinden e\u015fle\u015ftirecek ve tek bir sipari\u015fe kar\u015f\u0131n olay zincirinin ba\u011f\u0131n\u0131 kurguluyor olaca\u011f\u0131z.\n<\/li>\nAd\u0131m 5<\/em><\/strong> Saga.Orchestration.Service – (Saga Orchestration Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131)<\/span> \nRebus k\u00fct\u00fcphanesiyle yap\u0131lan Orchestration operasyonunda t\u0131pk\u0131 MassTransit ile yapm\u0131\u015f oldu\u011fumuz \u00e7al\u0131\u015fmada oldu\u011fu gibi belli ba\u015fl\u0131 davran\u0131\u015flara sahip nesneler senaryoda sorumluluk \u00fcstlenmekte ve haliyle \u00f6ncelikle bu nesnelerin \u00fcretilmesi gerekmektedir. \u015eimdi gelin bu nesneleri tek tek izah ederek ilerleyelim;<\/p>\n\nSaga Data Nesnesi<\/u><\/em> \nOrchestration operasyonu s\u00fcrecinde distributed bir \u015fekilde takip edilen ak\u0131\u015f\u0131n veri format\u0131n\u0131 temsil eden bir nesnedir. Bizim \u00f6rnek senaryomuzda bu bir sipari\u015f modeline kar\u015f\u0131l\u0131k gelmekte ve bir sipari\u015fle ilgili servisler aras\u0131 ileti\u015fim s\u00fcrecindeki verilerin geli\u015fimini takip etmemizi sa\u011flayacak olan bilgileri bar\u0131nd\u0131racak olan bir nesneyi ifade etmektedir. B\u00f6ylece bizler saga data nesnesi sayesinde distributed ak\u0131\u015ftaki olgunun state’ini tutabilmekte ve y\u00f6netebilmekteyiz.<\/p>\nBir s\u0131n\u0131f\u0131n saga data s\u0131n\u0131f\u0131 olabilmesi i\u00e7in ISagaData<\/code> interface’inden implemente edilmesi gerekmektedir.<\/p>\n\n\r\n public class OrderSagaData : BaseCorrelation, ISagaData\r\n {\r\n public Guid Id { get; set; }\r\n public int Revision { get; set; }\r\n public int OrderId { get; set; }\r\n public int BuyerId { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131da g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bir sipari\u015f s\u00fcrecinin state’ini takip etmemizi sa\u011flayacak olan ‘OrderSagaData’ s\u0131n\u0131f\u0131n\u0131 olu\u015fturmu\u015f bulunuyoruz. Burada dikkatinizi bir \u00f6nceki ad\u0131mda olu\u015fturdu\u011fumuz ‘BaseCorrelation’ s\u0131n\u0131f\u0131na \u00e7ekmek isterim. Evet, olu\u015fturdu\u011fumuz bu saga data nesnesi her ne kadar sipari\u015f state’ini tutacak olsa da hangi sipari\u015fe dair state’i tuttu\u011funu anlayabilmek i\u00e7in bunu da ‘BaseCorrelation’dan t\u00fcretiyor ve bu s\u0131n\u0131ftaki korelasyon yap\u0131lanmas\u0131n\u0131 saga data nesnesine aktar\u0131yoruz.<\/p>\n Ayr\u0131ca yukar\u0131da kullan\u0131lan ‘OrderItem’ referans\u0131n\u0131 da Shared<\/code> i\u00e7erisinde a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderItem\r\n {\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n<\/li>\nSaga Nesnesi<\/u><\/em> \nOrchestration yakla\u015f\u0131m\u0131n\u0131 uygulamam\u0131z\u0131 sa\u011flayacak olan, bir i\u015fin-ak\u0131\u015f\u0131n yani \u00f6rnek senaryomuzdaki sipari\u015f s\u00fcrecinin temsil edilmesine ve servisler aras\u0131ndaki koordinasyonun merkezi bir \u015fekilde y\u00fcr\u00fct\u00fclmesine imkan tan\u0131yacak olan s\u0131n\u0131f\u0131n ta kendisidir.<\/p>\nBizler saga s\u0131n\u0131f\u0131 sayesinde servisler aras\u0131ndaki mesajla\u015fmalar\u0131 takip edebilmekte, durumlar\u0131 y\u00f6netebilmekte ve i\u015f s\u00fcrecine uygun bir \u015fekilde durumlar aras\u0131 ge\u00e7i\u015fler yapabilmekteyiz.<\/p>\n Bir s\u0131n\u0131f\u0131n saga s\u0131n\u0131f\u0131 olabilmesi i\u00e7in Saga<T><\/code> abstract class’\u0131n\u0131 implemente etmesi gerekmektedir. \u015e\u00f6yle ki;<\/p>\n \n\r\n public class OrderSaga : Saga<OrderSagaData>\r\n {\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n\r\n }\r\n }\r\n<\/pre>\n<\/div>\nEvet, yukar\u0131daki kod blo\u011funda g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bizler ‘OrderSaga’ ad\u0131nda bir saga nesnesi olu\u015fturmu\u015f bulunuyoruz. \u0130\u00e7erik s\u00fcrecinde bu nesnenin hacminin farkl\u0131 implementasyonlarla geni\u015fledi\u011fini g\u00f6r\u00fcyor olacaks\u0131n\u0131z. \u015eimdilik en sade haliyle incelememiz gerekirse e\u011fer <T><\/code> parametresine verilen ‘OrderSagaData’ nesnesine dikkatinizi \u00e7ekerim. Evet, saga nesnesi sayesinde servisler aras\u0131 i\u015f ak\u0131\u015f s\u00fcrecini gelen message ve event’lere g\u00f6re merkezi bir \u015fekilde y\u00f6netecek ve ileti\u015fimi ger\u00e7ekle\u015ftiriyor olaca\u011f\u0131z lakin bunu yaparken de i\u015fleyece\u011fimiz verinin t\u00fcr\u00fcn\u00fcn ‘OrderSagaData’ olaca\u011f\u0131n\u0131 bildirmi\u015f oluyoruz. Bizler i\u015f ak\u0131\u015f s\u00fcrecinin(yani sipari\u015f s\u00fcrecinin) hangi noktas\u0131nda ya da hangi servisinde olursak olal\u0131m ona g\u00f6re arkada \u00fcretilmi\u015f olan ‘OrderSagaData’ nesnesinin de\u011ferleri \u015fekillenecek ve kuraca\u011f\u0131m\u0131z korelasyon a\u011f\u0131yla da tek bir ba\u011flamla i\u00e7erisinde bir sipari\u015fin en nihai halini yine bu nesne \u00fczerinden elde edebiliyor olaca\u011f\u0131z.<\/p>\n Ayr\u0131ca Saga<\/code> abstract class’\u0131n\u0131n implemente ettirdi\u011fi CorrelateMessages<\/em> isimli metotta ise birazdan olu\u015fturaca\u011f\u0131m\u0131z ve s\u00fcre\u00e7te i\u015flemeye \u00e7al\u0131\u015faca\u011f\u0131m\u0131z message ve event’lerin, saga data s\u0131n\u0131f\u0131m\u0131z olan ‘OrderSagaData’ nesnesiyle e\u015fle\u015ftirilmesini ve bir olguya yani sipari\u015fe dair korelasyon a\u011f\u0131n\u0131n kurulmas\u0131n\u0131 sa\u011fl\u0131yor olaca\u011f\u0131z. Oraya gelece\u011fiz, \u015fimdi bunun i\u00e7in \u00f6ncelikle \u00e7al\u0131\u015fmada kullanaca\u011f\u0131m\u0131z event ve message’lar\u0131n olu\u015fturulmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.\n<\/li>\n<\/ul>\n<\/li>\n Ad\u0131m 6<\/em><\/strong> Shared – (Event ve Message’lar\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u015eimdi kurguda kullanaca\u011f\u0131m\u0131z t\u00fcm event ve message yap\u0131lanmalar\u0131n\u0131 sorumluluklar\u0131n\u0131 izah ederek tek tek olu\u015fturmaya odaklanal\u0131m. Burada olu\u015fturaca\u011f\u0131m\u0131z t\u00fcm event ve message’lar\u0131n korelasyon ili\u015fkisini sa\u011flayabilmek i\u00e7in ba\u015ftan 4. ad\u0131mda olu\u015fturdu\u011fumuz ‘BaseCorrelation’ s\u0131n\u0131f\u0131ndan t\u00fcretildi\u011fini vurgulamakta fayda g\u00f6rmekteyim.<\/p>\n\nOrderStartedEvent<\/em> \nKullan\u0131c\u0131 taraf\u0131ndan sipari\u015f verildi\u011fi an s\u00fcrecin ba\u015flad\u0131\u011f\u0131n\u0131 Saga.Orchestration.Service<\/code>‘e bildirecek olan event’tir. Yani MassTransit ile yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmadaki Tetikleyici Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir. Bu event yay\u0131nland\u0131\u011f\u0131 taktirde Saga.Orchestration.Service<\/code>‘in veritaban\u0131nda ‘OrderSagaData’ya kar\u015f\u0131l\u0131k bir sat\u0131r olu\u015fturulacak ve distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecindeki t\u00fcm ilerlemeler ad\u0131m ad\u0131m bu sat\u0131r \u00fczerinden takip ediliyor olacakt\u0131r.<\/p>\n\n\r\n public class OrderStartedEvent : BaseCorrelation\r\n {\r\n public OrderStartedEvent() { }\r\n public OrderStartedEvent(Guid correlationId) : base(correlationId) { }\r\n public int OrderId { get; set; }\r\n public int BuyerId { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n<\/li>\nOrderCreatedEvent<\/em> \nSipari\u015f olu\u015fturulduktan ve s\u00fcre\u00e7 ba\u015flat\u0131ld\u0131ktan sonra Stock.Service<\/code>‘i tetikleyebilmek i\u00e7in yay\u0131nlanacak event’tir.<\/p>\n\n\r\n public class OrderCreatedEvent : BaseCorrelation\r\n {\r\n public OrderCreatedEvent(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem>? OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n OrderCompletedEvent<\/em> \nSipari\u015fe dair t\u00fcm servislerin i\u015flemlerini ba\u015far\u0131yla tamamland\u0131\u011f\u0131n\u0131 ve sipari\u015fin ba\u015far\u0131yla sonland\u0131\u011f\u0131n\u0131 ifade eden event’tir. Saga.Orchestration.Service<\/code>, bu event’i yay\u0131nlad\u0131\u011f\u0131 taktirde Order.Saga<\/code> servisi sipari\u015fin durumunu Completed<\/em>‘a \u00e7ekecektir. MassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.<\/p>\n\n\r\n public class OrderCompletedEvent\r\n {\r\n public int OrderId { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nAyr\u0131ca bu event’in dikkat ederseniz herhangi bir korelasyon de\u011feri bulunmamaktad\u0131r. \u00c7\u00fcnk\u00fc bu event, sipari\u015fin sonland\u0131\u011f\u0131n\u0131 ifade edece\u011finden dolay\u0131 bu bilgiyi i\u00e7erisindeki ‘OrderId’ ile ta\u015f\u0131yacak ve art\u0131k korelasyonel bir ba\u011flam i\u00e7erisinde \u00e7al\u0131\u015fmaya gerek kalmayacakt\u0131r. Bu mant\u0131kla i\u00e7eri\u011fin devam\u0131nda tecr\u00fcbe edilece\u011fi \u00fczere, OrderCompletedEvent<\/em> event’inin yay\u0131nlanaca\u011f\u0131 noktada Saga.Orchestration.Service<\/code> taraf\u0131ndan ilgili sipari\u015fe dair saga bilgisi tamamlanacak ve veritaban\u0131ndan kald\u0131r\u0131lm\u0131\u015f olacakt\u0131r. Yani birnevi sipari\u015f saga a\u00e7\u0131s\u0131ndan Finilize edilmi\u015f olacakt\u0131r. O noktaya geldi\u011fimizde bunu tekrardan hat\u0131rlataca\u011f\u0131m.\n<\/li>\n OrderFailedEvent<\/em> \nSipari\u015fe dair distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecinde servislerden herhangi birinde bir ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n s\u00f6z konusu oldu\u011funu yani uzun laf\u0131n k\u0131sas\u0131 sipari\u015fin ba\u015far\u0131s\u0131z oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class OrderFailedEvent : BaseCorrelation\r\n {\r\n public OrderFailedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n\r\n public int OrderId { get; set; }\r\n public string Message { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nBu event Saga.Orchestration.Service<\/code> taraf\u0131ndan yay\u0131nland\u0131\u011f\u0131 taktirde Order.Saga<\/code> taraf\u0131ndan ilgili sipari\u015fe dair state Fail<\/em>‘a \u00e7ekilecektir. MassTransit’te ki Ba\u015fars\u0131z\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockReservedEvent<\/em> \nSipari\u015fe dair Stock.Service<\/code>‘de ki stok i\u015flemlerinin ba\u015far\u0131l\u0131 oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class StockReservedEvent : BaseCorrelation\r\n {\r\n public StockReservedEvent(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockNotReservedEvent<\/em> \nSipari\u015fe dair Stock.Service<\/code>‘de ki stok i\u015flemlerinde ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class StockNotReservedEvent : BaseCorrelation\r\n {\r\n public StockNotReservedEvent(Guid correlationId) : base(correlationId) { }\r\n public string Message { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131s\u0131z Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentStartedEvent<\/em> \nStock.Service<\/code> i\u015flemini ba\u015far\u0131yla tamamlad\u0131\u011f\u0131 taktirde Payment.Service<\/code>‘i tetikleyecek ve \u00f6deme s\u00fcrecini ba\u015flatacak olan event’tir.<\/p>\n\n\r\n public class PaymentStartedEvent : BaseCorrelation\r\n {\r\n public PaymentStartedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentCompletedEvent<\/em> \nSipari\u015fe dair Payment.Service<\/code>‘de \u00f6deme i\u015flemlerinin ba\u015far\u0131l\u0131 oldu\u011funu ifade eden event\u2019tir.<\/p>\n\n\r\n public class PaymentCompletedEvent : BaseCorrelation\r\n {\r\n public PaymentCompletedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentFailedEvent<\/em> \nSipari\u015fe dair Payment.Service<\/code>‘de ki \u00f6deme i\u015flemlerinde ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class PaymentFailedEvent : BaseCorrelation\r\n {\r\n public List<OrderItem> OrderItems { get; set; }\r\n public string Messages { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131s\u0131z Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockRollbackMessage<\/em> \nPayment.Service<\/code>‘te PaymentFailedEvent<\/em> event\u2019i yay\u0131nlan\u0131rsa e\u011fer Stock.Service<\/code>‘de ki yap\u0131lan i\u015flemlerin geri al\u0131nmas\u0131n\u0131 sa\u011flayacak olan message’d\u0131r.<\/p>\n\n\r\n public class StockRollbackMessage : BaseCorrelation\r\n {\r\n public StockRollbackMessage(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Compensable Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n<\/ol>\n<\/li>\n Ad\u0131m 7<\/em><\/strong> Saga.Orchestration.Service – (OrderSaga \u0130\u00e7erisinde Korelasyon \u0130li\u015fkisini Ger\u00e7ekle\u015ftirme)<\/span> \nEvent ve message’lar\u0131 da olu\u015fturdu\u011fumuza g\u00f6re art\u0131k 5. ad\u0131mda bahsi ge\u00e7en korelasyonel a\u011f\u0131 olu\u015fturmaya odaklanabiliriz. Bunun i\u00e7in Saga.Orchestration.Service<\/code> i\u00e7erisinde olu\u015fturdu\u011fumuz ‘OrderSaga’ s\u0131n\u0131f\u0131ndaki CorrelateMessages<\/em> metodunda a\u015fa\u011f\u0131daki geli\u015ftirmeyi ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n public class OrderSaga : Saga<OrderSagaData>\r\n {\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n config.Correlate<OrderStartedEvent>(\r\n orderStartedEvent => orderStartedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<StockReservedEvent>(\r\n stockReservedEvent => stockReservedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<StockNotReservedEvent>(\r\n stockNotReservedEvent => stockNotReservedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<PaymentCompletedEvent>(\r\n paymentCompletedEvent => paymentCompletedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<PaymentFailedEvent>(\r\n paymentFailedEvent => paymentFailedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131daki \u00e7al\u0131\u015fmay\u0131 incelerseniz e\u011fer servislerden Saga.Orchestration.Service<\/code>‘e gelecek olan event’lerin ‘CorrelationId’ de\u011ferinin, ‘OrderSagaData’ t\u00fcr\u00fcnden olan saga data’n\u0131n ‘CorrelationId’ ile e\u015fle\u015ftirilmesini Correlate<T><\/code> metoduyla ger\u00e7ekle\u015ftiriyoruz. B\u00f6ylece bir sipari\u015f s\u00fcrecinde distributed i\u015f ak\u0131\u015f\u0131na dair takibin hangi ba\u011flam \u00e7er\u00e7evesinde oldu\u011funu bu korelasyonel a\u011f sayesinde ili\u015fkilendirerek s\u0131n\u0131rlam\u0131\u015f oluyoruz.<\/p>\n Art\u0131k korelasyonel a\u011f\u0131 da kurgulad\u0131\u011f\u0131m\u0131za g\u00f6re art\u0131k saga nesnesindeki operasyonlara odaklanabiliriz.\n<\/li>\n Ad\u0131m 8<\/em><\/strong> Saga.Orchestration.Service – (OrderSaga’n\u0131n IAmInitiatedBy ve IHandleMessages \u0130mplementasyonlar\u0131n\u0131n Ger\u00e7ekle\u015ftirilmesi)<\/span> \nS\u0131rada sipari\u015f s\u00fcrecindeki distributed ak\u0131\u015f\u0131n nas\u0131l olaca\u011f\u0131n\u0131 handle etmek vard\u0131r. Yani saga nesnesine gelen event’lere kar\u015f\u0131n hangi servise hangi event’in ya da message’\u0131n g\u00f6nderilece\u011fini ayarlamam\u0131z gerekmektedir. Bunun i\u00e7in Saga.Orchestration.Service<\/code>‘de ki saga nesnesinde a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\n public class OrderSaga :\r\n Saga<OrderSagaData>,\r\n IAmInitiatedBy<OrderStartedEvent>,\r\n IHandleMessages<StockReservedEvent>,\r\n IHandleMessages<StockNotReservedEvent>,\r\n IHandleMessages<PaymentCompletedEvent>,\r\n IHandleMessages<PaymentFailedEvent>\r\n {\r\n public Task Handle(OrderStartedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(StockReservedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(StockNotReservedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(PaymentCompletedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(PaymentFailedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n .\r\n .\r\n .\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere IAmInitiatedBy<\/code> ve IHandleMessages<\/code> interface’leri kullan\u0131lmaktad\u0131r. Bu interface’ler ile saga nesnesine di\u011fer servislerden gelecek olan event ve message’lar tan\u0131mlanarak, gerekli aksiyonlar sa\u011flanabilmektedir. Bu interface’lerin definition’lar\u0131na g\u00f6z atarsak e\u011fer;<\/p>\n \n\r\npublic interface IAmInitiatedBy<in TMessage> : IHandleMessages<TMessage> { }\r\n<\/pre>\n<\/div>\n\n\r\npublic interface IHandleMessages { }\r\n\r\npublic interface IHandleMessages<in TMessage> : IHandleMessages\r\n{\r\n Task Handle(TMessage message);\r\n}\r\n<\/pre>\n<\/div>\n\u015feklinde olduklar\u0131n\u0131 g\u00f6r\u00fcr\u00fcz. Yani bu interface’lerin her ikisinin de implementasyonunun da Task Handle(TMessage message);<\/code> imzas\u0131na kar\u015f\u0131n bir metodun uygulat\u0131ld\u0131\u011f\u0131n\u0131 s\u00f6yleyebiliriz. Dolay\u0131s\u0131yla yukar\u0131daki \u00e7al\u0131\u015fmada 9<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki Handle metot tan\u0131mlar\u0131 bu implementasyonlara kar\u015f\u0131n olu\u015fturulmu\u015ftur.<\/p>\n Burada IAmInitiatedBy<\/code> interface’i, saga’n\u0131n(yani kurgumuz gere\u011fi bir sipari\u015fin) ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flayacak event’i temsil etmektedir. 3.<\/em><\/strong> sat\u0131ra g\u00f6z atarsan\u0131z e\u011fer bu event’in OrderStartedEvent<\/em> oldu\u011fu ifade edilmekte ve b\u00f6ylece bu event yay\u0131nland\u0131\u011f\u0131 taktirde saga nesnesinin yeni bir saga data olu\u015fturaca\u011f\u0131 bildirilmi\u015f olmaktad\u0131r. Ve bu event’e kar\u015f\u0131n 9<\/em><\/strong> ile 12.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki ilgili t\u00fcr\u00fc handle eden metot tetiklenecektir.<\/p>\n IHandleMessages<\/code> interface’i ise di\u011fer event yahut message’lar\u0131 temsil etmektedir. Bu interface ile belirtilen event’lerin yay\u0131nlanmas\u0131 durumunda bu saga nesnesi taraf\u0131ndan bunlar\u0131n kar\u015f\u0131lanabilece\u011fini ifade etmemizi sa\u011flamaktad\u0131r. 14<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki metotlar ise gelecek event’in t\u00fcr\u00fcne uygun olacak \u015fekilde tetiklenecektir.\n<\/li>\n Ad\u0131m 9<\/em><\/strong> Saga.Orchestration.Service – (HandleMessage Operasyonlar\u0131n\u0131 Ger\u00e7ekle\u015ftirme)<\/span> \n\u015eimdi de handle metotlar\u0131ndaki gerekli \u00e7al\u0131\u015fmalar\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n public class OrderSaga(IBus bus) :\r\n Saga<OrderSagaData>,\r\n IAmInitiatedBy<OrderStartedEvent>,\r\n IHandleMessages<StockReservedEvent>,\r\n IHandleMessages<StockNotReservedEvent>,\r\n IHandleMessages<PaymentCompletedEvent>,\r\n IHandleMessages<PaymentFailedEvent>\r\n {\r\n public async Task Handle(OrderStartedEvent message)\r\n {\r\n if (!IsNew)\r\n return;\r\n\r\n Data.OrderId = message.OrderId;\r\n Data.BuyerId = message.BuyerId;\r\n Data.OrderItems = message.OrderItems;\r\n Data.TotalPrice = message.TotalPrice;\r\n\r\n await bus.Send(new OrderCreatedEvent(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems,\r\n });\r\n }\r\n\r\n public async Task Handle(StockReservedEvent message)\r\n {\r\n await bus.Send(new PaymentStartedEvent(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems,\r\n TotalPrice = Data.TotalPrice\r\n });\r\n }\r\n\r\n public async Task Handle(StockNotReservedEvent message)\r\n {\r\n await bus.Send(new OrderFailedEvent(message.CorrelationId)\r\n {\r\n Message = message.Message,\r\n OrderId = Data.OrderId\r\n });\r\n }\r\n\r\n public async Task Handle(PaymentCompletedEvent message)\r\n {\r\n await bus.Send(new OrderCompletedEvent()\r\n {\r\n OrderId = Data.OrderId\r\n });\r\n\r\n MarkAsComplete();\r\n }\r\n\r\n public async Task Handle(PaymentFailedEvent message)\r\n {\r\n await bus.Send(new OrderFailedEvent(message.CorrelationId)\r\n {\r\n OrderId = Data.OrderId,\r\n Message = message.Messages\r\n });\r\n\r\n await bus.Send(new StockRollbackMessage(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems\r\n });\r\n }\r\n\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n .\r\n .\r\n .\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBu ad\u0131mda yap\u0131lan \u00e7al\u0131\u015fmalar\u0131 incelemeye \u00f6ncelikle inject edilen IBus<\/code> referans\u0131n\u0131 vurgulayarak ba\u015flayal\u0131m. Bizler Rebus ile mesaj g\u00f6nderim i\u015flemlerini bu referans arac\u0131l\u0131\u011f\u0131yla kolayl\u0131kla ger\u00e7ekle\u015ftirebiliyoruz.<\/p>\n 9<\/em><\/strong> ile 23.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda OrderStartedEvent<\/em>‘e kar\u015f\u0131n handle i\u015flemleri y\u00fcr\u00fct\u00fclmektedir. Bu event geldi\u011fi taktirde \u00f6ncelikle IsNew<\/code> property’si ile yeni bir saga yani sipari\u015f s\u00fcrecinin olup olmad\u0131\u011f\u0131 de\u011ferlendirilmekte ve e\u011fer ki bu sipari\u015f daha \u00f6nce i\u015flendiyse tekrar etmeye gerek g\u00f6r\u00fclmemektedir. Yok e\u011fer yeni sipari\u015f durumu s\u00f6z konusuysa o taktirde ‘OrderSagaData’ t\u00fcr\u00fcnden saga data’ya Data<\/code> property’si \u00fczerinden eri\u015filmekte ve ba\u015flat\u0131c\u0131 event’in de\u011ferleri i\u015flenmekte ve ard\u0131ndan OrderCreatedEvent<\/em> yay\u0131nlanmaktad\u0131r.<\/p>\n 25<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise StockReservedEvent<\/em>‘e kar\u015f\u0131l\u0131k PaymentStartedEvent<\/em>, 34<\/em><\/strong> ile 41.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda StockNotReservedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderFailedEvent<\/em>, 43<\/em><\/strong> ile 51.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda PaymentCompletedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderCompletedEvent<\/em> ve son olarak da 53<\/em><\/strong> ile 65.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise PaymentFailedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderFailedEvent<\/em> ile birlikte StockRollbackMessage<\/em> yay\u0131nlanmaktad\u0131r.<\/p>\n 43<\/em><\/strong> ile 51.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131na tekrar gelirsek e\u011fer burada MarkAsComplete<\/code> metodunun \u00e7a\u011fr\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6rmekteyiz. Bu metot 6. ad\u0131mda OrderCompletedEvent<\/em>‘i olu\u015ftururken bahsetti\u011fim finalize i\u015flemini ger\u00e7ekle\u015ftirmektedir. Yani, ilgili handle metodunda OrderCompletedEvent<\/em> yay\u0131nland\u0131\u011f\u0131ndan dolay\u0131 art\u0131k sipari\u015fin ba\u015far\u0131l\u0131 oldu\u011fu kabul edilmekte ve b\u00f6ylece i\u015f ak\u0131\u015f\u0131n\u0131n tamamland\u0131\u011f\u0131 ifade edilmektedir. Dolay\u0131s\u0131yla MarkAsComplete<\/code> metodu \u00e7a\u011fr\u0131lmakta ve Saga.Orchestration.Service<\/code>‘in veritaban\u0131nda sipari\u015fe dair olu\u015fturulmu\u015f olan saga data sat\u0131r\u0131 kald\u0131r\u0131lmaktad\u0131r.\n<\/li>\n Ad\u0131m 10<\/em><\/strong> Shared – (Queue’lar\u0131n ve AMQP Url’in Yap\u0131land\u0131r\u0131lmas\u0131)<\/span> \n\u015eimdi de t\u00fcm servislerin ileti\u015fim s\u00fcre\u00e7lerinde handle edecekleri mesajlar\u0131 hangi queue’lardan alacaklar\u0131n\u0131 yap\u0131land\u0131ral\u0131m. Bunun i\u00e7in Shared<\/code> katman\u0131nda a\u015fa\u011f\u0131daki s\u0131n\u0131f\u0131 olu\u015fturabiliriz.<\/p>\n\n\r\n public static class RabbitMQQueueSettings\r\n {\r\n public const string OrderInputQueueName = "order-input-queue-name";\r\n public const string StockInputQueueName = "stock-input-queue-name";\r\n public const string PaymentInputQueueName = "payment-input-queue-name";\r\n public const string SagaOrchestrationInputQueueName = "saga-orchestration-input-queue-name";\r\n }\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Saga.Orchestration.Service<\/code>‘de dahil t\u00fcm servislerin queue isimlendirmesini RabbitMQQueueSettings<\/em> s\u0131n\u0131f\u0131nda ayarlam\u0131\u015f bulunuyoruz.<\/p>\n Queue isimlerinin yan\u0131nda ayr\u0131ca servisler aras\u0131 ileti\u015fim s\u00fcrecinde kullanaca\u011f\u0131m\u0131z RabbitMQ transporter’\u0131n\u0131n AMQP Url’ine t\u00fcm servislerin eri\u015febilece\u011fi \u015fekilde bir tan\u0131mlamada bulunmam\u0131z gerekmektedir. Evet, bu i\u015flem i\u00e7in her servisin appsettings.json dosyas\u0131ndan istifade edebiliriz ki do\u011frusu da budur. \u00c7\u00fcnk\u00fc production ortam\u0131nda bu tarz de\u011ferler elbet environment’tan yap\u0131land\u0131r\u0131lacakt\u0131r. Haliyle bunda mutab\u0131k\u0131z. Lakin bizler makalemizin hacmini \u015fi\u015firmemek i\u00e7in bu de\u011feri de yine Shared<\/code> katman\u0131nda olu\u015fturdu\u011fumuz a\u015fa\u011f\u0131daki RabbitMQAMQPUrl<\/em> s\u0131n\u0131f\u0131n da tutuyor olacak ve bu best practice’i bilin\u00e7li bir \u015fekilde g\u00f6z ard\u0131 ediyor olaca\u011f\u0131z.<\/p>\n \n\r\n public class RabbitMQAMQPUrl\r\n {\r\n public const string AMQPUrl = "amqps:\/\/irresudw:slx6TGLxuMAthCz4X61dYE6Crr-Vx7lx@chimpanzee.rmq.cloudamqp.com\/irresudw";\r\n }\r\n<\/pre>\n<\/div>\nEvet, art\u0131k bundan sonraki ad\u0131mlarda bu yap\u0131land\u0131rma de\u011ferlerini kullanarak servislerimizi konfig\u00fcre edebiliriz.\n<\/li>\n Ad\u0131m 11<\/em><\/strong> Saga.Orchestration.Service – (Program.cs Yap\u0131land\u0131rmas\u0131 ve Veritaban\u0131n\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u0130lk konfig\u00fcre edece\u011fimiz servis Saga.Orchestration.Service<\/code>‘dir. Bunun i\u00e7in ilgili servisin ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r =>\r\n r.TypeBased()\r\n .Map<OrderCreatedEvent>(RabbitMQQueueSettings.StockInputQueueName)\r\n .Map<PaymentStartedEvent>(RabbitMQQueueSettings.PaymentInputQueueName)\r\n .Map<OrderFailedEvent>(RabbitMQQueueSettings.OrderInputQueueName)\r\n .Map<OrderCompletedEvent>(RabbitMQQueueSettings.OrderInputQueueName)\r\n .Map<StockRollbackMessage>(RabbitMQQueueSettings.StockInputQueueName))\r\n .Transport(t =>\r\n t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl,\r\n inputQueueName: RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Sagas(s =>\r\n s.StoreInSqlServer("Server=localhost, 1433;Database=SagaOrchestrationRebusDB;User ID=SA;Password=1q2w3e4r+!;TrustServerCertificate=True",\r\n dataTableName: "Sagas",\r\n indexTableName: "SagaIndexes",\r\n automaticallyCreateTables: true))\r\n .Timeouts(t =>\r\n t.StoreInSqlServer("Server=localhost, 1433;Database=SagaOrchestrationRebusDB;User ID=SA;Password=1q2w3e4r+!;TrustServerCertificate=True",\r\n tableName: "Timeouts",\r\n automaticallyCreateTables: true)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n\r\nvar host = builder.Build();\r\nhost.Run();\r\n<\/pre>\n<\/div>\nYap\u0131lan \u00e7al\u0131\u015fmay\u0131 incelersek e\u011fer; 3.<\/em><\/strong> sat\u0131rda AddRebus<\/code> fonksiyonunu kullanarak Rebus servisini uygulamaya dahil ediyoruz. 4<\/em><\/strong> ile 10.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda Routing<\/code> metodu ile t\u00fcr\u00fcne g\u00f6re mesajlar\u0131n hangi kuyruklara y\u00f6nlendirilece\u011fini belirliyoruz. Burada TypeBased<\/code> metodu ile y\u00f6nlendirme stratejisi olarak mesaj t\u00fcr\u00fcne dayal\u0131 bir davran\u0131\u015f\u0131 belirleyece\u011fimizi ifade etmi\u015f oluyoruz. Ayr\u0131ca Map<\/code> fonksiyonu ile de belirtilen mesaj t\u00fcr\u00fcn\u00fc \u00f6nceden ayarlad\u0131\u011f\u0131m\u0131z kuyruk ad\u0131yla e\u015fle\u015ftiriyoruz ki b\u00f6ylece bu servis taraf\u0131ndan, o t\u00fcrden mesaj\u0131n hangi kuyruktan gelece\u011fini ve t\u00fcketebilece\u011fini yap\u0131land\u0131rm\u0131\u015f oluyoruz. Tabi burada t\u00fcm mesaj t\u00fcrlerine g\u00f6re ayr\u0131 ayr\u0131 yap\u0131land\u0131rma da bulunmaktansa MapAssemblyOf<\/code> metoduyla da a\u015fa\u011f\u0131daki gibi t\u00fcm t\u00fcrlere kar\u015f\u0131n assembly bazl\u0131 k\u00fcm\u00fclatif bir tan\u0131mda bulunabilirdik.<\/p>\n \n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r =>\r\n r.TypeBased()\r\n .MapAssemblyOf<BaseCorrelation>("..queue-name..")\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\nVelhas\u0131l, 11.<\/em><\/strong> sat\u0131rdaki Transport<\/code> metodu ile de bu servisin kullanaca\u011f\u0131 transporter’\u0131 belirtiyor ve 12.<\/em><\/strong> sat\u0131rda UseRabbitMq<\/code> metodu ile RabbitMQ’ya g\u00f6re gerekli yap\u0131land\u0131rmay\u0131 sa\u011fl\u0131yoruz. Ayr\u0131ca bu servisin mesaj g\u00f6nderirken hangi kuyru\u011fa g\u00f6nderece\u011fini de inputQueueName<\/code> parametresine verilen queue de\u011feriyle belirtiyoruz. Yani Saga.Orchestration.Service<\/code> bir message’\u0131 send ya da publish etti\u011finde bu, burada belirtilen kuyru\u011fa g\u00f6nderilmi\u015f olacakt\u0131r.<\/p>\n 14.<\/em><\/strong> sat\u0131rda Sagas<\/code> metodu ile de Rebus k\u00fct\u00fcphanesinin servisler aras\u0131ndaki ileti\u015fim s\u00fcrecinde i\u015f ak\u0131\u015f\u0131n\u0131n durumunu nerede saklayaca\u011f\u0131n\u0131 belirtiyoruz.<\/p>\n Ve son olarak 19.<\/em><\/strong> sat\u0131rda \u00e7a\u011f\u0131rd\u0131\u011f\u0131m\u0131z Timeouts<\/code> metodu ile de Rebus’\u0131n timeout s\u00fcre\u00e7lerine dair kay\u0131tlar\u0131n nerede tutulaca\u011f\u0131n\u0131 yap\u0131land\u0131r\u0131yoruz.<\/p>\n Burada Sagas<\/code> ve Timeouts<\/code> i\u015flemleri i\u00e7in gerekli olan veritaban\u0131 yap\u0131lar\u0131 automaticallyCreateTables<\/code> parametresi sayesinde servis aya\u011fa kald\u0131r\u0131ld\u0131\u011f\u0131 an otomatik olarak olu\u015fturulacakt\u0131r. Tabi veritaban\u0131n\u0131 bizlerin olu\u015fturmas\u0131 gerekmektedir. Kaynaktaki connection string de\u011ferine bakarsan\u0131z veritaban\u0131 ismine SagaOrchestrationRebusDB<\/code> verdi\u011fimizi g\u00f6r\u00fcrs\u00fcn\u00fcz. Haliyle \u015fimdi bu isimde bir veritaban\u0131n\u0131 olu\u015ftural\u0131m ve ard\u0131ndan servisimizi aya\u011fa kald\u0131r\u0131p gerekli tablo yap\u0131lanmas\u0131n\u0131 generate ettirelim.<\/p>\n \n\r\nCREATE DATABASE SagaOrchestrationRebusDB\r\n<\/pre>\n<\/div>\n<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere olu\u015fturdu\u011fumuz veritaban\u0131 i\u00e7erisine ilgili tablo yap\u0131s\u0131 olu\u015fturulmu\u015ftur. \u015eimdi olu\u015fturulan bu tablolar\u0131 inceleyelim.<\/p>\n\n\n\n\n\n\nTablolar<\/th>\n<\/tr>\n Sagas<\/th>\n SagaIndexes<\/th>\n Timeouts<\/th>\n<\/tr>\n<\/thead>\n Distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecindeki state’i saklamak ve takip etmek i\u00e7in kullan\u0131lan tablodur.<\/a>Burada i\u015f ak\u0131\u015f\u0131ndaki her bir state’i bir versiyon numaras\u0131yla temsil edece\u011fi revision<\/code> kolonunda tutmaktad\u0131r. Her bir state de\u011fi\u015fikli\u011fi bu kolonun de\u011ferini +1 art\u0131racakt\u0131r. B\u00f6ylece biz ilgili olguya dair i\u015f ak\u0131\u015f\u0131nda state’in ka\u00e7 kez de\u011fi\u015fti\u011fini \u00f6\u011frenebilmekteyiz.<\/p>\ndata<\/code> kolonunda ise her bir duruma kar\u015f\u0131n kullan\u0131lan OrderSagaData<\/em> t\u00fcr\u00fcnden saga data verisi binary format\u0131nda tutulmaktad\u0131r.\n<\/td>\n Sagas tablosuyla ili\u015fkilendirilmi\u015f olan bu SagaIndexes tablosu i\u015f ak\u0131\u015f\u0131 state’ini belirleyen index bilgilerini i\u00e7ermektedir.<\/a>saga_type<\/code> kolonunda state’i takip edilen saga data’n\u0131n t\u00fcr\u00fc, key<\/code> kolonunda korelasyon de\u011ferini ifade eden property ad\u0131 ve value<\/code> kolonunda ise i\u015f ak\u0131\u015f\u0131ndaki b\u00fct\u00fcnselli\u011fi sa\u011flayacak olan korelasyonel de\u011fer tutulmaktad\u0131r. <\/p>\n<\/td>\n Timeout s\u00fcre\u00e7lerini y\u00f6netmek i\u00e7in kullan\u0131lan tablodur. Bu tablo sayesinde, Rebus ile yap\u0131lan i\u015flemlerin yahut olaylar\u0131n belirli bir s\u00fcre i\u00e7erisinde tamamlanmas\u0131n\u0131 bekledi\u011fi durumlar\u0131 takip edebiliriz.<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\nAd\u0131m 12<\/em><\/strong> Order.API – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nS\u0131radaki konfig\u00fcre edece\u011fimiz servisimiz Order.API<\/code> olacakt\u0131r. Bunun i\u00e7in ilgili servisin ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.OrderInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Order.API<\/code>‘a t\u00fcm mesajlar\u0131n Saga.Orchestration.Service<\/code>‘in mesaj g\u00f6nderece\u011fi kuyruktan yani k\u0131saca Saga.Orchestration.Service<\/code>‘ten gelece\u011fini bildirmi\u015f bulunmaktay\u0131z. \u00c7\u00fcnk\u00fc Order.API<\/code> ve di\u011fer t\u00fcm servisler sade ve sadece Saga.Orchestration.Service<\/code>‘ten mesaj alacak ya da ona mesaj g\u00f6nderecektir. Ayr\u0131ca bu servisin g\u00f6nderece\u011fi mesajlar\u0131 da, inputQueueName<\/code> parametresine bakarsak RabbitMQQueueSettings.OrderInputQueueName<\/code> de\u011ferine kar\u015f\u0131l\u0131k gelen kuyru\u011fa g\u00f6nderece\u011fini ifade etmi\u015f bulunmaktay\u0131z. Haliyle buradaki yap\u0131land\u0131rma mant\u0131\u011f\u0131n\u0131 di\u011fer servislerde de birebir g\u00f6r\u00fcyor olaca\u011f\u0131z.<\/p>\n AutoRegisterHandlersFromAssemblyOf<\/code> metodu ise sonraki ad\u0131mlarda olu\u015fturaca\u011f\u0131m\u0131z handler s\u0131n\u0131flar\u0131n\u0131n assembly seviyesinde otomatik olarak yakalay\u0131p, register edilmesini sa\u011flamaktad\u0131r. Ha tabi, her ne kadar bu senaryoda Order.API<\/code>‘da bir handler s\u0131n\u0131f\u0131 olu\u015fturmayacak olsak da Rebus ile yap\u0131lan \u00e7al\u0131\u015fmalarda handler yap\u0131lanmalar\u0131n\u0131n aktivite edilmesi i\u00e7in bu metodun \u00e7a\u011fr\u0131lmas\u0131 elzemdir ve sonraki s\u00fcre\u00e7lerde olu\u015fturma ihtimaline nazaran uygulama seviyesinde \u00f6nceden \u00e7a\u011fr\u0131l\u0131p haz\u0131r bir \u015fekilde tutulmas\u0131 k\u00e2fidir.\n<\/li>\nAd\u0131m 13<\/em><\/strong> Order.API – (Sipari\u015f Olu\u015fturma S\u00fcrecinde OrderStartedEvent’in Yay\u0131nlanmas\u0131)<\/span> \n\u015eimdi de 2. ad\u0131mda Order.API<\/code>‘da geli\u015ftirdi\u011fimiz \/create-order<\/code> minimal api’sinde a\u015fa\u011f\u0131daki gibi OrderStartedEvent<\/em>‘i yay\u0131nlayal\u0131m ve distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecini ba\u015flatal\u0131m.<\/p>\n\n\r\n.\r\n.\r\n.\r\n\r\napp.MapPost("\/create-order", async (IBus bus, ApplicationDbContext context, CreateOrderVM model) =>\r\n{\r\n .\r\n .\r\n .\r\n\r\n OrderStartedEvent orderStartedEvent = new()\r\n {\r\n OrderId = order.Id,\r\n BuyerId = model.BuyerId,\r\n TotalPrice = order.TotalPrice,\r\n OrderItems = model.OrderItems.Select(oi => new Shared.Datas.OrderItem\r\n {\r\n Count = oi.Count,\r\n Price = oi.Price,\r\n ProductId = oi.ProductId\r\n }).ToList(),\r\n CorrelationId = Guid.NewGuid(),\r\n };\r\n\r\n await bus.Send(orderStartedEvent);\r\n\r\n return Results.Created();\r\n});\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 14<\/em><\/strong> Stock.Service – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nStock.Service<\/code>‘de de \u00f6nceki ad\u0131mlarda anlat\u0131lan mant\u0131kta yap\u0131land\u0131rmay\u0131 a\u015fa\u011f\u0131daki gibi sa\u011flayal\u0131m.<\/p>\n\n\r\n.\r\n.\r\n.\r\n\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.StockInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 15<\/em><\/strong> Stock.Service – (OrderCreatedEventHandler ve StockRollbackMessageHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nStock.Service<\/code>‘i yap\u0131land\u0131rd\u0131ktan sonra gerekli handler s\u0131n\u0131flar\u0131n\u0131 a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderCreatedEventHandler(MongoDBService mongoDBService, IBus bus) : IHandleMessages<OrderCreatedEvent>\r\n {\r\n public async Task Handle(OrderCreatedEvent message)\r\n {\r\n List<bool> stockResults = new();\r\n var stockCollection = mongoDBService.GetCollection<Models.Stock>();\r\n\r\n foreach (var orderItem in message.OrderItems)\r\n stockResults.Add(await (await stockCollection.FindAsync(s => s.ProductId == orderItem.ProductId && s.Count >=\r\n(long)orderItem.Count)).AnyAsync());\r\n\r\n if (stockResults.TrueForAll(s => s.Equals(true)))\r\n {\r\n foreach (var orderItem in message.OrderItems)\r\n {\r\n var stock = await (await stockCollection.FindAsync(s => s.ProductId == orderItem.ProductId)).FirstOrDefaultAsync();\r\n\r\n stock.Count -= orderItem.Count;\r\n\r\n await stockCollection.FindOneAndReplaceAsync(x => x.ProductId == orderItem.ProductId, stock);\r\n }\r\n\r\n StockReservedEvent stockReservedEvent = new(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems\r\n };\r\n\r\n await bus.Send(stockReservedEvent);\r\n }\r\n else\r\n {\r\n StockNotReservedEvent stockNotReservedEvent = new(message.CorrelationId)\r\n {\r\n Message = "Stok yetersiz...."\r\n };\r\n\r\n await bus.Send(stockNotReservedEvent);\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class StockRollbackMessageHandler(MongoDBService mongoDBService) : IHandleMessages<StockRollbackMessage>\r\n {\r\n public async Task Handle(StockRollbackMessage message)\r\n {\r\n var stockCollection = mongoDBService.GetCollection<Models.Stock>();\r\n\r\n foreach (var orderItem in message.OrderItems)\r\n {\r\n var stock = await (await stockCollection.FindAsync(x => x.ProductId == orderItem.ProductId)).FirstOrDefaultAsync();\r\n\r\n stock.Count += orderItem.Count;\r\n await stockCollection.FindOneAndReplaceAsync(x => x.ProductId == orderItem.ProductId, stock);\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131daki kodlar\u0131 incelerseniz e\u011fer gerekli stok i\u015flemleri ger\u00e7ekle\u015ftirilmekte yahut compensable transaction operasyonu y\u00fcr\u00fct\u00fclmektedir.\n<\/li>\n Ad\u0131m 16<\/em><\/strong> Payment.Service – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nAyn\u0131 mant\u0131kta Payment.Service<\/code>‘de de ‘Program.cs’ yap\u0131land\u0131rmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.PaymentInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 17<\/em><\/strong> Payment.Service – (PaymentStartedEventHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nVe \u00f6demeyle ilgili i\u015flemleri ba\u015flatacak olan PaymentStartedEvent<\/em>‘e kar\u015f\u0131n PaymentStartedEventHandler<\/em>‘\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\n public class PaymentStartedEventHandler(IBus bus) : IHandleMessages<PaymentStartedEvent>\r\n {\r\n public async Task Handle(PaymentStartedEvent message)\r\n {\r\n \/\/\u00d6deme ba\u015far\u0131l\u0131...\r\n await bus.Send(new PaymentCompletedEvent(message.CorrelationId));\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada farazi bir \u00f6deme i\u015fleminin yap\u0131ld\u0131\u011f\u0131n\u0131 varsayarak yolumuza devam edelim.\n<\/li>\n Ad\u0131m 19<\/em><\/strong> Order.Saga – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nVe son olarak Order.Saga<\/code> servisinde de ‘Program.cs’ yap\u0131land\u0131rmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.OrderInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 18<\/em><\/strong> Order.Saga – (OrderCompletedEventHandler ve OrderFailedEventHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nVe ard\u0131ndan sipari\u015fin nihai durumunu belirleyecek olan handler’lar\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderCompletedEventHandler(ApplicationDbContext applicationDbContext) : IHandleMessages<OrderCompletedEvent>\r\n {\r\n public async Task Handle(OrderCompletedEvent message)\r\n {\r\n Order.Saga.Models.Entities.Order order = await applicationDbContext.Orders.FindAsync(message.OrderId);\r\n if (order != null)\r\n {\r\n order.OrderStatus = Models.Enums.OrderStatus.Completed;\r\n await applicationDbContext.SaveChangesAsync();\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class OrderFailedEventHandler(ApplicationDbContext applicationDbContext) : IHandleMessages<OrderFailedEvent>\r\n {\r\n public async Task Handle(OrderFailedEvent message)\r\n {\r\n Order.Saga.Models.Entities.Order order = await applicationDbContext.Orders.FindAsync(message.OrderId);\r\n if (order != null)\r\n {\r\n order.OrderStatus = Order.Saga.Models.Enums.OrderStatus.Fail;\r\n await applicationDbContext.SaveChangesAsync();\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada dikkat edilmesi gereken nokta \u015fudur ki, Order.Saga<\/code> servisinde yap\u0131lan veritaban\u0131 \u00e7al\u0131\u015fmalar\u0131nda Order.API<\/code>‘dakine benzer context ve entity yap\u0131s\u0131 in\u015fa edilmi\u015f ve IoC Container’a provide edilmi\u015ftir. Tabi tekrara girmemek ve i\u00e7eri\u011fi haddinden fazla uzatmamak i\u00e7in bu k\u0131s\u0131mlar es ge\u00e7ilmi\u015ftir. Yap\u0131lan \u00e7al\u0131\u015fmalar\u0131n tam teferruatl\u0131 i\u00e7eri\u011fine makalenin sonunda payla\u015f\u0131lan github linki \u00fczerinden g\u00f6zlemde bulunabilirsiniz.\n<\/li>\n Ad\u0131m 19<\/em><\/strong> Test<\/span> \nArt\u0131k yap\u0131lan bunca \u00e7al\u0131\u015fman\u0131n testini ger\u00e7ekle\u015ftirebiliriz. Bunun i\u00e7in servislerimizi derleyip aya\u011fa kald\u0131ral\u0131m ve a\u015fa\u011f\u0131daki json data e\u015fli\u011finde bir sipari\u015f talebinde bulunal\u0131m.<\/p>\n\n\r\n{\r\n "buyerId": 1,\r\n "orderItems": [\r\n {\r\n "productId": 1,\r\n "count": 10,\r\n "price": 5\r\n },\r\n {\r\n "productId": 2,\r\n "count": 30,\r\n "price": 50\r\n },\r\n {\r\n "productId": 3,\r\n "count": 5,\r\n "price": 5\r\n }\r\n ]\r\n}\r\n<\/pre>\n<\/div>\n<\/a>Bu i\u015flem neticesinde s\u00fcrecin a\u015fa\u011f\u0131daki g\u00f6rseldeki gibi oldu\u011funu g\u00f6rece\u011fiz.<\/a>Ayr\u0131ca yeri gelmi\u015fken bahsetmekte fayda g\u00f6rmekteyim ki, distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecinde Sagas tablosunun ‘data’ kolonundaki binary veriyi a\u015fa\u011f\u0131daki sorguyla metinsele d\u00f6n\u00fc\u015ft\u00fcrebilir ve i\u00e7eri\u011fine dair g\u00f6zlemde bulunabilirsiniz.<\/p>\n \n\r\nSELECT CONVERT(VARCHAR(MAX), data)\r\nFROM SagaOrchestrationRebusDB.dbo.Sagas\r\n<\/pre>\n<\/div>\n\n{“$type”:”Saga.Orchestration.Service.SagaDatas.OrderSagaData, Saga.Orchestration.Service”,”Id”:”7e630713-c610-4c9b-8a38-03f61f3060a8″,”Revision”:1,”OrderId”:5,”BuyerId”:1,”TotalPrice”:1825.0,”OrderItems”:{“$type”:”System.Collections.Generic.List`1[[Shared.Datas.OrderItem, Shared]], System.Private.CoreLib”,”$values”:[{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:1,”Count”:10,”Price”:5.0},{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:2,”Count”:30,”Price”:50.0},{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:4,”Count”:55,”Price”:5.0}]},”CorrelationId”:”c5d0b313-2bf4-4081-935f-72fa0c9895f0″}\n<\/div>\n<\/li>\n<\/ul>\n\u0130\u015fte bu kadar \ud83d\ude42<\/p>\n Nihai olarak; \nSaga Orchestration implementasyonunu Rebus k\u00fct\u00fcphanesiyle, test ad\u0131m\u0131 da dahil olmak \u00fczere 19 ad\u0131mda uygulam\u0131\u015f ve MassTransit’e nazaran konuya dair alternatif bir yakla\u015f\u0131m\u0131 tecr\u00fcbe etmi\u015f bulunmaktay\u0131z. Nacizane fikrim, Rebus k\u00fct\u00fcphanesi MassTransit’e kar\u015f\u0131n yap\u0131land\u0131rma a\u00e7\u0131s\u0131ndan d\u00fc\u015f\u00fck bir komplikasyona sahip olsa da onun kadar geni\u015f bir yelpazede entegrasyon imkan\u0131 sa\u011flamamakta ve k\u00fc\u00e7\u00fck yahut orta \u00f6l\u00e7ekli uygulamalarda daha pratik \u00e7\u00f6z\u00fcmler sunmaktad\u0131r.<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\nNot : \u00d6rnek \u00e7al\u0131\u015fmaya a\u015fa\u011f\u0131daki github adresinden eri\u015febilirsiniz. \nhttps:\/\/github.com\/gncyyldz\/Saga.Orchestration.Example.With.Rebus<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Malumunuz, microservice mimarisiyle tasarlanm\u0131\u015f yaz\u0131l\u0131mlar\u0131m\u0131zda kullan\u0131c\u0131lar taraf\u0131ndan ba\u015flat\u0131lan i\u015flem ya da g\u00f6revlerin, bir servis taraf\u0131ndan al\u0131n\u0131p ard\u0131ndan belirli servisler \u00fczerinde mant\u0131ksal bir tetikleme silsilesiyle i\u015flenme ve koordine edilme s\u00fcre\u00e7lerini y\u00fcr\u00fctmemize ve biryandan da...<\/p>\n","protected":false},"author":1,"featured_media":26849,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4912,2739,3573],"tags":[3575,4994,4996,4995,4993,4372],"class_list":["post-26819","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-net-8","category-net-core","category-microservices","tag-microservice","tag-rebus","tag-rebus-microservice","tag-rebus-saga","tag-rebus-saga-orchestration","tag-saga-orchestration"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819","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=26819"}],"version-history":[{"count":20,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819\/revisions"}],"predecessor-version":[{"id":26850,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819\/revisions\/26850"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/26849"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

\nRebus.ServiceProvider<\/a>
\n Rebus.RabbitMq<\/a>
\n Rebus.SqlServer<\/a>\n<\/div>\n

Kazmay\u0131 Vural\u0131m<\/h5>\n
Projelere ilgili k\u00fct\u00fcphaneleri y\u00fckledi\u011fimize g\u00f6re art\u0131k genel senaryonun in\u015fas\u0131na ba\u015flayabiliriz. Bunun i\u00e7in a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 s\u0131ras\u0131yla seyretmemiz yeterli olacakt\u0131r kanaatindeyim…<\/p>\n
\n
Ad\u0131m 1<\/em><\/strong> Order.API – (Order Entity’sinin Olu\u015fturulmas\u0131, Veritaban\u0131 Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131 ve Migration \u0130\u015flemleri)<\/span>
\n\u0130lk olarak kullan\u0131c\u0131 taraf\u0131ndan verilecek olan sipari\u015fin `Order.API<\/code> taraf\u0131nda altyap\u0131s\u0131n\u0131 kurgulamam\u0131z gerekmektedir. Bunun i\u00e7in a\u015fa\u011f\u0131daki ‘Order’ entity’sinden istifade edebiliriz.<\/p>\n`\n\r\n public class Order\r\n {\r\n public int Id { get; set; }\r\n public int BuyerId { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n public OrderStatus OrderStatus { get; set; }\r\n public DateTime CreatedDate { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nTabi bu entity i\u00e7erisindeki ‘OrderItem’ ve ‘OrderStatus’ t\u00fcrleri de a\u015fa\u011f\u0131daki gibi olacakt\u0131r.<\/p>\n\n\r\n public class OrderItem\r\n {\r\n public int Id { get; set; }\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public enum OrderStatus\r\n {\r\n Suspend,\r\n Completed,\r\n Fail\r\n }\r\n<\/pre>\n<\/div>\nSipari\u015f entity’sini olu\u015fturdu\u011fumuza g\u00f6re \u015fimdi s\u0131rada DbContext nesnesini olu\u015fturmam\u0131z gerekmektedir.<\/p>\n \n\r\n public class ApplicationDbContext : DbContext\r\n {\r\n public ApplicationDbContext(DbContextOptions options) : base(options)\r\n {\r\n }\r\n\r\n public DbSet<Order.API.Models.Entities.Order> Orders { get; set; }\r\n public DbSet<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nArd\u0131ndan olu\u015fturulan bu yap\u0131y\u0131 uygulaman\u0131n ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rmam\u0131z gerekmektedir.<\/p>\n \n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddDbContext<ApplicationDbContext>(options =>\r\n options.UseSqlServer(builder.Configuration.GetConnectionString("SQLServer")));\r\n\r\nvar app = builder.Build();\r\n.\r\n.\r\n.\r\napp.Run();\r\n<\/pre>\n<\/div>\nVe son olarak da add-migration mig_1<\/code> talimat\u0131yla migration basal\u0131m ve \nupdate-database<\/code> talimat\u0131yla da migrate ederek veritaban\u0131n\u0131 sunucuda olu\u015ftural\u0131m.<\/a>(Not: Bu ad\u0131m\u0131 uygularken s\u00fcre\u00e7te ihtiya\u00e7 olabilecek baz\u0131 k\u00fct\u00fcphanelerin y\u00fcklendi\u011fi varsay\u0131lm\u0131\u015ft\u0131r. Bu k\u00fct\u00fcphaneler; EF Core i\u00e7in Microsoft.EntityFrameworkCore<\/a>, EF Core’da SQL Server’\u0131n kullan\u0131labilmesi i\u00e7in Microsoft.EntityFrameworkCore.SqlServer<\/a> ve package manager console \u00fczerinden migration i\u015flemlerinin y\u00fcr\u00fct\u00fclebilmesi i\u00e7in Microsoft.EntityFrameworkCore.Tools<\/a> k\u00fct\u00fcphaneleridir.)<\/span>\n<\/li>\n Ad\u0131m 2<\/em><\/strong> Order.API – (Sipari\u015fin Olu\u015fturulmas\u0131)<\/span> \nKullan\u0131c\u0131dan gelecek olan sipari\u015f i\u00e7in temel altyap\u0131y\u0131 kurgulad\u0131\u011f\u0131m\u0131za g\u00f6re art\u0131k sipari\u015fin olu\u015fturulmas\u0131na odaklanabiliriz. Bunun i\u00e7in \u00f6ncelikle kullan\u0131c\u0131dan sipari\u015fin bilgilerini alabilece\u011fimiz a\u015fa\u011f\u0131daki viewmodel nesnelerini olu\u015ftural\u0131m.<\/p>\n\n\r\n public class CreateOrderVM\r\n {\r\n public int BuyerId { get; set; }\r\n public List<CreateOrderItemVM> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class CreateOrderItemVM\r\n {\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nArd\u0131ndan sipari\u015fin olu\u015fturulmas\u0131n\u0131 sa\u011flayacak olan endpoint’i a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n.\r\n.\r\n.\r\nvar app = builder.Build();\r\n.\r\n.\r\n.\r\napp.MapPost("\/create-order", async (ApplicationDbContext context, CreateOrderVM model) =>\r\n{\r\n Order.API.Models.Entities.Order order = new()\r\n {\r\n BuyerId = model.BuyerId,\r\n OrderItems = model.OrderItems.Select(oi => new OrderItem\r\n {\r\n Count = oi.Count,\r\n Price = oi.Price,\r\n ProductId = oi.ProductId\r\n }).ToList(),\r\n OrderStatus = OrderStatus.Suspend,\r\n TotalPrice = model.OrderItems.Sum(oi => oi.Count * oi.Price),\r\n CreatedDate = DateTime.Now\r\n };\r\n\r\n await context.Orders.AddAsync(order);\r\n await context.SaveChangesAsync();\r\n return Results.Created();\r\n});\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere sipari\u015fe dair distributed s\u00fcrecin tamamlanmas\u0131n\u0131 bekleyece\u011fimizden dolay\u0131 ilk etapta Suspend<\/em> olarak olu\u015fturmaktay\u0131z.\n<\/li>\nAd\u0131m 3<\/em><\/strong> Stock.Service – (MongoDB Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131 ve \u00dcr\u00fcn Stok Bilgilerine Dair Dummy Datalar\u0131n Eklenmesi)<\/span> \nGelecek olan sipari\u015fin stok i\u015flemlerine dair de Stock.Service<\/code>‘de bir altyap\u0131 olu\u015fturmam\u0131z gerekmektedir. Bu altyap\u0131 i\u00e7eri\u011fi zenginle\u015ftirmek maksad\u0131yla MongoDB \u00fczerine kurgulanm\u0131\u015f olacakt\u0131r. Bunun i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki ‘MongoDBService’i olu\u015ftural\u0131m.<\/p>\n\n\r\n public class MongoDBService\r\n {\r\n readonly IMongoDatabase _database;\r\n readonly IConfiguration _configuration;\r\n public MongoDBService(IConfiguration configuration)\r\n {\r\n _configuration = configuration;\r\n MongoClient client = new(_configuration["MongoDB:Server"]);\r\n _database = client.GetDatabase(_configuration["MongoDB:DatabaseName"]);\r\n }\r\n public IMongoCollection<T> GetCollection<T>() => _database.GetCollection<T>(typeof(T).Name.ToLowerInvariant());\r\n }\r\n<\/pre>\n<\/div>\nTabi bu servisi olu\u015fturabilmek i\u00e7in MongoDB.Driver<\/a> k\u00fct\u00fcphanesinin ilgili servise y\u00fcklenmesi gerekmektedir.<\/p>\n Ba\u011flant\u0131 sa\u011flayaca\u011f\u0131m\u0131z MongoDB sunucusu bilgilerini de a\u015fa\u011f\u0131daki gibi appsettings.json dosyas\u0131na kaydedelim.<\/p>\n \n\r\n "MongoDB": {\r\n "Server": "mongodb:\/\/localhost:27017",\r\n "DatabaseName": "SagaOrchestrationRebusDB"\r\n }\r\n<\/pre>\n<\/div>\nVe ard\u0131ndan ilgili servisi, projenin ‘Program.cs’ dosyas\u0131 \u00fczerinden a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rarak uygulaman\u0131n IoC Container’\u0131na ekleyelim.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddSingleton<MongoDBService>();\r\n\r\nvar host = builder.Build();\r\n.\r\n.\r\n.\r\nhost.Run();\r\n<\/pre>\n<\/div>\nDevam\u0131nda ise MongoDB veritaban\u0131nda stok bilgilerini tutacak a\u015fa\u011f\u0131daki entity’i olu\u015ftural\u0131m.<\/p>\n\n\r\n public class Stock\r\n {\r\n [BsonRepresentation(BsonType.ObjectId)]\r\n [BsonId]\r\n [BsonElement(Order = 0)]\r\n public ObjectId Id { get; set; }\r\n [BsonRepresentation(BsonType.Int64)]\r\n [BsonElement(Order = 1)]\r\n public int ProductId { get; set; }\r\n [BsonRepresentation(BsonType.Int64)]\r\n [BsonElement(Order = 2)]\r\n public int Count { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nVe bu entity e\u015fli\u011finde yukar\u0131da yap\u0131land\u0131rd\u0131\u011f\u0131m\u0131z servis sayesinde \u00fcr\u00fcnlerin stok bilgilerini bar\u0131nd\u0131ran dummy datalar\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n.\r\n.\r\n.\r\nbuilder.Services.AddSingleton<MongoDBService>();\r\n\r\nvar host = builder.Build();\r\n\r\nusing var scope = builder.Services.BuildServiceProvider().CreateScope();\r\nvar mongoDbService = scope.ServiceProvider.GetRequiredService<MongoDBService>();\r\nif (!await (await mongoDbService.GetCollection<Stock.Service.Models.Stock>().FindAsync(x => true)).AnyAsync())\r\n{\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 1,\r\n Count = 200\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 2,\r\n Count = 300\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 3,\r\n Count = 50\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 4,\r\n Count = 10\r\n });\r\n mongoDbService.GetCollection<Stock.Service.Models.Stock>().InsertOne(new()\r\n {\r\n ProductId = 5,\r\n Count = 60\r\n });\r\n}\r\n\r\nhost.Run();\r\n<\/pre>\n<\/div>\nArt\u0131k bu \u00e7al\u0131\u015fmalar e\u015fli\u011finde Stock.Service<\/code>‘in bir kere aya\u011fa kald\u0131r\u0131lmas\u0131 hem veritaban\u0131n\u0131n hem de dummy datalar\u0131n olu\u015fturulmas\u0131 a\u00e7\u0131s\u0131ndan yeterli olacakt\u0131r.<\/a>\n<\/li>\n Ad\u0131m 4<\/em><\/strong> Shared – (BaseCorrelation S\u0131n\u0131f\u0131n\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u0130\u00e7eri\u011fimizin sonraki ad\u0131mlar\u0131nda Rebus ile Saga Orchestration davran\u0131\u015f\u0131n\u0131 uygularken geli\u015ftirece\u011fimiz merkezi Saga yap\u0131lanmas\u0131nda, servislerden gelecek olan mesajlar\u0131 e\u015fle\u015ftirmemizi ve bu mesajlar\u0131n ayn\u0131 i\u015f ak\u0131\u015f\u0131 i\u00e7erisinde belirli bir sipari\u015fe kar\u015f\u0131l\u0131k ili\u015fkilendirmemizi sa\u011flayacak olan korelasyon yap\u0131s\u0131n\u0131 olu\u015fturmam\u0131z gerekmektedir. Bu yap\u0131, herhangi bir de\u011fer olabilir. Usul gere\u011fi m\u00fcmk\u00fcn mertebe unique olmas\u0131na \u00f6zen g\u00f6sterilmesi gerekece\u011finden dolay\u0131 biz bu ihtiyaca istinaden ‘BaseCorrelation’ s\u0131n\u0131f\u0131 ile \u00e7\u00f6z\u00fcm getiriyor olaca\u011f\u0131z. Haliyle ilgili s\u0131n\u0131f\u0131n i\u00e7eri\u011fini Shared<\/code> class library’sinde a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m;<\/p>\n\n\r\n [Serializable]\r\n public class BaseCorrelation\r\n {\r\n public BaseCorrelation() { }\r\n public BaseCorrelation(Guid correlationId)\r\n {\r\n CorrelationId = correlationId;\r\n }\r\n [DataMember]\r\n public Guid CorrelationId { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere ‘BaseCorrelation’ s\u0131n\u0131f\u0131 i\u00e7erisinde ‘Guid’ t\u00fcr\u00fcnden bir de\u011fer al\u0131nmakta ve bu ‘CorrelationId’ property’sinde saklanmaktad\u0131r. B\u00f6ylece sistemde olu\u015fturulacak t\u00fcm message ve event yap\u0131lanmalar\u0131n\u0131 bu s\u0131n\u0131ftan t\u00fcreterek, ayn\u0131 i\u015f ak\u0131\u015f\u0131ndaki farkl\u0131 olaylar\u0131 ve mesajlar\u0131, ortak bir ba\u011flam bilgisi olmas\u0131 amac\u0131yla \u00fcretilmi\u015f olan korelasyon de\u011feri \u00fczerinden e\u015fle\u015ftirecek ve tek bir sipari\u015fe kar\u015f\u0131n olay zincirinin ba\u011f\u0131n\u0131 kurguluyor olaca\u011f\u0131z.\n<\/li>\nAd\u0131m 5<\/em><\/strong> Saga.Orchestration.Service – (Saga Orchestration Altyap\u0131s\u0131n\u0131n Kurgulanmas\u0131)<\/span> \nRebus k\u00fct\u00fcphanesiyle yap\u0131lan Orchestration operasyonunda t\u0131pk\u0131 MassTransit ile yapm\u0131\u015f oldu\u011fumuz \u00e7al\u0131\u015fmada oldu\u011fu gibi belli ba\u015fl\u0131 davran\u0131\u015flara sahip nesneler senaryoda sorumluluk \u00fcstlenmekte ve haliyle \u00f6ncelikle bu nesnelerin \u00fcretilmesi gerekmektedir. \u015eimdi gelin bu nesneleri tek tek izah ederek ilerleyelim;<\/p>\n\nSaga Data Nesnesi<\/u><\/em> \nOrchestration operasyonu s\u00fcrecinde distributed bir \u015fekilde takip edilen ak\u0131\u015f\u0131n veri format\u0131n\u0131 temsil eden bir nesnedir. Bizim \u00f6rnek senaryomuzda bu bir sipari\u015f modeline kar\u015f\u0131l\u0131k gelmekte ve bir sipari\u015fle ilgili servisler aras\u0131 ileti\u015fim s\u00fcrecindeki verilerin geli\u015fimini takip etmemizi sa\u011flayacak olan bilgileri bar\u0131nd\u0131racak olan bir nesneyi ifade etmektedir. B\u00f6ylece bizler saga data nesnesi sayesinde distributed ak\u0131\u015ftaki olgunun state’ini tutabilmekte ve y\u00f6netebilmekteyiz.<\/p>\nBir s\u0131n\u0131f\u0131n saga data s\u0131n\u0131f\u0131 olabilmesi i\u00e7in ISagaData<\/code> interface’inden implemente edilmesi gerekmektedir.<\/p>\n\n\r\n public class OrderSagaData : BaseCorrelation, ISagaData\r\n {\r\n public Guid Id { get; set; }\r\n public int Revision { get; set; }\r\n public int OrderId { get; set; }\r\n public int BuyerId { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131da g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bir sipari\u015f s\u00fcrecinin state’ini takip etmemizi sa\u011flayacak olan ‘OrderSagaData’ s\u0131n\u0131f\u0131n\u0131 olu\u015fturmu\u015f bulunuyoruz. Burada dikkatinizi bir \u00f6nceki ad\u0131mda olu\u015fturdu\u011fumuz ‘BaseCorrelation’ s\u0131n\u0131f\u0131na \u00e7ekmek isterim. Evet, olu\u015fturdu\u011fumuz bu saga data nesnesi her ne kadar sipari\u015f state’ini tutacak olsa da hangi sipari\u015fe dair state’i tuttu\u011funu anlayabilmek i\u00e7in bunu da ‘BaseCorrelation’dan t\u00fcretiyor ve bu s\u0131n\u0131ftaki korelasyon yap\u0131lanmas\u0131n\u0131 saga data nesnesine aktar\u0131yoruz.<\/p>\n Ayr\u0131ca yukar\u0131da kullan\u0131lan ‘OrderItem’ referans\u0131n\u0131 da Shared<\/code> i\u00e7erisinde a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderItem\r\n {\r\n public int ProductId { get; set; }\r\n public int Count { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n<\/li>\nSaga Nesnesi<\/u><\/em> \nOrchestration yakla\u015f\u0131m\u0131n\u0131 uygulamam\u0131z\u0131 sa\u011flayacak olan, bir i\u015fin-ak\u0131\u015f\u0131n yani \u00f6rnek senaryomuzdaki sipari\u015f s\u00fcrecinin temsil edilmesine ve servisler aras\u0131ndaki koordinasyonun merkezi bir \u015fekilde y\u00fcr\u00fct\u00fclmesine imkan tan\u0131yacak olan s\u0131n\u0131f\u0131n ta kendisidir.<\/p>\nBizler saga s\u0131n\u0131f\u0131 sayesinde servisler aras\u0131ndaki mesajla\u015fmalar\u0131 takip edebilmekte, durumlar\u0131 y\u00f6netebilmekte ve i\u015f s\u00fcrecine uygun bir \u015fekilde durumlar aras\u0131 ge\u00e7i\u015fler yapabilmekteyiz.<\/p>\n Bir s\u0131n\u0131f\u0131n saga s\u0131n\u0131f\u0131 olabilmesi i\u00e7in Saga<T><\/code> abstract class’\u0131n\u0131 implemente etmesi gerekmektedir. \u015e\u00f6yle ki;<\/p>\n \n\r\n public class OrderSaga : Saga<OrderSagaData>\r\n {\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n\r\n }\r\n }\r\n<\/pre>\n<\/div>\nEvet, yukar\u0131daki kod blo\u011funda g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bizler ‘OrderSaga’ ad\u0131nda bir saga nesnesi olu\u015fturmu\u015f bulunuyoruz. \u0130\u00e7erik s\u00fcrecinde bu nesnenin hacminin farkl\u0131 implementasyonlarla geni\u015fledi\u011fini g\u00f6r\u00fcyor olacaks\u0131n\u0131z. \u015eimdilik en sade haliyle incelememiz gerekirse e\u011fer <T><\/code> parametresine verilen ‘OrderSagaData’ nesnesine dikkatinizi \u00e7ekerim. Evet, saga nesnesi sayesinde servisler aras\u0131 i\u015f ak\u0131\u015f s\u00fcrecini gelen message ve event’lere g\u00f6re merkezi bir \u015fekilde y\u00f6netecek ve ileti\u015fimi ger\u00e7ekle\u015ftiriyor olaca\u011f\u0131z lakin bunu yaparken de i\u015fleyece\u011fimiz verinin t\u00fcr\u00fcn\u00fcn ‘OrderSagaData’ olaca\u011f\u0131n\u0131 bildirmi\u015f oluyoruz. Bizler i\u015f ak\u0131\u015f s\u00fcrecinin(yani sipari\u015f s\u00fcrecinin) hangi noktas\u0131nda ya da hangi servisinde olursak olal\u0131m ona g\u00f6re arkada \u00fcretilmi\u015f olan ‘OrderSagaData’ nesnesinin de\u011ferleri \u015fekillenecek ve kuraca\u011f\u0131m\u0131z korelasyon a\u011f\u0131yla da tek bir ba\u011flamla i\u00e7erisinde bir sipari\u015fin en nihai halini yine bu nesne \u00fczerinden elde edebiliyor olaca\u011f\u0131z.<\/p>\n Ayr\u0131ca Saga<\/code> abstract class’\u0131n\u0131n implemente ettirdi\u011fi CorrelateMessages<\/em> isimli metotta ise birazdan olu\u015fturaca\u011f\u0131m\u0131z ve s\u00fcre\u00e7te i\u015flemeye \u00e7al\u0131\u015faca\u011f\u0131m\u0131z message ve event’lerin, saga data s\u0131n\u0131f\u0131m\u0131z olan ‘OrderSagaData’ nesnesiyle e\u015fle\u015ftirilmesini ve bir olguya yani sipari\u015fe dair korelasyon a\u011f\u0131n\u0131n kurulmas\u0131n\u0131 sa\u011fl\u0131yor olaca\u011f\u0131z. Oraya gelece\u011fiz, \u015fimdi bunun i\u00e7in \u00f6ncelikle \u00e7al\u0131\u015fmada kullanaca\u011f\u0131m\u0131z event ve message’lar\u0131n olu\u015fturulmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.\n<\/li>\n<\/ul>\n<\/li>\n Ad\u0131m 6<\/em><\/strong> Shared – (Event ve Message’lar\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u015eimdi kurguda kullanaca\u011f\u0131m\u0131z t\u00fcm event ve message yap\u0131lanmalar\u0131n\u0131 sorumluluklar\u0131n\u0131 izah ederek tek tek olu\u015fturmaya odaklanal\u0131m. Burada olu\u015fturaca\u011f\u0131m\u0131z t\u00fcm event ve message’lar\u0131n korelasyon ili\u015fkisini sa\u011flayabilmek i\u00e7in ba\u015ftan 4. ad\u0131mda olu\u015fturdu\u011fumuz ‘BaseCorrelation’ s\u0131n\u0131f\u0131ndan t\u00fcretildi\u011fini vurgulamakta fayda g\u00f6rmekteyim.<\/p>\n\nOrderStartedEvent<\/em> \nKullan\u0131c\u0131 taraf\u0131ndan sipari\u015f verildi\u011fi an s\u00fcrecin ba\u015flad\u0131\u011f\u0131n\u0131 Saga.Orchestration.Service<\/code>‘e bildirecek olan event’tir. Yani MassTransit ile yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmadaki Tetikleyici Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir. Bu event yay\u0131nland\u0131\u011f\u0131 taktirde Saga.Orchestration.Service<\/code>‘in veritaban\u0131nda ‘OrderSagaData’ya kar\u015f\u0131l\u0131k bir sat\u0131r olu\u015fturulacak ve distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecindeki t\u00fcm ilerlemeler ad\u0131m ad\u0131m bu sat\u0131r \u00fczerinden takip ediliyor olacakt\u0131r.<\/p>\n\n\r\n public class OrderStartedEvent : BaseCorrelation\r\n {\r\n public OrderStartedEvent() { }\r\n public OrderStartedEvent(Guid correlationId) : base(correlationId) { }\r\n public int OrderId { get; set; }\r\n public int BuyerId { get; set; }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n<\/li>\nOrderCreatedEvent<\/em> \nSipari\u015f olu\u015fturulduktan ve s\u00fcre\u00e7 ba\u015flat\u0131ld\u0131ktan sonra Stock.Service<\/code>‘i tetikleyebilmek i\u00e7in yay\u0131nlanacak event’tir.<\/p>\n\n\r\n public class OrderCreatedEvent : BaseCorrelation\r\n {\r\n public OrderCreatedEvent(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem>? OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n OrderCompletedEvent<\/em> \nSipari\u015fe dair t\u00fcm servislerin i\u015flemlerini ba\u015far\u0131yla tamamland\u0131\u011f\u0131n\u0131 ve sipari\u015fin ba\u015far\u0131yla sonland\u0131\u011f\u0131n\u0131 ifade eden event’tir. Saga.Orchestration.Service<\/code>, bu event’i yay\u0131nlad\u0131\u011f\u0131 taktirde Order.Saga<\/code> servisi sipari\u015fin durumunu Completed<\/em>‘a \u00e7ekecektir. MassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.<\/p>\n\n\r\n public class OrderCompletedEvent\r\n {\r\n public int OrderId { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nAyr\u0131ca bu event’in dikkat ederseniz herhangi bir korelasyon de\u011feri bulunmamaktad\u0131r. \u00c7\u00fcnk\u00fc bu event, sipari\u015fin sonland\u0131\u011f\u0131n\u0131 ifade edece\u011finden dolay\u0131 bu bilgiyi i\u00e7erisindeki ‘OrderId’ ile ta\u015f\u0131yacak ve art\u0131k korelasyonel bir ba\u011flam i\u00e7erisinde \u00e7al\u0131\u015fmaya gerek kalmayacakt\u0131r. Bu mant\u0131kla i\u00e7eri\u011fin devam\u0131nda tecr\u00fcbe edilece\u011fi \u00fczere, OrderCompletedEvent<\/em> event’inin yay\u0131nlanaca\u011f\u0131 noktada Saga.Orchestration.Service<\/code> taraf\u0131ndan ilgili sipari\u015fe dair saga bilgisi tamamlanacak ve veritaban\u0131ndan kald\u0131r\u0131lm\u0131\u015f olacakt\u0131r. Yani birnevi sipari\u015f saga a\u00e7\u0131s\u0131ndan Finilize edilmi\u015f olacakt\u0131r. O noktaya geldi\u011fimizde bunu tekrardan hat\u0131rlataca\u011f\u0131m.\n<\/li>\n OrderFailedEvent<\/em> \nSipari\u015fe dair distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecinde servislerden herhangi birinde bir ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n s\u00f6z konusu oldu\u011funu yani uzun laf\u0131n k\u0131sas\u0131 sipari\u015fin ba\u015far\u0131s\u0131z oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class OrderFailedEvent : BaseCorrelation\r\n {\r\n public OrderFailedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n\r\n public int OrderId { get; set; }\r\n public string Message { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nBu event Saga.Orchestration.Service<\/code> taraf\u0131ndan yay\u0131nland\u0131\u011f\u0131 taktirde Order.Saga<\/code> taraf\u0131ndan ilgili sipari\u015fe dair state Fail<\/em>‘a \u00e7ekilecektir. MassTransit’te ki Ba\u015fars\u0131z\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockReservedEvent<\/em> \nSipari\u015fe dair Stock.Service<\/code>‘de ki stok i\u015flemlerinin ba\u015far\u0131l\u0131 oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class StockReservedEvent : BaseCorrelation\r\n {\r\n public StockReservedEvent(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockNotReservedEvent<\/em> \nSipari\u015fe dair Stock.Service<\/code>‘de ki stok i\u015flemlerinde ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class StockNotReservedEvent : BaseCorrelation\r\n {\r\n public StockNotReservedEvent(Guid correlationId) : base(correlationId) { }\r\n public string Message { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131s\u0131z Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentStartedEvent<\/em> \nStock.Service<\/code> i\u015flemini ba\u015far\u0131yla tamamlad\u0131\u011f\u0131 taktirde Payment.Service<\/code>‘i tetikleyecek ve \u00f6deme s\u00fcrecini ba\u015flatacak olan event’tir.<\/p>\n\n\r\n public class PaymentStartedEvent : BaseCorrelation\r\n {\r\n public PaymentStartedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n public decimal TotalPrice { get; set; }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentCompletedEvent<\/em> \nSipari\u015fe dair Payment.Service<\/code>‘de \u00f6deme i\u015flemlerinin ba\u015far\u0131l\u0131 oldu\u011funu ifade eden event\u2019tir.<\/p>\n\n\r\n public class PaymentCompletedEvent : BaseCorrelation\r\n {\r\n public PaymentCompletedEvent(Guid correlationId) : base(correlationId)\r\n {\r\n }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131l\u0131 Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n PaymentFailedEvent<\/em> \nSipari\u015fe dair Payment.Service<\/code>‘de ki \u00f6deme i\u015flemlerinde ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n oldu\u011funu ifade eden event’tir.<\/p>\n\n\r\n public class PaymentFailedEvent : BaseCorrelation\r\n {\r\n public List<OrderItem> OrderItems { get; set; }\r\n public string Messages { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Ba\u015far\u0131s\u0131z Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n StockRollbackMessage<\/em> \nPayment.Service<\/code>‘te PaymentFailedEvent<\/em> event\u2019i yay\u0131nlan\u0131rsa e\u011fer Stock.Service<\/code>‘de ki yap\u0131lan i\u015flemlerin geri al\u0131nmas\u0131n\u0131 sa\u011flayacak olan message’d\u0131r.<\/p>\n\n\r\n public class StockRollbackMessage : BaseCorrelation\r\n {\r\n public StockRollbackMessage(Guid correlationId) : base(correlationId) { }\r\n public List<OrderItem> OrderItems { get; set; }\r\n }\r\n<\/pre>\n<\/div>\nMassTransit’te ki Compensable Event<\/span>‘e kar\u015f\u0131l\u0131k gelmektedir.\n<\/li>\n<\/ol>\n<\/li>\n Ad\u0131m 7<\/em><\/strong> Saga.Orchestration.Service – (OrderSaga \u0130\u00e7erisinde Korelasyon \u0130li\u015fkisini Ger\u00e7ekle\u015ftirme)<\/span> \nEvent ve message’lar\u0131 da olu\u015fturdu\u011fumuza g\u00f6re art\u0131k 5. ad\u0131mda bahsi ge\u00e7en korelasyonel a\u011f\u0131 olu\u015fturmaya odaklanabiliriz. Bunun i\u00e7in Saga.Orchestration.Service<\/code> i\u00e7erisinde olu\u015fturdu\u011fumuz ‘OrderSaga’ s\u0131n\u0131f\u0131ndaki CorrelateMessages<\/em> metodunda a\u015fa\u011f\u0131daki geli\u015ftirmeyi ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n public class OrderSaga : Saga<OrderSagaData>\r\n {\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n config.Correlate<OrderStartedEvent>(\r\n orderStartedEvent => orderStartedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<StockReservedEvent>(\r\n stockReservedEvent => stockReservedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<StockNotReservedEvent>(\r\n stockNotReservedEvent => stockNotReservedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<PaymentCompletedEvent>(\r\n paymentCompletedEvent => paymentCompletedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n\r\n config.Correlate<PaymentFailedEvent>(\r\n paymentFailedEvent => paymentFailedEvent.CorrelationId,\r\n orderSagaData => orderSagaData.CorrelationId);\r\n }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131daki \u00e7al\u0131\u015fmay\u0131 incelerseniz e\u011fer servislerden Saga.Orchestration.Service<\/code>‘e gelecek olan event’lerin ‘CorrelationId’ de\u011ferinin, ‘OrderSagaData’ t\u00fcr\u00fcnden olan saga data’n\u0131n ‘CorrelationId’ ile e\u015fle\u015ftirilmesini Correlate<T><\/code> metoduyla ger\u00e7ekle\u015ftiriyoruz. B\u00f6ylece bir sipari\u015f s\u00fcrecinde distributed i\u015f ak\u0131\u015f\u0131na dair takibin hangi ba\u011flam \u00e7er\u00e7evesinde oldu\u011funu bu korelasyonel a\u011f sayesinde ili\u015fkilendirerek s\u0131n\u0131rlam\u0131\u015f oluyoruz.<\/p>\n Art\u0131k korelasyonel a\u011f\u0131 da kurgulad\u0131\u011f\u0131m\u0131za g\u00f6re art\u0131k saga nesnesindeki operasyonlara odaklanabiliriz.\n<\/li>\n Ad\u0131m 8<\/em><\/strong> Saga.Orchestration.Service – (OrderSaga’n\u0131n IAmInitiatedBy ve IHandleMessages \u0130mplementasyonlar\u0131n\u0131n Ger\u00e7ekle\u015ftirilmesi)<\/span> \nS\u0131rada sipari\u015f s\u00fcrecindeki distributed ak\u0131\u015f\u0131n nas\u0131l olaca\u011f\u0131n\u0131 handle etmek vard\u0131r. Yani saga nesnesine gelen event’lere kar\u015f\u0131n hangi servise hangi event’in ya da message’\u0131n g\u00f6nderilece\u011fini ayarlamam\u0131z gerekmektedir. Bunun i\u00e7in Saga.Orchestration.Service<\/code>‘de ki saga nesnesinde a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\n public class OrderSaga :\r\n Saga<OrderSagaData>,\r\n IAmInitiatedBy<OrderStartedEvent>,\r\n IHandleMessages<StockReservedEvent>,\r\n IHandleMessages<StockNotReservedEvent>,\r\n IHandleMessages<PaymentCompletedEvent>,\r\n IHandleMessages<PaymentFailedEvent>\r\n {\r\n public Task Handle(OrderStartedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(StockReservedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(StockNotReservedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(PaymentCompletedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n public Task Handle(PaymentFailedEvent message)\r\n {\r\n ...\r\n }\r\n\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n .\r\n .\r\n .\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere IAmInitiatedBy<\/code> ve IHandleMessages<\/code> interface’leri kullan\u0131lmaktad\u0131r. Bu interface’ler ile saga nesnesine di\u011fer servislerden gelecek olan event ve message’lar tan\u0131mlanarak, gerekli aksiyonlar sa\u011flanabilmektedir. Bu interface’lerin definition’lar\u0131na g\u00f6z atarsak e\u011fer;<\/p>\n \n\r\npublic interface IAmInitiatedBy<in TMessage> : IHandleMessages<TMessage> { }\r\n<\/pre>\n<\/div>\n\n\r\npublic interface IHandleMessages { }\r\n\r\npublic interface IHandleMessages<in TMessage> : IHandleMessages\r\n{\r\n Task Handle(TMessage message);\r\n}\r\n<\/pre>\n<\/div>\n\u015feklinde olduklar\u0131n\u0131 g\u00f6r\u00fcr\u00fcz. Yani bu interface’lerin her ikisinin de implementasyonunun da Task Handle(TMessage message);<\/code> imzas\u0131na kar\u015f\u0131n bir metodun uygulat\u0131ld\u0131\u011f\u0131n\u0131 s\u00f6yleyebiliriz. Dolay\u0131s\u0131yla yukar\u0131daki \u00e7al\u0131\u015fmada 9<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki Handle metot tan\u0131mlar\u0131 bu implementasyonlara kar\u015f\u0131n olu\u015fturulmu\u015ftur.<\/p>\n Burada IAmInitiatedBy<\/code> interface’i, saga’n\u0131n(yani kurgumuz gere\u011fi bir sipari\u015fin) ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flayacak event’i temsil etmektedir. 3.<\/em><\/strong> sat\u0131ra g\u00f6z atarsan\u0131z e\u011fer bu event’in OrderStartedEvent<\/em> oldu\u011fu ifade edilmekte ve b\u00f6ylece bu event yay\u0131nland\u0131\u011f\u0131 taktirde saga nesnesinin yeni bir saga data olu\u015fturaca\u011f\u0131 bildirilmi\u015f olmaktad\u0131r. Ve bu event’e kar\u015f\u0131n 9<\/em><\/strong> ile 12.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki ilgili t\u00fcr\u00fc handle eden metot tetiklenecektir.<\/p>\n IHandleMessages<\/code> interface’i ise di\u011fer event yahut message’lar\u0131 temsil etmektedir. Bu interface ile belirtilen event’lerin yay\u0131nlanmas\u0131 durumunda bu saga nesnesi taraf\u0131ndan bunlar\u0131n kar\u015f\u0131lanabilece\u011fini ifade etmemizi sa\u011flamaktad\u0131r. 14<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131ndaki metotlar ise gelecek event’in t\u00fcr\u00fcne uygun olacak \u015fekilde tetiklenecektir.\n<\/li>\n Ad\u0131m 9<\/em><\/strong> Saga.Orchestration.Service – (HandleMessage Operasyonlar\u0131n\u0131 Ger\u00e7ekle\u015ftirme)<\/span> \n\u015eimdi de handle metotlar\u0131ndaki gerekli \u00e7al\u0131\u015fmalar\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n public class OrderSaga(IBus bus) :\r\n Saga<OrderSagaData>,\r\n IAmInitiatedBy<OrderStartedEvent>,\r\n IHandleMessages<StockReservedEvent>,\r\n IHandleMessages<StockNotReservedEvent>,\r\n IHandleMessages<PaymentCompletedEvent>,\r\n IHandleMessages<PaymentFailedEvent>\r\n {\r\n public async Task Handle(OrderStartedEvent message)\r\n {\r\n if (!IsNew)\r\n return;\r\n\r\n Data.OrderId = message.OrderId;\r\n Data.BuyerId = message.BuyerId;\r\n Data.OrderItems = message.OrderItems;\r\n Data.TotalPrice = message.TotalPrice;\r\n\r\n await bus.Send(new OrderCreatedEvent(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems,\r\n });\r\n }\r\n\r\n public async Task Handle(StockReservedEvent message)\r\n {\r\n await bus.Send(new PaymentStartedEvent(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems,\r\n TotalPrice = Data.TotalPrice\r\n });\r\n }\r\n\r\n public async Task Handle(StockNotReservedEvent message)\r\n {\r\n await bus.Send(new OrderFailedEvent(message.CorrelationId)\r\n {\r\n Message = message.Message,\r\n OrderId = Data.OrderId\r\n });\r\n }\r\n\r\n public async Task Handle(PaymentCompletedEvent message)\r\n {\r\n await bus.Send(new OrderCompletedEvent()\r\n {\r\n OrderId = Data.OrderId\r\n });\r\n\r\n MarkAsComplete();\r\n }\r\n\r\n public async Task Handle(PaymentFailedEvent message)\r\n {\r\n await bus.Send(new OrderFailedEvent(message.CorrelationId)\r\n {\r\n OrderId = Data.OrderId,\r\n Message = message.Messages\r\n });\r\n\r\n await bus.Send(new StockRollbackMessage(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems\r\n });\r\n }\r\n\r\n protected override void CorrelateMessages(ICorrelationConfig<OrderSagaData> config)\r\n {\r\n .\r\n .\r\n .\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBu ad\u0131mda yap\u0131lan \u00e7al\u0131\u015fmalar\u0131 incelemeye \u00f6ncelikle inject edilen IBus<\/code> referans\u0131n\u0131 vurgulayarak ba\u015flayal\u0131m. Bizler Rebus ile mesaj g\u00f6nderim i\u015flemlerini bu referans arac\u0131l\u0131\u011f\u0131yla kolayl\u0131kla ger\u00e7ekle\u015ftirebiliyoruz.<\/p>\n 9<\/em><\/strong> ile 23.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda OrderStartedEvent<\/em>‘e kar\u015f\u0131n handle i\u015flemleri y\u00fcr\u00fct\u00fclmektedir. Bu event geldi\u011fi taktirde \u00f6ncelikle IsNew<\/code> property’si ile yeni bir saga yani sipari\u015f s\u00fcrecinin olup olmad\u0131\u011f\u0131 de\u011ferlendirilmekte ve e\u011fer ki bu sipari\u015f daha \u00f6nce i\u015flendiyse tekrar etmeye gerek g\u00f6r\u00fclmemektedir. Yok e\u011fer yeni sipari\u015f durumu s\u00f6z konusuysa o taktirde ‘OrderSagaData’ t\u00fcr\u00fcnden saga data’ya Data<\/code> property’si \u00fczerinden eri\u015filmekte ve ba\u015flat\u0131c\u0131 event’in de\u011ferleri i\u015flenmekte ve ard\u0131ndan OrderCreatedEvent<\/em> yay\u0131nlanmaktad\u0131r.<\/p>\n 25<\/em><\/strong> ile 32.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise StockReservedEvent<\/em>‘e kar\u015f\u0131l\u0131k PaymentStartedEvent<\/em>, 34<\/em><\/strong> ile 41.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda StockNotReservedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderFailedEvent<\/em>, 43<\/em><\/strong> ile 51.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda PaymentCompletedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderCompletedEvent<\/em> ve son olarak da 53<\/em><\/strong> ile 65.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda ise PaymentFailedEvent<\/em>‘e kar\u015f\u0131l\u0131k OrderFailedEvent<\/em> ile birlikte StockRollbackMessage<\/em> yay\u0131nlanmaktad\u0131r.<\/p>\n 43<\/em><\/strong> ile 51.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131na tekrar gelirsek e\u011fer burada MarkAsComplete<\/code> metodunun \u00e7a\u011fr\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6rmekteyiz. Bu metot 6. ad\u0131mda OrderCompletedEvent<\/em>‘i olu\u015ftururken bahsetti\u011fim finalize i\u015flemini ger\u00e7ekle\u015ftirmektedir. Yani, ilgili handle metodunda OrderCompletedEvent<\/em> yay\u0131nland\u0131\u011f\u0131ndan dolay\u0131 art\u0131k sipari\u015fin ba\u015far\u0131l\u0131 oldu\u011fu kabul edilmekte ve b\u00f6ylece i\u015f ak\u0131\u015f\u0131n\u0131n tamamland\u0131\u011f\u0131 ifade edilmektedir. Dolay\u0131s\u0131yla MarkAsComplete<\/code> metodu \u00e7a\u011fr\u0131lmakta ve Saga.Orchestration.Service<\/code>‘in veritaban\u0131nda sipari\u015fe dair olu\u015fturulmu\u015f olan saga data sat\u0131r\u0131 kald\u0131r\u0131lmaktad\u0131r.\n<\/li>\n Ad\u0131m 10<\/em><\/strong> Shared – (Queue’lar\u0131n ve AMQP Url’in Yap\u0131land\u0131r\u0131lmas\u0131)<\/span> \n\u015eimdi de t\u00fcm servislerin ileti\u015fim s\u00fcre\u00e7lerinde handle edecekleri mesajlar\u0131 hangi queue’lardan alacaklar\u0131n\u0131 yap\u0131land\u0131ral\u0131m. Bunun i\u00e7in Shared<\/code> katman\u0131nda a\u015fa\u011f\u0131daki s\u0131n\u0131f\u0131 olu\u015fturabiliriz.<\/p>\n\n\r\n public static class RabbitMQQueueSettings\r\n {\r\n public const string OrderInputQueueName = "order-input-queue-name";\r\n public const string StockInputQueueName = "stock-input-queue-name";\r\n public const string PaymentInputQueueName = "payment-input-queue-name";\r\n public const string SagaOrchestrationInputQueueName = "saga-orchestration-input-queue-name";\r\n }\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Saga.Orchestration.Service<\/code>‘de dahil t\u00fcm servislerin queue isimlendirmesini RabbitMQQueueSettings<\/em> s\u0131n\u0131f\u0131nda ayarlam\u0131\u015f bulunuyoruz.<\/p>\n Queue isimlerinin yan\u0131nda ayr\u0131ca servisler aras\u0131 ileti\u015fim s\u00fcrecinde kullanaca\u011f\u0131m\u0131z RabbitMQ transporter’\u0131n\u0131n AMQP Url’ine t\u00fcm servislerin eri\u015febilece\u011fi \u015fekilde bir tan\u0131mlamada bulunmam\u0131z gerekmektedir. Evet, bu i\u015flem i\u00e7in her servisin appsettings.json dosyas\u0131ndan istifade edebiliriz ki do\u011frusu da budur. \u00c7\u00fcnk\u00fc production ortam\u0131nda bu tarz de\u011ferler elbet environment’tan yap\u0131land\u0131r\u0131lacakt\u0131r. Haliyle bunda mutab\u0131k\u0131z. Lakin bizler makalemizin hacmini \u015fi\u015firmemek i\u00e7in bu de\u011feri de yine Shared<\/code> katman\u0131nda olu\u015fturdu\u011fumuz a\u015fa\u011f\u0131daki RabbitMQAMQPUrl<\/em> s\u0131n\u0131f\u0131n da tutuyor olacak ve bu best practice’i bilin\u00e7li bir \u015fekilde g\u00f6z ard\u0131 ediyor olaca\u011f\u0131z.<\/p>\n \n\r\n public class RabbitMQAMQPUrl\r\n {\r\n public const string AMQPUrl = "amqps:\/\/irresudw:slx6TGLxuMAthCz4X61dYE6Crr-Vx7lx@chimpanzee.rmq.cloudamqp.com\/irresudw";\r\n }\r\n<\/pre>\n<\/div>\nEvet, art\u0131k bundan sonraki ad\u0131mlarda bu yap\u0131land\u0131rma de\u011ferlerini kullanarak servislerimizi konfig\u00fcre edebiliriz.\n<\/li>\n Ad\u0131m 11<\/em><\/strong> Saga.Orchestration.Service – (Program.cs Yap\u0131land\u0131rmas\u0131 ve Veritaban\u0131n\u0131n Olu\u015fturulmas\u0131)<\/span> \n\u0130lk konfig\u00fcre edece\u011fimiz servis Saga.Orchestration.Service<\/code>‘dir. Bunun i\u00e7in ilgili servisin ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\nvar builder = Host.CreateApplicationBuilder(args);\r\n\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r =>\r\n r.TypeBased()\r\n .Map<OrderCreatedEvent>(RabbitMQQueueSettings.StockInputQueueName)\r\n .Map<PaymentStartedEvent>(RabbitMQQueueSettings.PaymentInputQueueName)\r\n .Map<OrderFailedEvent>(RabbitMQQueueSettings.OrderInputQueueName)\r\n .Map<OrderCompletedEvent>(RabbitMQQueueSettings.OrderInputQueueName)\r\n .Map<StockRollbackMessage>(RabbitMQQueueSettings.StockInputQueueName))\r\n .Transport(t =>\r\n t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl,\r\n inputQueueName: RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Sagas(s =>\r\n s.StoreInSqlServer("Server=localhost, 1433;Database=SagaOrchestrationRebusDB;User ID=SA;Password=1q2w3e4r+!;TrustServerCertificate=True",\r\n dataTableName: "Sagas",\r\n indexTableName: "SagaIndexes",\r\n automaticallyCreateTables: true))\r\n .Timeouts(t =>\r\n t.StoreInSqlServer("Server=localhost, 1433;Database=SagaOrchestrationRebusDB;User ID=SA;Password=1q2w3e4r+!;TrustServerCertificate=True",\r\n tableName: "Timeouts",\r\n automaticallyCreateTables: true)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n\r\nvar host = builder.Build();\r\nhost.Run();\r\n<\/pre>\n<\/div>\nYap\u0131lan \u00e7al\u0131\u015fmay\u0131 incelersek e\u011fer; 3.<\/em><\/strong> sat\u0131rda AddRebus<\/code> fonksiyonunu kullanarak Rebus servisini uygulamaya dahil ediyoruz. 4<\/em><\/strong> ile 10.<\/em><\/strong> sat\u0131r aral\u0131\u011f\u0131nda Routing<\/code> metodu ile t\u00fcr\u00fcne g\u00f6re mesajlar\u0131n hangi kuyruklara y\u00f6nlendirilece\u011fini belirliyoruz. Burada TypeBased<\/code> metodu ile y\u00f6nlendirme stratejisi olarak mesaj t\u00fcr\u00fcne dayal\u0131 bir davran\u0131\u015f\u0131 belirleyece\u011fimizi ifade etmi\u015f oluyoruz. Ayr\u0131ca Map<\/code> fonksiyonu ile de belirtilen mesaj t\u00fcr\u00fcn\u00fc \u00f6nceden ayarlad\u0131\u011f\u0131m\u0131z kuyruk ad\u0131yla e\u015fle\u015ftiriyoruz ki b\u00f6ylece bu servis taraf\u0131ndan, o t\u00fcrden mesaj\u0131n hangi kuyruktan gelece\u011fini ve t\u00fcketebilece\u011fini yap\u0131land\u0131rm\u0131\u015f oluyoruz. Tabi burada t\u00fcm mesaj t\u00fcrlerine g\u00f6re ayr\u0131 ayr\u0131 yap\u0131land\u0131rma da bulunmaktansa MapAssemblyOf<\/code> metoduyla da a\u015fa\u011f\u0131daki gibi t\u00fcm t\u00fcrlere kar\u015f\u0131n assembly bazl\u0131 k\u00fcm\u00fclatif bir tan\u0131mda bulunabilirdik.<\/p>\n \n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r =>\r\n r.TypeBased()\r\n .MapAssemblyOf<BaseCorrelation>("..queue-name..")\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\nVelhas\u0131l, 11.<\/em><\/strong> sat\u0131rdaki Transport<\/code> metodu ile de bu servisin kullanaca\u011f\u0131 transporter’\u0131 belirtiyor ve 12.<\/em><\/strong> sat\u0131rda UseRabbitMq<\/code> metodu ile RabbitMQ’ya g\u00f6re gerekli yap\u0131land\u0131rmay\u0131 sa\u011fl\u0131yoruz. Ayr\u0131ca bu servisin mesaj g\u00f6nderirken hangi kuyru\u011fa g\u00f6nderece\u011fini de inputQueueName<\/code> parametresine verilen queue de\u011feriyle belirtiyoruz. Yani Saga.Orchestration.Service<\/code> bir message’\u0131 send ya da publish etti\u011finde bu, burada belirtilen kuyru\u011fa g\u00f6nderilmi\u015f olacakt\u0131r.<\/p>\n 14.<\/em><\/strong> sat\u0131rda Sagas<\/code> metodu ile de Rebus k\u00fct\u00fcphanesinin servisler aras\u0131ndaki ileti\u015fim s\u00fcrecinde i\u015f ak\u0131\u015f\u0131n\u0131n durumunu nerede saklayaca\u011f\u0131n\u0131 belirtiyoruz.<\/p>\n Ve son olarak 19.<\/em><\/strong> sat\u0131rda \u00e7a\u011f\u0131rd\u0131\u011f\u0131m\u0131z Timeouts<\/code> metodu ile de Rebus’\u0131n timeout s\u00fcre\u00e7lerine dair kay\u0131tlar\u0131n nerede tutulaca\u011f\u0131n\u0131 yap\u0131land\u0131r\u0131yoruz.<\/p>\n Burada Sagas<\/code> ve Timeouts<\/code> i\u015flemleri i\u00e7in gerekli olan veritaban\u0131 yap\u0131lar\u0131 automaticallyCreateTables<\/code> parametresi sayesinde servis aya\u011fa kald\u0131r\u0131ld\u0131\u011f\u0131 an otomatik olarak olu\u015fturulacakt\u0131r. Tabi veritaban\u0131n\u0131 bizlerin olu\u015fturmas\u0131 gerekmektedir. Kaynaktaki connection string de\u011ferine bakarsan\u0131z veritaban\u0131 ismine SagaOrchestrationRebusDB<\/code> verdi\u011fimizi g\u00f6r\u00fcrs\u00fcn\u00fcz. Haliyle \u015fimdi bu isimde bir veritaban\u0131n\u0131 olu\u015ftural\u0131m ve ard\u0131ndan servisimizi aya\u011fa kald\u0131r\u0131p gerekli tablo yap\u0131lanmas\u0131n\u0131 generate ettirelim.<\/p>\n \n\r\nCREATE DATABASE SagaOrchestrationRebusDB\r\n<\/pre>\n<\/div>\n<\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere olu\u015fturdu\u011fumuz veritaban\u0131 i\u00e7erisine ilgili tablo yap\u0131s\u0131 olu\u015fturulmu\u015ftur. \u015eimdi olu\u015fturulan bu tablolar\u0131 inceleyelim.<\/p>\n\n\n\n\n\n\nTablolar<\/th>\n<\/tr>\n Sagas<\/th>\n SagaIndexes<\/th>\n Timeouts<\/th>\n<\/tr>\n<\/thead>\n Distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecindeki state’i saklamak ve takip etmek i\u00e7in kullan\u0131lan tablodur.<\/a>Burada i\u015f ak\u0131\u015f\u0131ndaki her bir state’i bir versiyon numaras\u0131yla temsil edece\u011fi revision<\/code> kolonunda tutmaktad\u0131r. Her bir state de\u011fi\u015fikli\u011fi bu kolonun de\u011ferini +1 art\u0131racakt\u0131r. B\u00f6ylece biz ilgili olguya dair i\u015f ak\u0131\u015f\u0131nda state’in ka\u00e7 kez de\u011fi\u015fti\u011fini \u00f6\u011frenebilmekteyiz.<\/p>\ndata<\/code> kolonunda ise her bir duruma kar\u015f\u0131n kullan\u0131lan OrderSagaData<\/em> t\u00fcr\u00fcnden saga data verisi binary format\u0131nda tutulmaktad\u0131r.\n<\/td>\n Sagas tablosuyla ili\u015fkilendirilmi\u015f olan bu SagaIndexes tablosu i\u015f ak\u0131\u015f\u0131 state’ini belirleyen index bilgilerini i\u00e7ermektedir.<\/a>saga_type<\/code> kolonunda state’i takip edilen saga data’n\u0131n t\u00fcr\u00fc, key<\/code> kolonunda korelasyon de\u011ferini ifade eden property ad\u0131 ve value<\/code> kolonunda ise i\u015f ak\u0131\u015f\u0131ndaki b\u00fct\u00fcnselli\u011fi sa\u011flayacak olan korelasyonel de\u011fer tutulmaktad\u0131r. <\/p>\n<\/td>\n Timeout s\u00fcre\u00e7lerini y\u00f6netmek i\u00e7in kullan\u0131lan tablodur. Bu tablo sayesinde, Rebus ile yap\u0131lan i\u015flemlerin yahut olaylar\u0131n belirli bir s\u00fcre i\u00e7erisinde tamamlanmas\u0131n\u0131 bekledi\u011fi durumlar\u0131 takip edebiliriz.<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\nAd\u0131m 12<\/em><\/strong> Order.API – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nS\u0131radaki konfig\u00fcre edece\u011fimiz servisimiz Order.API<\/code> olacakt\u0131r. Bunun i\u00e7in ilgili servisin ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 yapal\u0131m.<\/p>\n\n\r\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.OrderInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere Order.API<\/code>‘a t\u00fcm mesajlar\u0131n Saga.Orchestration.Service<\/code>‘in mesaj g\u00f6nderece\u011fi kuyruktan yani k\u0131saca Saga.Orchestration.Service<\/code>‘ten gelece\u011fini bildirmi\u015f bulunmaktay\u0131z. \u00c7\u00fcnk\u00fc Order.API<\/code> ve di\u011fer t\u00fcm servisler sade ve sadece Saga.Orchestration.Service<\/code>‘ten mesaj alacak ya da ona mesaj g\u00f6nderecektir. Ayr\u0131ca bu servisin g\u00f6nderece\u011fi mesajlar\u0131 da, inputQueueName<\/code> parametresine bakarsak RabbitMQQueueSettings.OrderInputQueueName<\/code> de\u011ferine kar\u015f\u0131l\u0131k gelen kuyru\u011fa g\u00f6nderece\u011fini ifade etmi\u015f bulunmaktay\u0131z. Haliyle buradaki yap\u0131land\u0131rma mant\u0131\u011f\u0131n\u0131 di\u011fer servislerde de birebir g\u00f6r\u00fcyor olaca\u011f\u0131z.<\/p>\n AutoRegisterHandlersFromAssemblyOf<\/code> metodu ise sonraki ad\u0131mlarda olu\u015fturaca\u011f\u0131m\u0131z handler s\u0131n\u0131flar\u0131n\u0131n assembly seviyesinde otomatik olarak yakalay\u0131p, register edilmesini sa\u011flamaktad\u0131r. Ha tabi, her ne kadar bu senaryoda Order.API<\/code>‘da bir handler s\u0131n\u0131f\u0131 olu\u015fturmayacak olsak da Rebus ile yap\u0131lan \u00e7al\u0131\u015fmalarda handler yap\u0131lanmalar\u0131n\u0131n aktivite edilmesi i\u00e7in bu metodun \u00e7a\u011fr\u0131lmas\u0131 elzemdir ve sonraki s\u00fcre\u00e7lerde olu\u015fturma ihtimaline nazaran uygulama seviyesinde \u00f6nceden \u00e7a\u011fr\u0131l\u0131p haz\u0131r bir \u015fekilde tutulmas\u0131 k\u00e2fidir.\n<\/li>\nAd\u0131m 13<\/em><\/strong> Order.API – (Sipari\u015f Olu\u015fturma S\u00fcrecinde OrderStartedEvent’in Yay\u0131nlanmas\u0131)<\/span> \n\u015eimdi de 2. ad\u0131mda Order.API<\/code>‘da geli\u015ftirdi\u011fimiz \/create-order<\/code> minimal api’sinde a\u015fa\u011f\u0131daki gibi OrderStartedEvent<\/em>‘i yay\u0131nlayal\u0131m ve distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecini ba\u015flatal\u0131m.<\/p>\n\n\r\n.\r\n.\r\n.\r\n\r\napp.MapPost("\/create-order", async (IBus bus, ApplicationDbContext context, CreateOrderVM model) =>\r\n{\r\n .\r\n .\r\n .\r\n\r\n OrderStartedEvent orderStartedEvent = new()\r\n {\r\n OrderId = order.Id,\r\n BuyerId = model.BuyerId,\r\n TotalPrice = order.TotalPrice,\r\n OrderItems = model.OrderItems.Select(oi => new Shared.Datas.OrderItem\r\n {\r\n Count = oi.Count,\r\n Price = oi.Price,\r\n ProductId = oi.ProductId\r\n }).ToList(),\r\n CorrelationId = Guid.NewGuid(),\r\n };\r\n\r\n await bus.Send(orderStartedEvent);\r\n\r\n return Results.Created();\r\n});\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 14<\/em><\/strong> Stock.Service – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nStock.Service<\/code>‘de de \u00f6nceki ad\u0131mlarda anlat\u0131lan mant\u0131kta yap\u0131land\u0131rmay\u0131 a\u015fa\u011f\u0131daki gibi sa\u011flayal\u0131m.<\/p>\n\n\r\n.\r\n.\r\n.\r\n\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.StockInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 15<\/em><\/strong> Stock.Service – (OrderCreatedEventHandler ve StockRollbackMessageHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nStock.Service<\/code>‘i yap\u0131land\u0131rd\u0131ktan sonra gerekli handler s\u0131n\u0131flar\u0131n\u0131 a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderCreatedEventHandler(MongoDBService mongoDBService, IBus bus) : IHandleMessages<OrderCreatedEvent>\r\n {\r\n public async Task Handle(OrderCreatedEvent message)\r\n {\r\n List<bool> stockResults = new();\r\n var stockCollection = mongoDBService.GetCollection<Models.Stock>();\r\n\r\n foreach (var orderItem in message.OrderItems)\r\n stockResults.Add(await (await stockCollection.FindAsync(s => s.ProductId == orderItem.ProductId && s.Count >=\r\n(long)orderItem.Count)).AnyAsync());\r\n\r\n if (stockResults.TrueForAll(s => s.Equals(true)))\r\n {\r\n foreach (var orderItem in message.OrderItems)\r\n {\r\n var stock = await (await stockCollection.FindAsync(s => s.ProductId == orderItem.ProductId)).FirstOrDefaultAsync();\r\n\r\n stock.Count -= orderItem.Count;\r\n\r\n await stockCollection.FindOneAndReplaceAsync(x => x.ProductId == orderItem.ProductId, stock);\r\n }\r\n\r\n StockReservedEvent stockReservedEvent = new(message.CorrelationId)\r\n {\r\n OrderItems = message.OrderItems\r\n };\r\n\r\n await bus.Send(stockReservedEvent);\r\n }\r\n else\r\n {\r\n StockNotReservedEvent stockNotReservedEvent = new(message.CorrelationId)\r\n {\r\n Message = "Stok yetersiz...."\r\n };\r\n\r\n await bus.Send(stockNotReservedEvent);\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class StockRollbackMessageHandler(MongoDBService mongoDBService) : IHandleMessages<StockRollbackMessage>\r\n {\r\n public async Task Handle(StockRollbackMessage message)\r\n {\r\n var stockCollection = mongoDBService.GetCollection<Models.Stock>();\r\n\r\n foreach (var orderItem in message.OrderItems)\r\n {\r\n var stock = await (await stockCollection.FindAsync(x => x.ProductId == orderItem.ProductId)).FirstOrDefaultAsync();\r\n\r\n stock.Count += orderItem.Count;\r\n await stockCollection.FindOneAndReplaceAsync(x => x.ProductId == orderItem.ProductId, stock);\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\nYukar\u0131daki kodlar\u0131 incelerseniz e\u011fer gerekli stok i\u015flemleri ger\u00e7ekle\u015ftirilmekte yahut compensable transaction operasyonu y\u00fcr\u00fct\u00fclmektedir.\n<\/li>\n Ad\u0131m 16<\/em><\/strong> Payment.Service – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nAyn\u0131 mant\u0131kta Payment.Service<\/code>‘de de ‘Program.cs’ yap\u0131land\u0131rmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.PaymentInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 17<\/em><\/strong> Payment.Service – (PaymentStartedEventHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nVe \u00f6demeyle ilgili i\u015flemleri ba\u015flatacak olan PaymentStartedEvent<\/em>‘e kar\u015f\u0131n PaymentStartedEventHandler<\/em>‘\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\n public class PaymentStartedEventHandler(IBus bus) : IHandleMessages<PaymentStartedEvent>\r\n {\r\n public async Task Handle(PaymentStartedEvent message)\r\n {\r\n \/\/\u00d6deme ba\u015far\u0131l\u0131...\r\n await bus.Send(new PaymentCompletedEvent(message.CorrelationId));\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada farazi bir \u00f6deme i\u015fleminin yap\u0131ld\u0131\u011f\u0131n\u0131 varsayarak yolumuza devam edelim.\n<\/li>\n Ad\u0131m 19<\/em><\/strong> Order.Saga – (Program.cs Yap\u0131land\u0131rmas\u0131)<\/span> \nVe son olarak Order.Saga<\/code> servisinde de ‘Program.cs’ yap\u0131land\u0131rmas\u0131n\u0131 ger\u00e7ekle\u015ftirelim.<\/p>\n\n\r\n.\r\n.\r\n.\r\nbuilder.Services.AddRebus(rebus => rebus\r\n .Routing(r => r.TypeBased().MapAssemblyOf<BaseCorrelation>(RabbitMQQueueSettings.SagaOrchestrationInputQueueName))\r\n .Transport(t => t.UseRabbitMq(RabbitMQAMQPUrl.AMQPUrl, inputQueueName: RabbitMQQueueSettings.OrderInputQueueName)));\r\n\r\nbuilder.Services.AutoRegisterHandlersFromAssemblyOf<Program>();\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 18<\/em><\/strong> Order.Saga – (OrderCompletedEventHandler ve OrderFailedEventHandler’\u0131n Olu\u015fturulmas\u0131)<\/span> \nVe ard\u0131ndan sipari\u015fin nihai durumunu belirleyecek olan handler’lar\u0131 olu\u015ftural\u0131m.<\/p>\n\n\r\n public class OrderCompletedEventHandler(ApplicationDbContext applicationDbContext) : IHandleMessages<OrderCompletedEvent>\r\n {\r\n public async Task Handle(OrderCompletedEvent message)\r\n {\r\n Order.Saga.Models.Entities.Order order = await applicationDbContext.Orders.FindAsync(message.OrderId);\r\n if (order != null)\r\n {\r\n order.OrderStatus = Models.Enums.OrderStatus.Completed;\r\n await applicationDbContext.SaveChangesAsync();\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class OrderFailedEventHandler(ApplicationDbContext applicationDbContext) : IHandleMessages<OrderFailedEvent>\r\n {\r\n public async Task Handle(OrderFailedEvent message)\r\n {\r\n Order.Saga.Models.Entities.Order order = await applicationDbContext.Orders.FindAsync(message.OrderId);\r\n if (order != null)\r\n {\r\n order.OrderStatus = Order.Saga.Models.Enums.OrderStatus.Fail;\r\n await applicationDbContext.SaveChangesAsync();\r\n }\r\n }\r\n }\r\n<\/pre>\n<\/div>\nBurada dikkat edilmesi gereken nokta \u015fudur ki, Order.Saga<\/code> servisinde yap\u0131lan veritaban\u0131 \u00e7al\u0131\u015fmalar\u0131nda Order.API<\/code>‘dakine benzer context ve entity yap\u0131s\u0131 in\u015fa edilmi\u015f ve IoC Container’a provide edilmi\u015ftir. Tabi tekrara girmemek ve i\u00e7eri\u011fi haddinden fazla uzatmamak i\u00e7in bu k\u0131s\u0131mlar es ge\u00e7ilmi\u015ftir. Yap\u0131lan \u00e7al\u0131\u015fmalar\u0131n tam teferruatl\u0131 i\u00e7eri\u011fine makalenin sonunda payla\u015f\u0131lan github linki \u00fczerinden g\u00f6zlemde bulunabilirsiniz.\n<\/li>\n Ad\u0131m 19<\/em><\/strong> Test<\/span> \nArt\u0131k yap\u0131lan bunca \u00e7al\u0131\u015fman\u0131n testini ger\u00e7ekle\u015ftirebiliriz. Bunun i\u00e7in servislerimizi derleyip aya\u011fa kald\u0131ral\u0131m ve a\u015fa\u011f\u0131daki json data e\u015fli\u011finde bir sipari\u015f talebinde bulunal\u0131m.<\/p>\n\n\r\n{\r\n "buyerId": 1,\r\n "orderItems": [\r\n {\r\n "productId": 1,\r\n "count": 10,\r\n "price": 5\r\n },\r\n {\r\n "productId": 2,\r\n "count": 30,\r\n "price": 50\r\n },\r\n {\r\n "productId": 3,\r\n "count": 5,\r\n "price": 5\r\n }\r\n ]\r\n}\r\n<\/pre>\n<\/div>\n<\/a>Bu i\u015flem neticesinde s\u00fcrecin a\u015fa\u011f\u0131daki g\u00f6rseldeki gibi oldu\u011funu g\u00f6rece\u011fiz.<\/a>Ayr\u0131ca yeri gelmi\u015fken bahsetmekte fayda g\u00f6rmekteyim ki, distributed i\u015f ak\u0131\u015f\u0131 s\u00fcrecinde Sagas tablosunun ‘data’ kolonundaki binary veriyi a\u015fa\u011f\u0131daki sorguyla metinsele d\u00f6n\u00fc\u015ft\u00fcrebilir ve i\u00e7eri\u011fine dair g\u00f6zlemde bulunabilirsiniz.<\/p>\n \n\r\nSELECT CONVERT(VARCHAR(MAX), data)\r\nFROM SagaOrchestrationRebusDB.dbo.Sagas\r\n<\/pre>\n<\/div>\n\n{“$type”:”Saga.Orchestration.Service.SagaDatas.OrderSagaData, Saga.Orchestration.Service”,”Id”:”7e630713-c610-4c9b-8a38-03f61f3060a8″,”Revision”:1,”OrderId”:5,”BuyerId”:1,”TotalPrice”:1825.0,”OrderItems”:{“$type”:”System.Collections.Generic.List`1[[Shared.Datas.OrderItem, Shared]], System.Private.CoreLib”,”$values”:[{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:1,”Count”:10,”Price”:5.0},{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:2,”Count”:30,”Price”:50.0},{“$type”:”Shared.Datas.OrderItem, Shared”,”ProductId”:4,”Count”:55,”Price”:5.0}]},”CorrelationId”:”c5d0b313-2bf4-4081-935f-72fa0c9895f0″}\n<\/div>\n<\/li>\n<\/ul>\n\u0130\u015fte bu kadar \ud83d\ude42<\/p>\n Nihai olarak; \nSaga Orchestration implementasyonunu Rebus k\u00fct\u00fcphanesiyle, test ad\u0131m\u0131 da dahil olmak \u00fczere 19 ad\u0131mda uygulam\u0131\u015f ve MassTransit’e nazaran konuya dair alternatif bir yakla\u015f\u0131m\u0131 tecr\u00fcbe etmi\u015f bulunmaktay\u0131z. Nacizane fikrim, Rebus k\u00fct\u00fcphanesi MassTransit’e kar\u015f\u0131n yap\u0131land\u0131rma a\u00e7\u0131s\u0131ndan d\u00fc\u015f\u00fck bir komplikasyona sahip olsa da onun kadar geni\u015f bir yelpazede entegrasyon imkan\u0131 sa\u011flamamakta ve k\u00fc\u00e7\u00fck yahut orta \u00f6l\u00e7ekli uygulamalarda daha pratik \u00e7\u00f6z\u00fcmler sunmaktad\u0131r.<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\nNot : \u00d6rnek \u00e7al\u0131\u015fmaya a\u015fa\u011f\u0131daki github adresinden eri\u015febilirsiniz. \nhttps:\/\/github.com\/gncyyldz\/Saga.Orchestration.Example.With.Rebus<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Malumunuz, microservice mimarisiyle tasarlanm\u0131\u015f yaz\u0131l\u0131mlar\u0131m\u0131zda kullan\u0131c\u0131lar taraf\u0131ndan ba\u015flat\u0131lan i\u015flem ya da g\u00f6revlerin, bir servis taraf\u0131ndan al\u0131n\u0131p ard\u0131ndan belirli servisler \u00fczerinde mant\u0131ksal bir tetikleme silsilesiyle i\u015flenme ve koordine edilme s\u00fcre\u00e7lerini y\u00fcr\u00fctmemize ve biryandan da...<\/p>\n","protected":false},"author":1,"featured_media":26849,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4912,2739,3573],"tags":[3575,4994,4996,4995,4993,4372],"class_list":["post-26819","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-net-8","category-net-core","category-microservices","tag-microservice","tag-rebus","tag-rebus-microservice","tag-rebus-saga","tag-rebus-saga-orchestration","tag-saga-orchestration"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819","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=26819"}],"version-history":[{"count":20,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819\/revisions"}],"predecessor-version":[{"id":26850,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26819\/revisions\/26850"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/26849"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}