{"id":37030,"date":"2019-10-31T22:15:23","date_gmt":"2019-10-31T19:15:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane\/"},"modified":"2019-10-31T22:15:23","modified_gmt":"2019-10-31T19:15:23","slug":"servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane","title":{"rendered":"Rrjeti sh\u00ebrbim, \"Plani i t\u00eb dh\u00ebnave\" dhe \"Plani i kontrollit\" (Service mesh data plane vs. control plane)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>P\u00ebrsh\u00ebndetje, Habr! Ju prezantoj p\u00ebrkthimin e artikullit <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.envoyproxy.io\/service-mesh-data-plane-vs-control-plane-2774e720f7fc\">\u00abPlaneja e kontrollit t\u00eb mesh-it t\u00eb sh\u00ebrbimeve\u00bb<\/a><\/noindex> autori <b>Matt Klein<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Rrjeti sh\u00ebrbim, &quot;Plani i t\u00eb dh\u00ebnave&quot; dhe &quot;Plani i kontrollit&quot; (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/487456689eb832f9e3845966cb0d85d4.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebt\u00eb her\u00eb, p\u00ebrshkrimi i t\u00eb dy componenteve t\u00eb mesh-it t\u00eb sh\u00ebrbimeve, planeve t\u00eb dh\u00ebnash dhe planeve t\u00eb kontrollit, m\u00eb dukej m\u00eb i qart\u00eb dhe interesant, e m\u00eb e r\u00ebnd\u00ebsishme, q\u00eb ndihmon n\u00eb kuptimin e \u00abA \u00ebsht\u00eb e nevojshme n\u00eb t\u00eb v\u00ebrtet\u00eb?\u00bb<\/p>\n<p>T\u00eb mendosh p\u00ebr mesh-in e sh\u00ebrbimeve (Service mesh) po b\u00ebhet gjithnj\u00eb e m\u00eb i popullarizuar gjat\u00eb dy viteve t\u00eb fundit (artikulli origjinal nga 10 tetori 2017), dhe numri i pjes\u00ebmarr\u00ebsve n\u00eb k\u00ebt\u00eb hap\u00ebsir\u00eb \u00ebsht\u00eb rritur, kam v\u00ebrejtur nj\u00eb rritje t\u00eb ngjashme t\u00eb konfuzionit midis t\u00ebr\u00eb komunitetit teknik n\u00eb lidhje me m\u00ebnyr\u00ebn e krahasimit dhe diferenciimit t\u00eb zgjidhjeve t\u00eb ndryshme.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nSituat\u00ebn mund ta p\u00ebrshkruajm\u00eb m\u00eb mir\u00eb me nj\u00eb seri tweet-esh q\u00eb kam shkruar n\u00eb korrik:<\/p>\n<blockquote><p>Konfuzioni n\u00eb lidhje me mesh-in e sh\u00ebrbimeve (service mesh) #1: Linkerd ~ = Nginx ~ = HAProxy ~ = Envoy. Asnj\u00ebra nga k\u00ebto nuk \u00ebsht\u00eb e barabart\u00eb me Istio. Istio \u00ebsht\u00eb di\u00e7ka krejt\u00ebsisht tjet\u00ebr. 1 \/<\/p><\/blockquote>\n<blockquote><p>T\u00eb parat jan\u00eb thjesht plane t\u00eb dh\u00ebnash (data planes). Ato vet\u00eb nuk b\u00ebjn\u00eb asgj\u00eb. Ato duhet t\u00eb konfigurohen p\u00ebr di\u00e7ka m\u00eb t\u00eb madhe. 2 \/<\/p><\/blockquote>\n<blockquote><p>Istio \u00ebsht\u00eb nj\u00eb shembull i nj\u00eb plani kontrolli (control plane), q\u00eb lidh pjes\u00ebt s\u00eb bashku. Ky \u00ebsht\u00eb nj\u00eb nivel tjet\u00ebr. \/fund<\/p><\/blockquote>\n<p>N\u00eb tweet-et e m\u00ebparshme p\u00ebrmenden disa projekte t\u00eb ndryshme (Linkerd, NGINX, HAProxy, Envoy dhe Istio), por m\u00eb e r\u00ebnd\u00ebsishmja, futen konceptet e p\u00ebrgjithshme t\u00eb planeve t\u00eb dh\u00ebnash (data plane), mesh-it t\u00eb sh\u00ebrbimeve (service mesh) dhe planeve t\u00eb kontrollit (control plane). N\u00eb k\u00ebt\u00eb post do t\u00eb heq nj\u00eb hap prapa dhe do t\u00eb shpjegoj \u00e7far\u00eb n\u00ebnkuptoj me termin \u00abplane t\u00eb dh\u00ebnash (data plane)\u00bb dhe \u00abplan kontrolli (control plane)\u00bb n\u00eb nj\u00eb nivel shum\u00eb t\u00eb lart\u00eb, dhe pastaj do t\u00eb shpjegoj se si k\u00ebto terma lidhen me projektet q\u00eb jan\u00eb p\u00ebrmendur n\u00eb tweet-et.<\/p>\n<h1>\u00c7far\u00eb \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb nj\u00eb mesh sh\u00ebrbimesh (What is a service mesh, really)?<\/h1>\n<p>\n<img decoding=\"async\" alt=\"Rrjeti sh\u00ebrbim, &quot;Plani i t\u00eb dh\u00ebnave&quot; dhe &quot;Plani i kontrollit&quot; (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/63c195aa9bcb7080f6924cecbff0fbc1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Figura 1: P\u00ebrshtypje e mesh-it t\u00eb sh\u00ebrbimeve (Service mesh overview)<\/b><\/p>\n<p><b>Figura 1<\/b> ilustron konceptin e mesh-it t\u00eb sh\u00ebrbimeve (service mesh) n\u00eb nivelin m\u00eb bazik. Ka kat\u00ebr klaster\u00eb sh\u00ebrbimesh (A-D). \u00c7do instanc\u00eb sh\u00ebrbimi \u00ebsht\u00eb e lidhur me nj\u00eb server proxy lokal. I gjith\u00eb trafi ky\u00e7 (HTTP, REST, gRPC, Redis, etj.) nga instancat e ve\u00e7anta t\u00eb aplikacionit d\u00ebrgohet p\u00ebrmes serverit proxy lokal n\u00eb klaster\u00ebt sh\u00ebrbimor\u00eb t\u00eb jasht\u00ebm p\u00ebrkat\u00ebs. K\u00ebshtu, instanca e aplikacionit nuk e di p\u00ebr rrjetin n\u00eb t\u00ebr\u00ebsi dhe njeh vet\u00ebm serverin e saj lokal proxy. N\u00eb fakt, rrjeti i sistemit t\u00eb distribuar \u00ebsht\u00eb hequr nga sh\u00ebrbimi.<\/p>\n<h1>Plani i t\u00eb dh\u00ebnave (Data plane)<\/h1>\n<p>\nN\u00eb mesh-in e sh\u00ebrbimeve (service mesh), serveri proxy i vendosur lokal p\u00ebr aplikacionin kryen k\u00ebto detyra:<\/p>\n<ul>\n<li> <b>Zbulesa e sh\u00ebrbimeve (Service discovery)<\/b>. Cilat sh\u00ebrbime\/funksione\/aplikacione jan\u00eb t\u00eb disponueshme p\u00ebr aplikacionin tuaj?<\/li>\n<li><b>Kontrolli i sh\u00ebndetit (Health checking)<\/b>. A jan\u00eb instancat e sh\u00ebrbimeve, t\u00eb rikthyera nga zbulesa e sh\u00ebrbimeve (service discovery), n\u00eb gjendje t\u00eb sh\u00ebndosh\u00eb dhe gati p\u00ebr t\u00eb pranuar trafik n\u00eb rrjet? Kjo mund t\u00eb p\u00ebrfshij\u00eb si kontroll aktiv (p.sh., verifikimi i p\u00ebrgjigjes \/ healthcheck), ashtu edhe t\u00eb pasiv (p.sh., duke p\u00ebrdorur 3 gabime 5xx rresht si nj\u00eb tregues t\u00eb gjendjes s\u00eb keqe t\u00eb sh\u00ebrbimit). <\/li>\n<li><b>Routimi (Routing)<\/b>. \u041f\u043e\u043b\u0443\u0447\u0438\u0432 \u043e\u0442 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 REST \u0437\u0430\u043f\u0440\u043e\u0441 \u043a &#171;\/foo&#187;, \u0432 \u043a\u0430\u043a\u043e\u0439 \u0441\u0435\u0440\u0432\u0438\u0441\u043d\u044b\u0439 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441? <\/li>\n<li> <b>Balancimi i ngarkes\u00ebs (Load balancing)<\/b>. Pas p\u00ebrzgjedhjes s\u00eb klasterit t\u00eb sh\u00ebrbimit gjat\u00eb rrug\u00ebs, n\u00eb cilin instanc\u00eb sh\u00ebrbimi duhet d\u00ebrguar k\u00ebrkesa? Me cilin afat? Me cilat parametra t\u00eb ndalimit t\u00eb qarkut (circuit breaking)? N\u00ebse k\u00ebrkesa d\u00ebshton, a duhet ta rip\u00ebrs\u00ebrisim at\u00eb?<\/li>\n<li> <b>Autentifikimi dhe autorizimi (Authentication and authorization)<\/b>. P\u00ebr k\u00ebrkesat e ardhshme, mund t\u00eb identifikohet\/autorizohet sh\u00ebrbimi thirr\u00ebs n\u00eb m\u00ebnyr\u00eb kriptografike p\u00ebrmes mTLS ose ndonj\u00eb mekanizmi tjet\u00ebr? N\u00ebse \u00ebsht\u00eb identifikuar\/autorizar, a i lejohet t\u00eb th\u00ebrras\u00eb operacionin (endpoint) n\u00eb sh\u00ebrbim ose duhet t\u00eb kthehet nj\u00eb p\u00ebrgjigje e paautorizuar?<\/li>\n<li> <b>V\u00ebzhgueshm\u00ebria (Observability)<\/b>. P\u00ebr secil\u00ebn k\u00ebrkes\u00eb, duhet t\u00eb gjenerohen t\u00eb dh\u00ebna t\u00eb detajuara statistikore, logje\/raporte dhe t\u00eb dh\u00ebna t\u00eb gjurmimit t\u00eb shp\u00ebrndar\u00eb, q\u00eb operator\u00ebt t\u00eb mund t\u00eb kuptojn\u00eb rrug\u00ebn e shp\u00ebrndar\u00eb t\u00eb trafik dhe problemet e zgjidhjes s\u00eb gabimeve nd\u00ebrsa ato ndodhin.<\/li>\n<\/ul>\n<p>\nP\u00ebr t\u00eb gjitha pikat e p\u00ebrmendura m\u00eb sip\u00ebr, p\u00ebrgjigjen e ka plani i t\u00eb dh\u00ebnave (data plane) n\u00eb mesh-in e sh\u00ebrbimeve (service mesh). N\u00eb thelb, proxy lokal p\u00ebr sh\u00ebrbimin (sidecar) \u00ebsht\u00eb plani i t\u00eb dh\u00ebnave (data plane). N\u00eb terma t\u00eb tjer\u00eb, plani i t\u00eb dh\u00ebnave (data plane) p\u00ebrgjigjet p\u00ebr transmetimin, d\u00ebrgimin dhe v\u00ebzhgimin e \u00e7do pakete rrjeti q\u00eb d\u00ebrgohet n\u00eb sh\u00ebrbim ose d\u00ebrgohet prej tij.<\/p>\n<h1>Plani i kontrollit (The control plane)<\/h1>\n<p>\n\u0421\u0435\u0442\u0435\u0432\u0430\u044f \u0430\u0431\u0441\u0442\u0440\u0430\u043a\u0446\u0438\u044f, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u0435\u0442 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0439 \u043f\u0440\u043e\u043a\u0441\u0438 \u0432 \u043f\u043b\u043e\u0441\u043a\u043e\u0441\u0442\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 (data plane), \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u043e\u043b\u0448\u0435\u0431\u043d\u043e\u0439 (?). \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043a\u0430\u043a \u043f\u0440\u043e\u043a\u0441\u0438-\u0441\u0435\u0440\u0432\u0435\u0440 \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0434\u0435\u043b\u0435 \u0443\u0437\u043d\u0430\u0435\u0442 \u043e \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0435 &#171;\/foo&#187; \u043a \u0441\u0435\u0440\u0432\u0438\u0441\u0443 B? \u041a\u0430\u043a \u0434\u0430\u043d\u043d\u044b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 (service discovery), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0437\u0430\u043f\u043e\u043b\u043d\u044f\u044e\u0442\u0441\u044f \u043f\u0440\u043e\u043a\u0441\u0438-\u0437\u0430\u043f\u0440\u043e\u0441\u0430\u043c\u0438, \u043c\u043e\u0433\u0443\u0442 \u0431\u044b\u0442\u044c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u044b? \u041a\u0430\u043a \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043d\u044b \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u044b \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438, \u0442\u0430\u0439\u043c\u0430\u0443\u0442\u0430 (timeout), \u043e\u0431\u0440\u044b\u0432\u0430 \u0446\u0435\u043f\u0438 (circuit breaking) \u0438 \u0442.\u0434.? \u041a\u0430\u043a \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u0441\u0438\u043d\u0435\u0433\u043e\/\u0437\u0435\u043b\u0435\u043d\u043e\u0433\u043e (blue\/green) \u043c\u0435\u0442\u043e\u0434\u0430 \u0438\u043b\u0438 \u043c\u0435\u0442\u043e\u0434\u0430 \u043f\u043e\u0441\u0442\u0435\u043f\u0435\u043d\u043d\u043e\u0433\u043e \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430 \u0442\u0440\u0430\u0444\u0438\u043a\u0430? \u041a\u0442\u043e \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u0435\u0442 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u044b \u043e\u0431\u0449\u0435\u0441\u0438\u0441\u0442\u0435\u043c\u043d\u043e\u0439 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0438 \u0430\u0432\u0442\u043e\u0440\u0438\u0437\u0430\u0446\u0438\u0438?<\/p>\n<p>T\u00eb gjitha \u00e7\u00ebshtjet e lartp\u00ebrmendura jan\u00eb n\u00ebn menaxhimin e nivelit t\u00eb kontrollit (control plane) t\u00eb rrjetit t\u00eb sh\u00ebrbimeve (service mesh). <i>Niveli i kontrollit (control plane) merr nj\u00eb grup proxy-esh t\u00eb izoluar,<a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sq\/server\/\"   title=\"servera\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1348\">servera<\/a> pa gjendje dhe i kthen ato n\u00eb nj\u00eb sistem t\u00eb shp\u00ebrndar\u00eb.<\/i>.<\/p>\n<p>Mendoj se arsyeja pse shum\u00eb teknolog\u00eb e gjejn\u00eb t\u00eb nd\u00ebrlikuar konceptin e ndar\u00eb t\u00eb nivelit t\u00eb t\u00eb dh\u00ebnave (data plane) dhe nivelit t\u00eb kontrollit (control plane) \u00ebsht\u00eb se niveli i t\u00eb dh\u00ebnave \u00ebsht\u00eb i njohur, nd\u00ebrsa niveli i kontrollit \u00ebsht\u00eb i huaj\/i paqart\u00eb. Ne kemi punuar p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb me ruter\u00eb dhe kalues fizik\u00eb rrjetesh. Ne e kuptojm\u00eb q\u00eb paketat\/k\u00ebrkesat duhet t\u00eb shkojn\u00eb nga pika A n\u00eb pik\u00ebn B, dhe se \u00e7far\u00eb mund t\u00eb p\u00ebrdorim p\u00ebr k\u00ebt\u00eb \u00ebsht\u00eb harduer dhe softuer. Brezi i ri i proxy-ve programore \u00ebsht\u00eb thjesht moda e instrumenteve q\u00eb kemi p\u00ebrdorur p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Rrjeti sh\u00ebrbim, &quot;Plani i t\u00eb dh\u00ebnave&quot; dhe &quot;Plani i kontrollit&quot; (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/1b512802777cbf1853c5c4f7f2f81d99.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Figura 2: Niveli i menaxhimit njer\u00ebzor (Human control plane)<\/b><\/p>\n<p>Megjithat\u00eb, ne kemi p\u00ebrdorur nivelet e kontrollit (control plane) p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, edhe pse shumica e operator\u00ebve t\u00eb rrjetit mund t\u00eb mos lidhen k\u00ebt\u00eb pjes\u00eb t\u00eb sistemit me ndonj\u00eb komponent teknologjik. Arsyeja p\u00ebr k\u00ebt\u00eb \u00ebsht\u00eb e thjesht\u00eb:<br \/>\n<b>Shumica e niveleve t\u00eb kontrollit (control plane) t\u00eb p\u00ebrdorura sot jan\u00eb... ne<\/b>.<\/p>\n<p>N\u00eb <b>n\u00eb figur\u00ebn 2<\/b> kam ilustruar at\u00eb q\u00eb e quaj \"Niveli i Menaxhimit Njer\u00ebzor (Human control plane)\". N\u00eb k\u00ebt\u00eb lloj implementimi, q\u00eb ndodhet ende shum\u00eb shpesh, operatori njer\u00ebzor, ndoshta me nj\u00eb humor t\u00eb keq, krijon konfiguracione statike \u2014 potencialisht, me ndihm\u00ebn e skripteve \u2014 dhe i implementon ato n\u00ebp\u00ebrmjet nj\u00eb procesi t\u00eb ve\u00e7ant\u00eb n\u00eb t\u00eb gjitha serverat proxy. M\u00eb pas, proxy-t fillojn\u00eb t\u00eb p\u00ebrdorin k\u00ebt\u00eb konfigurim dhe fillojn\u00eb t\u00eb trajtojn\u00eb nivelin e t\u00eb dh\u00ebnave (data plane) duke p\u00ebrdorur cil\u00ebsimet e azhurnuara.<\/p>\n<p><img decoding=\"async\" alt=\"Rrjeti sh\u00ebrbim, &quot;Plani i t\u00eb dh\u00ebnave&quot; dhe &quot;Plani i kontrollit&quot; (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/6b12429611475e0fc4dfa9f980704e16.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Figura 3: Niveli i avancuar i kontrollit t\u00eb rrjetit t\u00eb sh\u00ebrbimeve (Advanced service mesh control plane)<\/b><\/p>\n<p>N\u00eb <b>n\u00eb figur\u00ebn 3<\/b> \u00ebsht\u00eb ilustruar niveli \"i avancuar\" i kontrollit (control plane) t\u00eb rrjetit t\u00eb sh\u00ebrbimeve (service mesh). Ai p\u00ebrb\u00ebhet nga pjes\u00ebt e m\u00ebposhtme:<\/p>\n<ul>\n<li> <b>Njeriu (The human)<\/b>: Akoma ka nj\u00eb njeri (shpresoj, m\u00eb pak i m\u00ebrzitur) q\u00eb merr vendime n\u00eb nivel t\u00eb lart\u00eb p\u00ebr t\u00ebr\u00eb sistemin.<\/li>\n<li><b>Nd\u00ebrfaqja e p\u00ebrdoruesit t\u00eb nivelit t\u00eb kontrollit (Control plane UI)<\/b>: Njeriu nd\u00ebrvepron me ndonj\u00eb lloj nd\u00ebrfaqeje p\u00ebr t\u00eb menaxhuar sistemin. Kjo mund t\u00eb jet\u00eb nj\u00eb portal web, nj\u00eb aplikacion komand\u00eb (CLI) ose ndonj\u00eb nd\u00ebrfaqe tjet\u00ebr. Me an\u00eb t\u00eb nd\u00ebrfaqes, operatori ka qasje n\u00eb parametrat global\u00eb t\u00eb konfigurimit t\u00eb sistemit, si:\n<ul>\n<li>Menaxhimi i implementimit, blu\/jeshile (blue\/green) dhe\/ose me kalimin gradual t\u00eb trafikut <\/li>\n<li>Parametrat e autentifikimit dhe autorizimit <\/li>\n<li>\u0421\u043f\u0435\u0446\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0442\u0430\u0431\u043b\u0438\u0446\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438, \u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u043e\u0433\u0434\u0430 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 A \u0437\u0430\u043f\u0440\u0430\u0448\u0438\u0432\u0430\u0435\u0442 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e &#171;\/foo&#187;, \u0447\u0442\u043e \u043f\u0440\u043e\u0438\u0441\u0445\u043e\u0434\u0438\u0442 <\/li>\n<li>Cil\u00ebsimet e balancuesit t\u00eb ngarkes\u00ebs, p\u00ebr shembull, skadimet (timeouts), p\u00ebrpjekjet (retries), parametrat e thyerjes s\u00eb qarkut (circuit breaking) etj. <\/li>\n<\/ul>\n<\/li>\n<li> <b>Planifikuesi i ngarkesave (Workload scheduler)<\/b>: Sh\u00ebrbimet fillojn\u00eb n\u00eb infrastruktur\u00eb p\u00ebrmes nj\u00eb sistemi planifikimi\/orkestrimi t\u00eb caktuar, p\u00ebr shembull, Kubernetes ose Nomad. Planifikuesi \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr ngarkimin e sh\u00ebrbimit me serverin e tij lokal proxy.<\/li>\n<li> <b>Zbulimi i sh\u00ebrbimit (Service discovery)<\/b>. Kur planifikuesi aktivizon dhe ndalon instancat e sh\u00ebrbimit, ai raporton gjendjen e pun\u00ebs n\u00eb sistemin e zbulimit t\u00eb sh\u00ebrbimit.<\/li>\n<li> <b>API t\u00eb konfigurimit t\u00eb proxy-t lokal (Sidecar proxy configuration APIs) <\/b>: Proxy-t lokal t\u00ebrheqin dinamik gjendjen nga komponent\u00ebt e ndrysh\u00ebm t\u00eb sistemit sipas modelit \"fundosja n\u00eb fund\" (eventually consistent) pa nd\u00ebrhyrjen e operatorit. E gjith\u00eb sistemi, q\u00eb p\u00ebrb\u00ebhet nga t\u00eb gjitha instancat aktualisht t\u00eb aktivizuara t\u00eb sh\u00ebrbimeve dhe proxy-ve lokal, p\u00ebrfundimisht p\u00ebrcjell n\u00eb nj\u00eb ekosistem. API e nivelit universal t\u00eb t\u00eb dh\u00ebnave (data plane) n\u00eb Envoy \u00ebsht\u00eb nj\u00eb nga shembujt se si funksionon n\u00eb praktik\u00eb.<\/li>\n<\/ul>\n<p>\nN\u00eb thelb, q\u00ebllimi i planit t\u00eb kontrollit (control plane) \u00ebsht\u00eb t\u00eb vendos\u00eb politik\u00ebn q\u00eb n\u00eb fund do t\u00eb miratohet nga plani i t\u00eb dh\u00ebnave (data plane). Planet m\u00eb t\u00eb avancuara t\u00eb kontrollit (control plane) do t\u00eb largojn\u00eb m\u00eb shum\u00eb detaje t\u00eb disa sistemeve nga operatori dhe do t\u00eb k\u00ebrkojn\u00eb m\u00eb pak menaxhim manual, me kusht q\u00eb ato t\u00eb funksionojn\u00eb si\u00e7 duhet!..<\/p>\n<h1>Plani i t\u00eb dh\u00ebnave dhe plani i kontrollit. P\u00ebrmbledhje (Data plane vs. control plane summary)<\/h1>\n<p><\/p>\n<ul>\n<li> <b>Plani i t\u00eb dh\u00ebnave t\u00eb rrjetit t\u00eb sh\u00ebrbimit (Service mesh data plane)<\/b>: prek \u00e7do paket\u00eb \/ k\u00ebrkes\u00eb n\u00eb sistem. P\u00ebrcakton zbulimin e aplikacioneve \/ sh\u00ebrbimeve, kontrollin e funksionalitetit, rrug\u00ebzimin, shp\u00ebrndarjen e ngarkes\u00ebs, autentikimin \/ autorizimin dhe monitorimin.<\/li>\n<li> <b>Plani i kontrollit t\u00eb rrjetit t\u00eb sh\u00ebrbimit (Service mesh control plane)<\/b>: ofron politikat dhe konfigurimin p\u00ebr t\u00eb gjitha planet e t\u00eb dh\u00ebnave q\u00eb funksionojn\u00eb brenda rrjetit t\u00eb sh\u00ebrbimit. Nuk prek asnj\u00eb paket\u00eb \/ k\u00ebrkes\u00eb n\u00eb sistem. Plani i kontrollit e kthen t\u00eb gjitha planet e t\u00eb dh\u00ebnave n\u00eb nj\u00eb sistem t\u00eb shp\u00ebrndar\u00eb.<\/li>\n<\/ul>\n<p><\/p>\n<h1>Gjendja aktuale e projektit (Current project landscape)<\/h1>\n<p>\nPas shpjegimit t\u00eb m\u00ebsip\u00ebrm, le t\u00eb shikojm\u00eb gjendjen aktuale t\u00eb projektit \"rrjeti i sh\u00ebrbimeve (service mesh)\".<\/p>\n<ul>\n<li> <b>Planet e t\u00eb dh\u00ebnave (Data planes)<\/b>: Linkerd, NGINX, HAProxy, Envoy, Traefik<\/li>\n<li><b>Planet e kontrollit (Control planes)<\/b>: Istio, Nelson, SmartStack <\/li>\n<\/ul>\n<p>\nN\u00eb vend t\u00eb analizimit t\u00eb thelluar t\u00eb secilit nga zgjidhjet e lartp\u00ebrmendura, un\u00eb do t\u00eb ndalem shkurtimisht n\u00eb disa pika q\u00eb, sipas mendimit tim, shkaktojn\u00eb shumic\u00ebn e konfuzionit n\u00eb ekosistemin aktual.<\/p>\n<p>N\u00eb fillim t\u00eb vitit 2016, Linkerd ishte nj\u00eb nga proxy-t e par\u00eb t\u00eb planit t\u00eb t\u00eb dh\u00ebnave (data plane) p\u00ebr rrjetin e sh\u00ebrbimeve (service mesh) dhe b\u00ebri nj\u00eb pun\u00eb t\u00eb shk\u00eblqyer n\u00eb rritjen e vet\u00ebdijes dhe p\u00ebrqendrimit mbi modelin e projektimit \"rrjeti i sh\u00ebrbimeve\" (service mesh). Rreth 6 muaj m\u00eb pas, Envoy i bashk\u00ebngjiti Linkerd (ndon\u00ebse kishte punuar n\u00eb Lyft q\u00eb nga fundi i vitit 2015). Linkerd dhe Envoy jan\u00eb dy projekte q\u00eb p\u00ebrmenden shpesh n\u00eb diskutimet mbi rrjetet e sh\u00ebrbimeve (service mesh).<\/p>\n<p>Istio u shpall n\u00eb maj 2017. Q\u00ebllimet e projektit Istio jan\u00eb t\u00eb ngjashme me planet e zgjeruara t\u00eb kontrollit (control plane) q\u00eb jan\u00eb treguar n\u00eb <b>n\u00eb figur\u00ebn 3<\/b>. Envoy p\u00ebr Istio \u00ebsht\u00eb proxy \"p\u00ebr default\". K\u00ebshtu, Istio \u00ebsht\u00eb plani i kontrollit (control plane), nd\u00ebrsa Envoy \u00ebsht\u00eb plani i t\u00eb dh\u00ebnave (data plane). N\u00eb nj\u00eb koh\u00eb shum\u00eb t\u00eb shkurt\u00ebr, Istio shkaktoi shum\u00eb zhurm\u00eb, dhe planet e tjera t\u00eb t\u00eb dh\u00ebnave (data plane) filluan integrimin si z\u00ebvend\u00ebs t\u00eb Envoy (dhe Linkerd dhe NGINX kan\u00eb demonstruar integrimin me Istio). Fakti q\u00eb n\u00eb nj\u00eb plan t\u00eb kontrollit (control plane) mund t\u00eb p\u00ebrdoren disa plane t\u00eb t\u00eb dh\u00ebnave (data plane) tregon se plani i kontrollit (control plane) dhe plani i t\u00eb dh\u00ebnave (data plane) nuk jan\u00eb domosdoshm\u00ebrisht t\u00eb lidhur ngusht\u00eb. Nj\u00eb API si API-universali i planit t\u00eb t\u00eb dh\u00ebnave (data plane) Envoy mund t\u00eb formoj\u00eb nj\u00eb ur\u00eb midis dy pjes\u00ebve t\u00eb sistemit.<\/p>\n<p>Nelson dhe SmartStack ndihmojn\u00eb p\u00ebr t\u00eb ilustruar m\u00eb tej ndarjen e planit t\u00eb kontrollit (control plane) dhe planit t\u00eb t\u00eb dh\u00ebnave (data plane). Nelson p\u00ebrdor Envoy si proxy-n\u00eb e tij dhe nd\u00ebrton nj\u00eb plan t\u00eb besuesh\u00ebm t\u00eb kontrollit (control plane) t\u00eb rrjetit t\u00eb sh\u00ebrbimit (service mesh) mbi baz\u00ebn e stack-ut t\u00eb HashiCorp, dmth. Nomad etj. SmartStack \u00ebsht\u00eb b\u00ebr\u00eb, ndoshta, i pari nga vala e re e rrjeteve t\u00eb sh\u00ebrbimeve (service mesh). SmartStack formon nj\u00eb plan t\u00eb kontrollit (control plane) rreth HAProxy ose NGINX, duke demonstruar mund\u00ebsin\u00eb e lirshm\u00ebris\u00eb s\u00eb planit t\u00eb kontrollit (control plane) t\u00eb rrjetit t\u00eb sh\u00ebrbimit (service mesh) dhe planit t\u00eb t\u00eb dh\u00ebnave (data plane).<\/p>\n<p>Arkitektura mikrosh\u00ebrbimit me rrjetin e sh\u00ebrbimeve (service mesh) po t\u00ebrheq gjithnj\u00eb e m\u00eb shum\u00eb v\u00ebmendje (me t\u00eb drejt\u00eb!), dhe gjithnj\u00eb e m\u00eb shum\u00eb projekte dhe shit\u00ebs po fillojn\u00eb t\u00eb punojn\u00eb n\u00eb k\u00ebt\u00eb drejtim. N\u00eb vitet n\u00eb vijim, ne do t\u00eb shohim shum\u00eb inovacione si n\u00eb planet e t\u00eb dh\u00ebnave (data plane) ashtu edhe n\u00eb planet e kontrollit (control plane), si dhe p\u00ebrzierje t\u00eb m\u00ebtejshme t\u00eb komponent\u00ebve t\u00eb ndrysh\u00ebm. N\u00eb fund t\u00eb fundit, arkitektura mikrosh\u00ebrbimit duhet t\u00eb b\u00ebhet m\u00eb e qart\u00eb dhe m\u00eb magjike (?) p\u00ebr operatorin.<br \/>\nShpresoj, gjithnj\u00eb e m\u00eb pak e irrituar.<\/p>\n<h1>Pikat kryesore (Key takeaways)<\/h1>\n<p><\/p>\n<ul>\n<li> Rrjeti i sh\u00ebrbimeve (service mesh) p\u00ebrb\u00ebhet nga dy pjes\u00eb t\u00eb ndryshme: plani i t\u00eb dh\u00ebnave (data plane) dhe plani i kontrollit (control plane). T\u00eb dy komponent\u00ebt jan\u00eb t\u00eb domosdosh\u00ebm, dhe pa ta sistemi nuk do t\u00eb funksionoj\u00eb.<\/li>\n<li>T\u00eb gjith\u00eb jan\u00eb t\u00eb njohur me planin e kontrollit (control plane), dhe p\u00ebr momentin plani i kontrollit (control plane) mund t\u00eb jeni ju! <\/li>\n<li>T\u00eb gjith\u00eb planet e t\u00eb dh\u00ebnave (data plane) konkurrojn\u00eb midis tyre p\u00ebr funksionalitet, performanc\u00eb, konfigurueshm\u00ebri dhe zgjerueshm\u00ebri. <\/li>\n<li> T\u00eb gjith\u00eb planet e kontrollit (control plane) konkurrojn\u00eb midis tyre p\u00ebr funksionalitet, konfigurueshm\u00ebri, zgjerueshm\u00ebri dhe leht\u00ebsin\u00eb e p\u00ebrdorimit.<\/li>\n<li>Nj\u00eb plan kontrolli (control plane) mund t\u00eb p\u00ebrmbaj\u00eb abstraksionet dhe API-t\u00eb e duhura, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mund\u00ebsoj\u00eb p\u00ebrdorimin e disa planeve t\u00eb t\u00eb dh\u00ebnave (data plane). <\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/462699\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e \u0432\u0430\u0448\u0435\u043c\u0443 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u00abService mesh data plane vs control plane\u00bb \u0430\u0432\u0442\u043e\u0440\u0430 Matt Klein. \u0412 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u00ab\u0437\u0430\u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0438 \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u043e\u0441\u044c\u00bb \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043e\u0431\u043e\u0438\u0445 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 service mesh, data plane \u0438 control plane. \u042d\u0442\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043c\u043d\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0441\u0430\u043c\u044b\u043c \u043f\u043e\u043d\u044f\u0442\u043d\u044b\u043c \u0438 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u043c, \u0430 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u043f\u043e\u0434\u0432\u043e\u0434\u044f\u0449\u0438\u043c \u043a \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u00ab\u0410 \u043d\u0443\u0436\u043d\u043e \u043b\u0438 \u043e\u043d\u043e \u0432\u043e\u043e\u0431\u0449\u0435?\u00bb. \u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0438\u0434\u0435\u044f \u00ab\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u043e\u0439 \u0441\u0435\u0442\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27757,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37030","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e \u0432\u0430\u0448\u0435\u043c\u0443 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u00abService mesh data plane vs control plane\u00bb \u0430\u0432\u0442\u043e\u0440\u0430 Matt Klein. \u0412 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u00ab\u0437\u0430\u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0438 \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u043e\u0441\u044c\u00bb \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043e\u0431\u043e\u0438\u0445 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 service mesh, data plane \u0438 control plane. \u042d\u0442\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043c\u043d\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0441\u0430\u043c\u044b\u043c \u043f\u043e\u043d\u044f\u0442\u043d\u044b\u043c \u0438 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u043c, \u0430 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u043f\u043e\u0434\u0432\u043e\u0434\u044f\u0449\u0438\u043c \u043a \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u00ab\u0410 \u043d\u0443\u0436\u043d\u043e \u043b\u0438 \u043e\u043d\u043e \u0432\u043e\u043e\u0431\u0449\u0435?\u00bb. \u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0438\u0434\u0435\u044f \u00ab\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u043e\u0439 \u0441\u0435\u0442\u0438\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u0430\u044f \u0441\u0435\u0442\u044c, \u00ab\u041f\u043b\u043e\u0441\u043a\u043e\u0441\u0442\u044c \u0434\u0430\u043d\u043d\u044b\u0445\u00bb \u0438 \u00ab\u041f\u043b\u043e\u0441\u043a\u043e\u0441\u0442\u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f\u00bb (Service mesh data plane vs. control plane) | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e \u0432\u0430\u0448\u0435\u043c\u0443 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u00abService mesh data plane vs control plane\u00bb \u0430\u0432\u0442\u043e\u0440\u0430 Matt Klein. \u0412 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u00ab\u0437\u0430\u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0438 \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u043e\u0441\u044c\u00bb \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043e\u0431\u043e\u0438\u0445 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 service mesh, data plane \u0438 control plane. \u042d\u0442\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043c\u043d\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0441\u0430\u043c\u044b\u043c \u043f\u043e\u043d\u044f\u0442\u043d\u044b\u043c \u0438 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u043c, \u0430 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u043f\u043e\u0434\u0432\u043e\u0434\u044f\u0449\u0438\u043c \u043a \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u00ab\u0410 \u043d\u0443\u0436\u043d\u043e \u043b\u0438 \u043e\u043d\u043e \u0432\u043e\u043e\u0431\u0449\u0435?\u00bb. \u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0438\u0434\u0435\u044f \u00ab\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u043e\u0439 \u0441\u0435\u0442\u0438\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:15:23+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:15:23+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Rrjeti i Sh\u00ebrbimeve, \u00abPlani i t\u00eb Dh\u00ebnave\u00bb dhe \u00abPlani i Kontrollit\u00bb (Service mesh data plane vs. control plane) | ProHoster","description":"P\u00ebrsh\u00ebndetje, Habr! Po ju paraqes p\u00ebrkthimin e artikullit \u00abService mesh data plane vs control plane\u00bb nga autor Matt Klein. K\u00ebt\u00eb her\u00eb, pata d\u00ebshir\u00eb t\u00eb p\u00ebrkthej p\u00ebrshkrimin e t\u00eb dy komponent\u00ebve t\u00eb service mesh, data plane dhe control plane. Ky p\u00ebrshkrim m\u00eb duket m\u00eb i qart\u00eb dhe m\u00eb interesante, dhe m\u00eb s\u00eb r\u00ebnd\u00ebsishmi, e \u00e7on n\u00eb kuptimin \u00abA \u00ebsht\u00eb e nevojshme v\u00ebrtet?\u00bb. Sepse ideja e \u00abRrjetit t\u00eb Sh\u00ebrbimeve\u00bb","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u0430\u044f \u0441\u0435\u0442\u044c, \u00ab\u041f\u043b\u043e\u0441\u043a\u043e\u0441\u0442\u044c \u0434\u0430\u043d\u043d\u044b\u0445\u00bb \u0438 \u00ab\u041f\u043b\u043e\u0441\u043a\u043e\u0441\u0442\u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f\u00bb (Service mesh data plane vs. control plane) | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e \u0432\u0430\u0448\u0435\u043c\u0443 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u00abService mesh data plane vs control plane\u00bb \u0430\u0432\u0442\u043e\u0440\u0430 Matt Klein. \u0412 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u00ab\u0437\u0430\u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0438 \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u043e\u0441\u044c\u00bb \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043e\u0431\u043e\u0438\u0445 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 service mesh, data plane \u0438 control plane. \u042d\u0442\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u043c\u043d\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0441\u0430\u043c\u044b\u043c \u043f\u043e\u043d\u044f\u0442\u043d\u044b\u043c \u0438 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u043c, \u0430 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u043f\u043e\u0434\u0432\u043e\u0434\u044f\u0449\u0438\u043c \u043a \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044e \u00ab\u0410 \u043d\u0443\u0436\u043d\u043e \u043b\u0438 \u043e\u043d\u043e \u0432\u043e\u043e\u0431\u0449\u0435?\u00bb. \u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0438\u0434\u0435\u044f \u00ab\u0421\u0435\u0440\u0432\u0438\u0441\u043d\u043e\u0439 \u0441\u0435\u0442\u0438","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:15:23+00:00","article:modified_time":"2019-10-31T19:15:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37030","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-09 17:07:03","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:34:25","updated":"2026-02-09 17:07:03","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=37030"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37030\/revisions"}],"predecessor-version":[{"id":158592,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37030\/revisions\/158592"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27757"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}