<\/div>\n

Merhaba,<\/p>\n

\u00d6nceki yaz\u0131lar\u0131m\u0131zdan Nedir Bu Onion Architecture? Tam Teferruatl\u0131 \u0130nceleyelim<\/a> ba\u015fl\u0131kl\u0131 makalemizde inceledi\u011fimiz Onion Architecture \u00fczerinde ya\u015fanabilecek bir tak\u0131m problemleri ele alacak ve bunlara CQRS Pattern<\/a> ile \u00e7\u00f6z\u00fcm getirmeye \u00e7al\u0131\u015faca\u011f\u0131z.<\/p>\n

\u0130lgili makaleye g\u00f6z atarsan\u0131z e\u011fer ‘Presentation’ katman\u0131ndaki API uygulamas\u0131ndan d\u0131\u015f d\u00fcnyan\u0131n taleplerine kar\u015f\u0131l\u0131k \u00fcretilen datalar ‘Domain’ katman\u0131ndaki entity’ler t\u00fcr\u00fcnde sunulmaktad\u0131r. Bu tarz bir sunum biz geli\u015ftiriciler taraf\u0131ndan pek tercih edilebilir bir durum de\u011fildir. Nihayetinde ‘Application’ katman\u0131nda DTO nesnelerimiz mevcuttur ve controller’lar bu DTO’lar\u0131 a\u015f\u0131p direkt ‘Domain’de ki entity’lere ula\u015f\u0131yorsa e\u011fer burada tasar\u0131msal bir sak\u0131nca var demektir. B\u00f6yle bir durumda controller, istek neticesinde verileri entity t\u00fcr\u00fcnde elde etmekte ve bu elde edilen verileri client’a sunabilmek i\u00e7in DTO d\u00f6n\u00fc\u015f\u00fcm\u00fcnden(conversion) sorumlu olmaktad\u0131r. Halbuki bu conversion i\u015fleminden sorumlu olan controller de\u011fil, ‘Application’ katman\u0131d\u0131r. Veri sorgulan\u0131rken ‘Application’ katman\u0131ndan \u00f6yle ya da b\u00f6yle DTO t\u00fcr\u00fcnde gelmeli ve controller herhangi bir d\u00f6n\u00fc\u015f\u00fcmle ya da t\u00fcr ile ilgili i\u015flemlerle ilgilenmeksizin gelen datay\u0131 d\u0131\u015f d\u00fcnyaya g\u00f6ndermelidir.<\/p>\n

\u00c7\u00f6z\u00fcm<\/h3>\n
Controller’lar da ki conversion sorumlulu\u011funun ar\u0131nd\u0131r\u0131l\u0131p ‘Application’ katman\u0131na verilebilmesi ve b\u00f6ylece ‘Presentation’ katman\u0131 a\u00e7\u0131s\u0131ndan direkt olarak talep edilen datan\u0131n entity ve DTO t\u00fcrleriyle, ne \u015fekilde hangi \u015fartlarda d\u00f6n\u00fc\u015f\u00fcm\u00fcn ve e\u015fle\u015ftirmenin ger\u00e7ekle\u015ftirildi\u011fiyle ilgilenmeksizin ‘Application’dan talep edilmesi ve m\u00fcmk\u00fcn mertebe Action metotlar da ger\u00e7ekle\u015ftirilen operasyonlar\u0131n sadele\u015ftirilebilmesi i\u00e7in MediatR k\u00fct\u00fcphanesi e\u015fli\u011finde CQRS pattern’i kullanaca\u011f\u0131z.<\/p>\n

Pratik Uygulama<\/h3>\n
$\"Onion$ <\/a>\u00d6ncelikle ‘Application’ katman\u0131na MediatR<\/a> ve MediatR.Extensions.Microsoft .DependencyInjection<\/a> isimli k\u00fct\u00fcphaneleri kural\u0131m. Ard\u0131ndan ilgili katmanda ‘Features’ isimli klas\u00f6r i\u00e7erisinde ‘Commands’ ve ‘Queries’ isimli iki klas\u00f6r olu\u015ftural\u0131m ve CQRS pattern yap\u0131lanmas\u0131n\u0131 burada kural\u0131m.<\/p>\n
Esas\u0131nda buradaki t\u00fcm ‘..Request’ ve ‘..Response’ s\u0131n\u0131flar\u0131 sistemdeki DTO s\u0131n\u0131flar\u0131na kar\u015f\u0131l\u0131k gelmektedir. Amma velakin bizler CQRS pattern’\u0131 daha d\u00fczenli olu\u015fturabilmek i\u00e7in sistemi bu \u015fekilde in\u015fa etmeyi tercih edece\u011fiz. Sizlere de tavsiyem bu y\u00f6ndedir. Aksi taktirde say\u0131lar\u0131 artt\u0131k\u00e7a hangi DTO hangi command ya da query’nin oldu\u011fu haddinden fazla kompleksle\u015fecektir.<\/p>\n
Burada yap\u0131lanman\u0131n kayna\u011f\u0131na dair herhangi bir \u00f6rnek g\u00f6stermenin gere\u011fi yok kanaatindeyim. Nihayetinde yukar\u0131da da adresini referans etti\u011fim ve \u00f6nceden klavyeye alm\u0131\u015f oldu\u011fum CQRS Pattern<\/a> makalemizde bu yap\u0131lanman\u0131n ne oldu\u011funu ve hangi mant\u0131kla in\u015fa edildi\u011fini tam teferruatl\u0131 ele alm\u0131\u015f bulunmaktay\u0131z.<\/p>\n

