{"id":551,"date":"2016-02-14T22:25:43","date_gmt":"2016-02-14T20:25:43","guid":{"rendered":"https:\/\/gokhan-gokalp.com\/?p=551"},"modified":"2016-09-08T15:14:28","modified_gmt":"2016-09-08T12:14:28","slug":"remote-facade-pattern-ile-network-verimliligini-arttirmak","status":"publish","type":"post","link":"https:\/\/gokhan-gokalp.com\/tr\/remote-facade-pattern-ile-network-verimliligini-arttirmak\/","title":{"rendered":"Remote Facade Pattern ile Network Verimlili\u011fini Artt\u0131rmak"},"content":{"rendered":"

Merhaba arkada\u015flar.<\/p>\n

Bu makalemde\u00a0sizlere distributed architecture<\/strong> design pattern’leri aras\u0131nda bulunan Remote Facade<\/strong>\u00a0pattern’i hakk\u0131ndaki bilgilerimi aktarmaya \u00e7al\u0131\u015faca\u011f\u0131m.<\/p>\n

Bu\u00a0pattern’i anlad\u0131\u011f\u0131m\u0131zda\u00a0her ne kadar basit ve kolay gelecek olsa da, asl\u0131nda yapt\u0131\u011f\u0131 i\u015f ve\u00a0sa\u011flayaca\u011f\u0131 fayda a\u00e7\u0131s\u0131ndan asla k\u00fc\u00e7\u00fcmsememeliyiz.\u00a0G\u00fcn\u00fcm\u00fczde mobil uygulamalar sayesinde\u00a0RESTful tabanl\u0131 mimarilerin\u00a0git gide pop\u00fclerle\u015fmesi ile birlikte,\u00a0yeni geli\u015ftirilen ve mevcut sistemler yava\u015f yava\u015f servis y\u00f6nelimli mimarilere kaymaktad\u0131r. Bu mimarilerin getirdi\u011fi faydalar\u0131n yan\u0131 s\u0131ra, “latency” ve “network yava\u015fl\u0131\u011f\u0131” gibi problemleri de beraberinde getirmektedir. Helede bu servislerin implementasyonu s\u0131ras\u0131nda yanl\u0131\u015f kararlar verilip, her bir i\u015flem i\u00e7in s\u00fcrekli ilgili servis call ediliyorsa. Bu gibi durumlarda fazlas\u0131yla servis \u00e7a\u011fr\u0131lar\u0131nda bulunulaca\u011f\u0131 i\u00e7in, ilgili servis \u00e7a\u011fr\u0131s\u0131 yapan uygulaman\u0131n h\u0131z performans\u0131 hemde \u00e7a\u011fr\u0131lan servisin y\u00fcksek concurrent<\/strong> i\u015flem an\u0131nda \u00f6l\u00e7eklenebilirli\u011fini<\/strong> sa\u011flamak zamanla imkans\u0131z bir hale gelecektir. Peki bu gibi durumlarda neler yapmal\u0131y\u0131z?, nelere dikkat etmeliyiz k\u0131sm\u0131na bir bakal\u0131m.<\/p>\n

Nedir Remote Facade?<\/h2>\n

\"remote-facede\"<\/a><\/p>\n

Martin Fowler bu pattern i\u00e7in kitab\u0131nda derki;<\/p>\n

“Provides a coarse-grained facade on fine-grained objects to improve efficiency over a network”<\/p><\/blockquote>\n

Yani Remote Facade’\u0131n \u00f6z\u00fcnde yapt\u0131\u011f\u0131 i\u015f,\u00a0network verimlili\u011fini artt\u0131rmak i\u00e7in<\/strong> birden fazla veriyi\u00a0servis \u00fczerinden tek tek \u00e7ekmek yerine bunu bir nesne \u00fczerinde bir kere<\/strong> \u00e7ekmektir. Bu sayede hem client taraf\u0131nda performans art\u0131\u015f\u0131 sa\u011flam\u0131\u015f hemde servis taraf\u0131nda transaction say\u0131s\u0131n\u0131 azaltaca\u011f\u0131m\u0131z i\u00e7in verimlili\u011finide\u00a0sa\u011flam\u0131\u015f oluruz.<\/p>\n

Remote Facade pattern’inin bir ba\u015fka faydas\u0131 ise bize, karma\u015f\u0131k business i\u015flemlerininde kolayl\u0131kla tek bir servis \u00e7a\u011fr\u0131s\u0131 ile handle edebilmemizi sa\u011flamas\u0131d\u0131r.<\/p>\n

Nas\u0131l Kullan\u0131l\u0131r?<\/h2>\n

\"address-remote-facede\"<\/a><\/p>\n

Kullan\u0131m\u0131 yukar\u0131daki diyagramda\u00a0g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi asl\u0131nda olduk\u00e7a basit \u00f6rneklemi\u015f Martin Fowler. Buradaki tasar\u0131mda g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi Address Facade<\/strong>\u00a0tasar\u0131m\u0131, Address Domain Model<\/strong>‘inden “GetStreet”, “GetZip”, “GetCity” method’lar\u0131na tek tek servis \u00e7a\u011fr\u0131s\u0131 bulunulmas\u0131 yerine, Address Facade \u00fczerinden “GetAddressData” method’u ile bu \u00fc\u00e7 method sonucuna tek bir servis \u00e7a\u011fr\u0131s\u0131 arac\u0131l\u0131\u011f\u0131 ile\u00a0eri\u015filebilinmesini sa\u011flamaktad\u0131r. Bu sayede hem network \u00fczerindeki yo\u011fun trafik oran\u0131<\/strong> hemde sunucu taraf\u0131ndaki serialization<\/strong> maliyeti d\u00fc\u015f\u00fcr\u00fclm\u00fc\u015f olacakt\u0131r.<\/p>\n

Buradaki Address Facade<\/strong>\u00a0modeli\u00a0akl\u0131m\u0131z\u0131 Data Transfer Object<\/strong> (DTO) modeli ile\u00a0belki kar\u0131\u015ft\u0131rabilir. DTO modeli de i\u00e7erisinde ortak olan business’lar\u0131\u00a0encapsule ederek, katmanlar aras\u0131 data ge\u00e7irebilmektedir. Fakat DTO i\u00e7erisinde herhangi bir setter method<\/strong> bar\u0131nd\u0131rmamaktad\u0131r. Remote Facade deseninde ise setter<\/strong> i\u015flemler de dahil olmak \u00fczere, ayn\u0131 business’lar i\u00e7in bir arada yap\u0131labilmektedir.<\/p>\n

Peki derseniz\u00a0GOF pattern’leri aras\u0131nda bulunan Facade pattern’i ile aras\u0131ndaki fark\u00a0nedir derseniz? Ozaman \u015f\u00f6yle diyelim:<\/p>\n