AutoMapper Konfig\u00fcrasyonu<\/h3>\n

Tabi CQRS pattern’\u0131 kullan\u0131rken bir yandan da Handle s\u0131n\u0131flar\u0131ndaki conversion\/mapping operasyonlar\u0131n\u0131n AutoMapper<\/a> k\u00fct\u00fcphanesiyle ne \u015fekilde daha pratik hale getirildi\u011fini g\u00f6zlemleyebilmek i\u00e7in herhangi bir handler s\u0131n\u0131f\u0131n\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131ya alal\u0131m.<\/p>\n

\r\n    public class GetAllProductQueryHandler : IRequestHandler<GetAllProductQueryRequest, List<GetAllProductQueryResponse>>\r\n    {\r\n        readonly IProductRepository _productRepository;\r\n        IMapper _mapper;\r\n        public GetAllProductQueryHandler(IProductRepository productRepository, IMapper mapper)\r\n        {\r\n            _productRepository = productRepository;\r\n            _mapper = mapper;\r\n        }\r\n        public async Task<List<GetAllProductQueryResponse>> Handle(GetAllProductQueryRequest request, CancellationToken cancellationToken)\r\n        {\r\n            var products = await _productRepository.GetAsync();\r\n            return _mapper.Map<List<GetAllProductQueryResponse>>(products);\r\n        }\r\n    }\r\n<\/pre>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere handler s\u0131n\u0131flar\u0131nda repository \u00fczerinden entity t\u00fcr\u00fcnde elde edilen datalar response nesnelerine ‘IMapper’ \u00fczerinden h\u0131zl\u0131ca d\u00f6n\u00fc\u015ft\u00fcr\u00fclmektedir. Bunun i\u00e7in ‘Application’ katman\u0131ndaki ‘Mapping’ klas\u00f6r\u00fc i\u00e7erisinde;<\/p>\n\r\n    public class GeneralMapping : Profile\r\n    {\r\n        public GeneralMapping()\r\n        {\r\n            CreateMap<Product, GetAllProductQueryResponse>()\r\n                .ReverseMap();\r\n            CreateMap<Product, GetByIdProductQueryResponse>()\r\n                .ReverseMap();\r\n            CreateMap<Product, GetWhereProductQueryResponse>()\r\n                .ReverseMap();\r\n        }\r\n    }\r\n<\/pre>\ni\u00e7eri\u011fine sahip bir ‘Profile’ s\u0131n\u0131f\u0131n\u0131n tan\u0131mlanmas\u0131 yeterli olacakt\u0131r.<\/p>\n
T\u00fcm bu i\u015flemlerden sonra ‘Application’ katman\u0131n\u0131n ‘ServiceRegistration’ s\u0131n\u0131f\u0131nda a\u015fa\u011f\u0131daki konfig\u00fcrasyonlar\u0131n yap\u0131lmas\u0131 gerekmektedir;<\/p>\n\r\n    static public class ServiceRegistration\r\n    {\r\n        public static void AddApplicationServices(this IServiceCollection serviceCollection)\r\n        {\r\n            serviceCollection.AddMediatR(Assembly.GetExecutingAssembly());\r\n            serviceCollection.AddAutoMapper(Assembly.GetExecutingAssembly());\r\n        }\r\n    }\r\n<\/pre>\nGeriye ‘Presentation’ katman\u0131ndaki Web API uygulamas\u0131nda bu servisleri kullanan a\u015fa\u011f\u0131daki controller’\u0131n tasarlanmas\u0131 kalmaktad\u0131r;<\/p>\n\r\n    [Route("api\/[controller]")]\r\n    [ApiController]\r\n    public class ProductsController : ControllerBase\r\n    {\r\n        IMediator _mediator;\r\n        public ProductsController(IMediator mediator)\r\n        {\r\n            _mediator = mediator;\r\n        }\r\n\r\n        [HttpGet]\r\n        public async Task<List<GetAllProductQueryResponse>> Get()\r\n        {\r\n            return await _mediator.Send(new GetAllProductQueryRequest());\r\n        }\r\n\r\n        [HttpGet("{Id}")]\r\n        public async Task<GetByIdProductQueryResponse> Get([FromQuery] GetByIdProductQueryRequest request)\r\n        {\r\n            return await _mediator.Send(request);\r\n        }\r\n\r\n        [HttpGet("search\/{Name}")]\r\n        public async Task<List<GetWhereProductQueryResponse>> Get([FromQuery] GetWhereProductQueryRequest request)\r\n        {\r\n            return await _mediator.Send(request);\r\n        }\r\n\r\n        [HttpPost]\r\n        public async Task<CreateProductCommandResponse> Post([FromBody] CreateProductCommandRequest request)\r\n        {\r\n            return await _mediator.Send(request);\r\n        }\r\n    }\r\n<\/pre>\n\u0130\u015fte bu kadar… G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bu tarz bir tasar\u0131m sayesinde controller’lar client’a iletilecek verinin t\u00fcr\u00fcyle yahut conversion i\u015flemleriyle ilgilenmemekte, direkt olarak i\u015f kural\u0131n\u0131 uygulay\u0131p geriye sonu\u00e7 d\u00f6nmektedirler.<\/p>\nFluent Validation Konfig\u00fcrasyonu<\/h3>\nHandle operasyonlar\u0131nda client’lardan gelecek olan verileri do\u011frulamam\u0131z gerekebilmektedir. Bunun i\u00e7in en etkili k\u00fct\u00fcphanelerden biri olan FluentValidation<\/a>‘\u0131 kullanabiliriz.
\n
<\/a>T\u00fcm bu k\u00fct\u00fcphaneleri Application katman\u0131na y\u00fckleyiniz…<\/p><\/div><\/p>\n<\/a>Fluent Validation k\u00fct\u00fcphanesi Validator s\u0131n\u0131flar\u0131 \u00fczerinden do\u011frulama ger\u00e7ekle\u015ftirmektedir. Onion Architecture’da Validator s\u0131n\u0131flar\u0131n\u0131 ‘Features’ alt\u0131nda ilgili Command yahut Query alt\u0131nda olu\u015fturmam\u0131z yeterli olacakt\u0131r.<\/p>\n
\r\n    public class CreateProductCommandValidator : AbstractValidator<CreateProductCommandRequest>\r\n    {\r\n        public CreateProductCommandValidator()\r\n        {\r\n            RuleFor(p => p.Name)\r\n                .NotNull()\r\n                .WithMessage("L\u00fctfen 'Name'i bo\u015f ge\u00e7meyiniz.")\r\n                .MaximumLength(20)\r\n                .MinimumLength(3)\r\n                .WithMessage("'Name' de\u011feri 3 ile 20 karakter aras\u0131nda olmal\u0131d\u0131r.");\r\n            RuleFor(p => p.Price)\r\n                .Must(p => p > 0)\r\n                .WithMessage("L\u00fctfen 'Price' de\u011ferini do\u011fru giriniz.");\r\n        }\r\n    }\r\n<\/pre>\nArd\u0131ndan bu validator’\u0131 t\u00fcrl\u00fc y\u00f6ntemlerle i\u015fleyebilir ve kullanabiliriz. Misal ben burada ‘ValidationFilter’ isminde bir filter olu\u015fturaca\u011f\u0131m ve ilgili validasyonlar\u0131 burada kontrol edece\u011fim. Tabi bu filter’\u0131 ‘Infrastructure’ katman\u0131nda olu\u015fturmam\u0131z daha do\u011fru olacakt\u0131r. Haliyle a\u015fa\u011f\u0131daki gibi bir tasar\u0131m neticesinde i\u015flemimizi ger\u00e7ekle\u015ftiriyoruz;
\n<\/a><\/p>\n
\r\n    public class ValidationFilter : IAsyncActionFilter\r\n    {\r\n        public async Task OnActionExecutionAsync(ActionExecutingContext context, ActionExecutionDelegate next)\r\n        {\r\n            if (!context.ModelState.IsValid)\r\n            {\r\n                var errors = context.ModelState\r\n                    .Where(x => x.Value.Errors.Count > 0)\r\n                    .ToDictionary(e => e.Key, e => e.Value.Errors.Select(e => new\r\n                    {\r\n                        e.ErrorMessage\r\n                    })).ToArray();\r\n\r\n                context.Result = new BadRequestObjectResult(errors);\r\n                return;\r\n            }\r\n            await next();\r\n        }\r\n    }\r\n<\/pre>\n\u0130lgili filter’\u0131 olu\u015fturduktan sonra ‘Presentation’ katman\u0131ndaki ‘WebAPI’ projesinin ‘Startup.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki konfig\u00fcrasyonu ger\u00e7ekle\u015ftirelim.<\/p>\n\r\n    public class Startup\r\n    {\r\n        .\r\n        .\r\n        .\r\n        public void ConfigureServices(IServiceCollection services)\r\n        {\r\n            services.AddApplicationServices();\r\n            services.AddPersistenceServices(Configuration);\r\n            services.AddInfrastructureServices();\r\n\r\n            services.AddControllers(options => options.Filters.Add<ValidationFilter>())\r\n                .AddFluentValidation(configuration => configuration\r\n                    .RegisterValidatorsFromAssemblyContaining<Application.Features.Commands.CreateProduct.CreateProductCommandValidator>())\r\n                .ConfigureApiBehaviorOptions(o => o.SuppressModelStateInvalidFilter = true);\r\n            .\r\n            .\r\n            .\r\n        }\r\n        .\r\n        .\r\n        .\r\n    }\r\n<\/pre>\nBurada 12<\/strong><\/em> ile 15.<\/strong><\/em> sat\u0131rlar aras\u0131na g\u00f6z atarsan\u0131z e\u011fer ilgili entegrasyon sa\u011flanmaktad\u0131r. 12.<\/strong><\/em> sat\u0131rda AddControllers(options => options.Filters.Add<ValidationFilter>())<\/code> komutu ile geli\u015ftirilen ValidationFilter isimli filter’\u0131 uygulamaya dahil ediyoruz. 13.<\/strong><\/em> sat\u0131rda ise Fluent Validation k\u00fct\u00fcphanesini uygulamaya entegre ediyor ve 14.<\/strong><\/em> sat\u0131rda ise validator s\u0131n\u0131flar\u0131n\u0131n hangi assembly’den okunaca\u011f\u0131n\u0131 bildiriyoruz. Son olarak da 15.<\/strong><\/em> sat\u0131rda model state’lerinin otomatik kontrol edilmesini pasifle\u015ftiriyoruz. B\u00f6ylece art\u0131k her bir istek geldi\u011finde ilgili filter tetiklenecek ve validation kontrol\u00fc sa\u011flam\u0131\u015f olacakt\u0131r. Uygun olmayan bir model post edildi\u011fi zaman a\u015fa\u011f\u0131dakine benzer bir hata al\u0131nacakt\u0131r.<\/p>\n<\/a><\/p>\n
B\u00f6ylece Onion Architecture \u00fczerinde CQRS + MediatR pattern’\u0131n nas\u0131l uyguland\u0131\u011f\u0131n\u0131 ve akabinde AutoMapper ile conversion i\u015flemlerinin nas\u0131l otomatize edildi\u011fini ve Fluent Validation sayesinde de validation kontrol\u00fcn\u00fcn nas\u0131l yap\u0131ld\u0131\u011f\u0131n\u0131 kombine olarak incelemi\u015f olduk. Umar\u0131m verimli olmu\u015ftur…<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…
\n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n
Not : \u00d6rnek projeyi indirmek i\u00e7in buraya<\/a> t\u0131klay\u0131n\u0131z.<\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, \u00d6nceki yaz\u0131lar\u0131m\u0131zdan Nedir Bu Onion Architecture? Tam Teferruatl\u0131 \u0130nceleyelim ba\u015fl\u0131kl\u0131 makalemizde inceledi\u011fimiz Onion Architecture \u00fczerinde ya\u015fanabilecek bir tak\u0131m problemleri ele alacak ve bunlara CQRS Pattern ile \u00e7\u00f6z\u00fcm getirmeye \u00e7al\u0131\u015faca\u011f\u0131z. Problemleri Tan\u0131yal\u0131m \u0130lgili makaleye...<\/p>\n","protected":false},"author":1,"featured_media":21001,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2739,12],"tags":[4150,4162,4151,4157,4153,4159,4144,4160,4161,4163],"class_list":["post-21162","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-net-core","category-c-sharp-c","tag-cqrs","tag-cqrs-automapper","tag-cqrs-pattern","tag-mediator-pattern","tag-mediatr","tag-mediatr-library","tag-onion-architecture","tag-onion-architecture-cqrs","tag-onion-architecture-cqrs-mediatr","tag-onion-architecture-automapper"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/21162","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=21162"}],"version-history":[{"count":38,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/21162\/revisions"}],"predecessor-version":[{"id":21209,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/21162\/revisions\/21209"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/21001"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=21162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=21162"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=21162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}