<\/a><\/noindex>
N\u00eb nivelin e proxy (data plane):<\/i><\/p>\n\nCaktimi dhe shp\u00ebrndarja e politikave t\u00eb rrug\u00ebzimit dhe balancimit t\u00eb trafikut\n<\/li>\n Shp\u00ebrndarja e \u00e7el\u00ebsave, certifikatave, token\u00ebve\n<\/li>\n Grumbullimi i telemetris\u00eb, form\u00ebsimi i metrikave t\u00eb monitorimit\n<\/li>\n Integrimi me infrastruktur\u00ebn e siguris\u00eb dhe monitorimit\n<\/li>\n<\/ul>\n\nN\u00eb nivelin e kontrollit (control plane):<\/i><\/p>\n\nZbatimi i politikave t\u00eb rrug\u00ebzimit dhe balancimit t\u00eb trafikut\n<\/li>\n Menaxhimi i rip\u00ebrs\u00ebritjeve dhe koh\u00ebve t\u00eb pritjes, identifikimi i node-ve \u00abt\u00eb vdekur\u00bb (circuit breaking), menaxhimi i situatave t\u00eb d\u00ebshtuara (injecting faults) dhe sigurimi i q\u00ebndrueshm\u00ebris\u00eb (resilience) t\u00eb sh\u00ebrbimeve p\u00ebrmes mekanizmave t\u00eb tjer\u00eb\n<\/li>\n Autentifikimi\/autoriza e thirrjeve\n<\/li>\n R\u00ebnia e metrikave (observability)\n<\/li>\n<\/ul>\n\nRrethi i p\u00ebrdoruesve t\u00eb interesuar p\u00ebr zhvillimin e k\u00ebsaj teknologjie \u00ebsht\u00eb shum\u00eb i gjer\u00eb \u2014 nga startupet e vogla deri te korporatat e m\u00ebdha t\u00eb internetit, p\u00ebr shembull, PayPal.<\/p>\n
P\u00ebr \u00e7far\u00eb \u00ebsht\u00eb e nevojshme Service Mesh n\u00eb sektorin korporativ<\/h2>\n \nP\u00ebrdorimi i Service Mesh sjell shum\u00eb p\u00ebrfitime t\u00eb dukshme. S\u00eb pari, \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme p\u00ebr zhvilluesit: p\u00ebr t\u00eb shkruar kodin shfaqet nj\u00eb platform\u00eb teknologjike<\/i>, e cila e thjeshton n\u00eb m\u00ebnyr\u00eb t\u00eb ndjeshme integrimin n\u00eb infrastruktur\u00ebn cloud p\u00ebr shkak se shtresa e transportit \u00ebsht\u00eb plot\u00ebsisht e izoluar nga logjika aplikative.<\/p>\n
P\u00ebr m\u00eb tep\u00ebr, Service Mesh thjeshton marr\u00ebdh\u00ebniet midis ofruesve dhe konsumator\u00ebve.<\/i> Sot bler\u00ebsit dhe konsumator\u00ebt e API-ve \u00ebsht\u00eb shum\u00eb m\u00eb e leht\u00eb t\u00eb dyja pal\u00ebt t\u00eb arrijn\u00eb marr\u00ebveshje p\u00ebr \u0438\u043d\u0442\u0435\u0440\u0444e rezultatet dhe kontratat vet\u00eb, pa nevoj\u00ebn p\u00ebr nj\u00eb nd\u00ebrmjet\u00ebs t\u00eb specializuar integrues dhe arbit\u00ebr \u2013 autobusin e sh\u00ebrbimeve t\u00eb korporatave. Ky qasje ka nj\u00eb ndikim t\u00eb r\u00ebnd\u00ebsish\u00ebm n\u00eb dy tregues. Rritet shpejt\u00ebsia e prezantimit t\u00eb funksionaliteteve t\u00eb reja n\u00eb treg (koha p\u00ebr n\u00eb treg), por kjo rrit koston e zgjidhjes, pasi integrimi duhet t\u00eb b\u00ebhet nga vet\u00eb p\u00ebrdoruesi. P\u00ebrdorimi i Service Mesh nga ekipet e zhvillimit t\u00eb funksionaliteteve t\u00eb biznesit lejon ruajtjen e balansit k\u00ebtu. N\u00eb p\u00ebrfundim, ofruesit e API-ve mund t\u00eb p\u00ebrqendrohen ekskluzivisht n\u00eb komponentin aplikativ t\u00eb sh\u00ebrbimit t\u00eb tyre dhe thjesht ta publikojn\u00eb at\u00eb n\u00eb Service Mesh \u2013 API menj\u00ebher\u00eb do t\u00eb b\u00ebhet i disponuesh\u00ebm p\u00ebr t\u00eb gjith\u00eb klient\u00ebt, dhe cil\u00ebsia e integrimit do t\u00eb jet\u00eb gati p\u00ebr prodhim dhe nuk do t\u00eb k\u00ebrkoj\u00eb asnj\u00eb rresht shtes\u00eb kodi.<\/p>\n
P\u00ebrfitimi tjet\u00ebr \u00ebsht\u00eb se zhvilluesi, duke p\u00ebrdorur Service Mesh, p\u00ebrqendrohet ekskluzivisht n\u00eb funksionalitetin e biznesit<\/i> \u2014 n\u00eb produktin dhe jo n\u00eb komponentin teknologjik t\u00eb sh\u00ebrbimit t\u00eb tij. P\u00ebr shembull, tani nuk \u00ebsht\u00eb e nevojshme t\u00eb mendoni se n\u00eb nj\u00eb situat\u00eb ku sh\u00ebrbimi do t\u00eb thirret p\u00ebrmes rrjetit, mund t\u00eb ndodhi nj\u00eb nd\u00ebrprerje e lidhjes. P\u00ebr m\u00eb tep\u00ebr, Service Mesh ndihmon n\u00eb balancimin e trafikut midis kopjeve t\u00eb nj\u00eb sh\u00ebrbimi t\u00eb nj\u00ebjt\u00eb: n\u00ebse nj\u00eb nga kopjet \"vdes\", sistemi do t\u00eb kaloj\u00eb t\u00eb gjith\u00eb trafikun n\u00eb kopjet e mbetura aktive. <\/p>\n
Service Mesh <\/i>\u2014 \u00ebsht\u00eb nj\u00eb themel i mir\u00eb p\u00ebr krijimin e aplikacioneve t\u00eb shp\u00ebrndara<\/i>, e cila fsheh nga klienti detajet e siguris\u00eb p\u00ebr thirrjet e sh\u00ebrbimeve t\u00eb tij si nga brenda ashtu edhe nga jasht\u00eb. T\u00eb gjitha aplikacionet q\u00eb p\u00ebrdorin Service Mesh jan\u00eb t\u00eb izoluara n\u00eb nivelin transportues nga rrjeti dhe nj\u00ebra-tjetra: nuk ka asnj\u00eb lidhje midis tyre. K\u00ebtu, zhvilluesi merr kontroll t\u00eb plot\u00eb mbi sh\u00ebrbimet e tij.<\/p>\n
Nuk mund t\u00eb injorohet se p\u00ebrdit\u00ebsimi i aplikacioneve t\u00eb shp\u00ebrndara n\u00eb nj\u00eb ambient ku p\u00ebrdoret Service Mesh b\u00ebhet m\u00eb i leht\u00eb.<\/i> P\u00ebr shembull, implementimi blue\/green, ku dy mjedise aplikacioni jan\u00eb t\u00eb disponueshme p\u00ebr instalim, nj\u00ebra prej t\u00eb cilave nuk p\u00ebrdit\u00ebsohet dhe mbetet n\u00eb modalitetin prit\u00ebs. Roli i rikthimit n\u00eb versionin e m\u00ebparsh\u00ebm n\u00eb rast t\u00eb nj\u00eb l\u00ebshimi t\u00eb d\u00ebshtuar luhet n\u00eb m\u00ebnyr\u00eb t\u00eb shk\u00eblqyer nga Service Mesh.. <\/i>P\u00ebr testimin e versionit t\u00eb ri mund t\u00eb p\u00ebrdoret gjithashtu l\u00ebshimi kanarin\u00eb <\/i>\u2014 t\u00eb kaloni n\u00eb versionin e ri vet\u00ebm 10% t\u00eb trafikut ose k\u00ebrkesave nga grupi pilot i klient\u00ebve. Trafiku kryesor shkon n\u00eb versionin e vjet\u00ebr, nuk ka asnj\u00eb nd\u00ebrprerje.<\/p>\n
Po ashtu Service Mesh na jep kontrollin SLA n\u00eb koh\u00eb reale<\/i>. Sistemi i proksive t\u00eb shp\u00ebrndara nuk do ta lejoj\u00eb sh\u00ebrbimin t\u00eb d\u00ebshtoj\u00eb kur ndonj\u00eb nga klient\u00ebt tejkalon kuot\u00ebn e dh\u00ebn\u00eb. N\u00ebse kapaciteti p\u00ebr API \u00ebsht\u00eb i kufizuar, askush nuk do t\u00eb mund ta sulmoj\u00eb me nj\u00eb num\u00ebr t\u00eb madh transaksionesh: Service Mesh q\u00ebndron p\u00ebrpara sh\u00ebrbimit dhe nuk lejon trafik t\u00eb tep\u00ebrt. Ai thjesht do t\u00eb filtronte n\u00eb nivelin e integrimit, nd\u00ebrsa sh\u00ebrbimet vet\u00eb do t\u00eb vazhdojn\u00eb t\u00eb funksionojn\u00eb pa e v\u00ebn\u00eb re k\u00ebt\u00eb.<\/p>\n
N\u00ebse nj\u00eb kompani d\u00ebshiron t\u00eb reduktoj\u00eb shpenzimet p\u00ebr zhvillimin e zgjidhjeve integruese, Service Mesh gjithashtu ndihmon: n\u00eb versionin e tij open-source mund t\u00eb kaloni nga produktet komerciale.<\/i>. Sh\u00ebrbimi yn\u00eb Enterprise Service Mesh bazohet n\u00eb versionin open-source t\u00eb Service Mesh. <\/p>\n
Nj\u00eb tjet\u00ebr avantazh \u2014 prania e nj\u00eb grupi t\u00eb plot\u00eb sh\u00ebrbimesh integruese<\/i>. Duke qen\u00eb se e gjith\u00eb integrimi nd\u00ebrtohet p\u00ebrmes k\u00ebtij shtrese nd\u00ebrmjet\u00ebse, ne mund t\u00eb menaxhojm\u00eb t\u00eb gjith\u00eb trafikun e integrimit dhe lidhjet midis aplikacioneve q\u00eb formojn\u00eb thelbin e biznesit t\u00eb kompanis\u00eb. Kjo \u00ebsht\u00eb shum\u00eb e dobishme.<\/p>\n
Dhe n\u00eb fund Service Mesh inkurajon kompanin\u00eb drejt kalimit n\u00eb nj\u00eb infrastruktur\u00eb dinamike.<\/i> Tani tani po shikojn\u00eb drejt konteinerizimit. Nd\u00ebrprerja e monolitit n\u00eb mikrosh\u00ebrbime dhe implementimi i t\u00eb gjitha k\u00ebtyre \u00ebsht\u00eb nj\u00eb tem\u00eb q\u00eb \u00ebsht\u00eb n\u00eb rritje. Por kur p\u00ebrpiqesh t\u00eb transferosh nj\u00eb sistem, i cili \u00ebsht\u00eb tashm\u00eb shum\u00eb vite n\u00eb prodhim, p\u00ebr nj\u00eb platform\u00eb t\u00eb re, menj\u00ebher\u00eb p\u00ebrballesh me nj\u00eb s\u00ebr\u00eb problemesh: t'i fut\u00ebsh t\u00eb gjitha k\u00ebto n\u00eb kontejner\u00eb dhe t'i vendos\u00ebsh n\u00eb platform\u00eb nuk \u00ebsht\u00eb e leht\u00eb. Implementimi, sinkronizimi dhe nd\u00ebrveprimi i k\u00ebtyre komponent\u00ebve t\u00eb shp\u00ebrndar\u00eb jan\u00eb nj\u00eb tem\u00eb tjet\u00ebr shum\u00eb e nd\u00ebrlikuar. Si do t\u00eb komunikojn\u00eb ata mes tyre? A do t\u00eb ket\u00eb ndonj\u00eb d\u00ebshtim n\u00eb zinxhir? Service Mesh lejon t\u00eb zgjidh\u00ebsh pjes\u00ebrisht k\u00ebto probleme dhe leht\u00ebson migrimin nga arkitektura e vjet\u00ebr n\u00eb t\u00eb re duke e b\u00ebr\u00eb t\u00eb mundur q\u00eb logjika e shk\u00ebmbimit t\u00eb rrjeteve t\u00eb harrohet.<\/p>\nPse \u00ebsht\u00eb e nevojshme personalizimi i Service Mesh<\/h2>\n
\nN\u00eb kompanin\u00eb ton\u00eb bashkohen qindra sisteme dhe module, dhe runtime \u00ebsht\u00eb shum\u00eb i ngarkuar. Prandaj, nj\u00eb model i thjesht\u00eb, ku nj\u00eb sistem th\u00ebrret nj\u00eb tjet\u00ebr dhe merr nj\u00eb p\u00ebrgjigje, nuk \u00ebsht\u00eb i mjaftuesh\u00ebm, sepse n\u00eb prodhim duam m\u00eb shum\u00eb. \u00c7far\u00eb tjet\u00ebr na nevojitet nga Service Mesh-i korporativ? <\/p>\n
Sh\u00ebrbimi i p\u00ebrpunimit t\u00eb ngjarjeve<\/h3>\n \nImagjinoni se na duhet t\u00eb krijojm\u00eb p\u00ebrpunimin e ngjarjeve n\u00eb koh\u00eb reale \u2014 nj\u00eb sistem q\u00eb analizon veprimet e klientit n\u00eb koh\u00eb reale dhe mund t'i b\u00ebj\u00eb menj\u00ebher\u00eb nj\u00eb propozim t\u00eb p\u00ebrshtatsh\u00ebm. P\u00ebr t\u00eb realizuar nj\u00eb funksionalitet t\u00eb till\u00eb, p\u00ebrdoret nj\u00eb model arkitektonik t\u00eb quajtur arkitektura e bazuar n\u00eb ngjarje (EDA)<\/i>. Asnj\u00eb nga Mesh-at e Aktualizuar t\u00eb Sh\u00ebrbimeve nuk e mb\u00ebshtet natyrsh\u00ebm k\u00ebt\u00eb model, dhe kjo \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme, ve\u00e7an\u00ebrisht p\u00ebr bankat!<\/p>\n
\u00cbsht\u00eb mjaft e \u00e7uditshme q\u00eb t\u00eb gjitha versionet e Mesh-it t\u00eb Sh\u00ebrbimeve mb\u00ebshtetin thirrjen e larg\u00ebt Remote Procedure Call (RPC), nd\u00ebrsa me EDA nuk jan\u00eb n\u00eb harmoni. Sepse Mesh-i i Sh\u00ebrbimeve \u00ebsht\u00eb nj\u00eb lloj integrimi t\u00eb shp\u00ebrndar\u00eb modern, nd\u00ebrsa EDA \u00ebsht\u00eb nj\u00eb model arkitektonik shum\u00eb aktual q\u00eb lejon krijimin e gj\u00ebrave unike n\u00eb p\u00ebrvoj\u00ebn e klientit.<\/p>\n
Mesh-i yn\u00eb i Sh\u00ebrbimeve Nd\u00ebrmarr\u00ebse duhet t\u00eb zgjidh\u00eb k\u00ebt\u00eb problem. P\u00ebr m\u00eb tep\u00ebr, ne duam t\u00eb shohim n\u00eb t\u00eb implementimin e dor\u00ebzimit t\u00eb garantuar, p\u00ebrpunimin e rrjedhsh\u00ebm dhe t\u00eb kompleks t\u00eb ngjarjeve duke p\u00ebrdorur filtre dhe template t\u00eb ndryshme.<\/p>\n
Sh\u00ebrbimi i transferimit t\u00eb skedareve<\/h3>\n \nP\u00ebrve\u00e7 EDA-s, do t\u00eb ishte mir\u00eb t\u00eb kishte mund\u00ebsin\u00eb p\u00ebr t\u00eb transferuar skedar\u00eb: n\u00eb nivelin Enterprise shpesh vet\u00ebm integrimi i skedar\u00ebve \u00ebsht\u00eb i mundur. N\u00eb ve\u00e7anti, p\u00ebrdoret modeli arkitekturor ETL (Extract, Transform, Load \u2014 'nxjerrja, transformimi, ngarkimi'). N\u00eb t\u00eb, zakonisht tregohet se t\u00eb gjith\u00eb shk\u00ebmbejn\u00eb ekskluzivisht skedar\u00eb: p\u00ebrdoren t\u00eb dh\u00ebna t\u00eb m\u00ebdha, t\u00eb cilat nuk jan\u00eb t\u00eb arsyeshme t\u00eb d\u00ebrgohen me k\u00ebrkesa t\u00eb ve\u00e7anta. Mund\u00ebsia e mb\u00ebshtetjes natyrale p\u00ebr transferimin e skedar\u00ebve n\u00eb Enterprise Service Mesh ofron fleksibilitetin e nevojsh\u00ebm p\u00ebr biznesin.<\/p>\n
Sh\u00ebrbimi i orkestrimit<\/h3>\n \nN\u00eb organizatat e m\u00ebdha, pothuajse gjithmon\u00eb ka ekipe t\u00eb ndryshme q\u00eb krijojn\u00eb produkte t\u00eb ndryshme. P\u00ebr shembull, n\u00eb nj\u00eb bank\u00eb, disa ekipe punojn\u00eb me depozitat, nd\u00ebrsa t\u00eb tjera me produktet e kreditit, dhe raste t\u00eb tilla jan\u00eb mjaft t\u00eb shumta. K\u00ebto jan\u00eb njer\u00ebz t\u00eb ndrysh\u00ebm, ekipe t\u00eb ndryshme, q\u00eb krijojn\u00eb produktet e tyre, zhvillojn\u00eb API-t\u00eb e tyre dhe i ofrojn\u00eb ato p\u00ebr t\u00eb tjer\u00ebt. Shpesh shfaqet nevoja p\u00ebr t\u00eb kompozuar k\u00ebto sh\u00ebrbime, si dhe p\u00ebr t\u00eb implementuar logjik\u00ebn komplekse t\u00eb thirrjes se nj\u00eb grupi API. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem, nevojitet nj\u00eb zgjidhje n\u00eb nivelin e integrimit, e cila do t\u00eb lejoj\u00eb thjeshtimin e gjith\u00eb k\u00ebsaj logjike kompozitore (thirrja e disa API-ve, p\u00ebrshkrimi i rrug\u00ebs s\u00eb k\u00ebrkesave, etj.). Ky \u00ebsht\u00eb sh\u00ebrbimi i orkestrimit n\u00eb Enterprise Service Mesh.<\/p>\n
AI dhe ML<\/h3>\n \nKur mikrosh\u00ebrbimet komunikojn\u00eb p\u00ebrmes nj\u00eb shtrese integruese, Service Mesh natyrsh\u00ebm di gjith\u00e7ka n\u00eb lidhje me thirrjet e \u00e7do sh\u00ebrbimi. Ne mbledhim telemetri: kush thirri kush, kur, sa gjat\u00eb, sa her\u00eb dhe k\u00ebshtu me radh\u00eb. Kur k\u00ebta sh\u00ebrbime jan\u00eb qindra mij\u00ebra, dhe thirrjet \u2014 miliarda, t\u00eb gjitha k\u00ebto grumbullohen dhe formojn\u00eb Big Data. K\u00ebto t\u00eb dh\u00ebna mund t\u00eb analizohen p\u00ebrmes mjeteve t\u00eb AI, machine learning dhe t\u00eb tjera, dhe m\u00eb pas mund t\u00eb b\u00ebhet di\u00e7ka e dobishme n\u00eb baz\u00eb t\u00eb rezultateve t\u00eb analiz\u00ebs. Do t\u00eb ishte e p\u00ebrshtatshme t\u00eb kalojm\u00eb t\u00eb pakt\u00ebn pjes\u00ebrisht inteligjenc\u00ebn artificiale n\u00eb menaxhimin e gjith\u00eb k\u00ebtij trafiku rrjet dhe thirrjeve t\u00eb aplikacioneve, t\u00eb integruara n\u00eb Service Mesh.<\/p>\n
Sh\u00ebrbimi API Gateway (Shkalla API)<\/h3>\n \nSi rregull, n\u00eb Service Mesh ka proksi dhe sh\u00ebrbime q\u00eb komunikojn\u00eb me nj\u00ebra-tjetr\u00ebn brenda nj\u00eb perimeteri t\u00eb besuesh\u00ebm. Por ka edhe kontraktor\u00eb t\u00eb jasht\u00ebm. K\u00ebrkesat p\u00ebr API-t\u00eb q\u00eb i ofrohen k\u00ebtij grupi konsumator\u00ebsh jan\u00eb shum\u00eb m\u00eb serioze. K\u00ebt\u00eb detyr\u00eb ne e ndajm\u00eb n\u00eb dy pjes\u00eb kryesore. <\/p>\n
\nSiguria<\/i>. Pyetje q\u00eb lidhen me ddos, vulnerabilitetin e protokolleve, aplikacioneve, sistemeve operative dhe k\u00ebshtu me radh\u00eb. \n<\/li>\nShkall\u00ebt<\/i>. Kur llogarit\u00eb API, q\u00eb duhet t'u jepen klient\u00ebve, shkojn\u00eb n\u00eb mij\u00ebra ose madje qindra mij\u00ebra, lind nevoja p\u00ebr nj\u00eb mjet menaxhimi t\u00eb k\u00ebtij grupi API. Duhet t\u00eb ndjekim vazhdimisht API: n\u00ebse ata funksionojn\u00eb ose jo, \u00e7far\u00eb statusi kan\u00eb, \u00e7far\u00eb trafiku po shkon, cila \u00ebsht\u00eb statistika etj. Nj\u00eb port\u00eb API duhet t\u00eb p\u00ebrballoj\u00eb k\u00ebt\u00eb detyr\u00eb, duke e b\u00ebr\u00eb gjith\u00eb procesin t\u00eb menaxhuesh\u00ebm dhe t\u00eb sigurt. Fal\u00eb k\u00ebtij komponenti, Enterprise Service Mesh m\u00ebson t\u00eb publikoj\u00eb pa komplikime si API t\u00eb brendshme ashtu edhe ato t\u00eb jashtme.\n<\/li>\n<\/ul>\n <\/p>\n
Sh\u00ebrbimi mb\u00ebshtet\u00ebs p\u00ebr protokolle specifike dhe formate t\u00eb dh\u00ebnash (port\u00eb AS)<\/h3>\n \nAktualisht, shumica e zgjidhjeve t\u00eb Service Mesh din\u00eb t\u00eb punojn\u00eb natyrisht vet\u00ebm me trafik HTTP dhe HTTP2 ose n\u00eb nj\u00eb m\u00ebnyr\u00eb t\u00eb kufizuar n\u00eb nivelin TCP\/IP. Enterprise Service Mesh sjell shum\u00eb protokolle t\u00eb tjera t\u00eb transmetimit t\u00eb dh\u00ebnash mjaft specifike. Disa sisteme mund t\u00eb p\u00ebrdorin broker\u00eb mesazhesh, t\u00eb tjerat jan\u00eb t\u00eb integruara n\u00eb nivelin e bazave t\u00eb t\u00eb dh\u00ebnave. N\u00ebse n\u00eb kompani ka SAP, ai gjithashtu mund t\u00eb p\u00ebrdor\u00eb sistemin e vet t\u00eb integrimit. Dhe t\u00eb gjitha k\u00ebto funksionojn\u00eb dhe jan\u00eb nj\u00eb pjes\u00eb e r\u00ebnd\u00ebsishme e biznesit.<\/p>\n
Nuk mund t\u00eb thoni thjesht: \"Le t\u00eb heqim dor\u00eb nga sistemet e vjetra dhe t\u00eb b\u00ebjm\u00eb sisteme t\u00eb reja q\u00eb mund t\u00eb p\u00ebrdorin Service Mesh\". P\u00ebr t\u00eb bashkuar t\u00eb gjitha sistemet e vjetra me t\u00eb rejat (n\u00eb arkitektur\u00ebn mikro-sh\u00ebrbimore), sistemi q\u00eb mund t\u00eb p\u00ebrdor\u00eb Service Mesh do t'i duhet nj\u00eb adaptues, nd\u00ebrmjet\u00ebs, ose port\u00eb. Pajtohuni, do t\u00eb ishte mir\u00eb n\u00ebse ai do t\u00eb vinte i integruar me sh\u00ebrbimin. Porta AS pik\u00ebrisht mund t\u00eb mb\u00ebshtes\u00eb \u00e7do variant integrimi. Vet\u00ebm imagjinoni, thjesht instaloni Enterprise Service Mesh, dhe ai \u00ebsht\u00eb gati t\u00eb bashk\u00ebveproj\u00eb me t\u00eb gjitha protokollet q\u00eb ju nevojiten. P\u00ebr ne, ky qasje \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme.<\/p>\n
K\u00ebshtu e paraqesim versionin korporativ t\u00eb Service Mesh (Enterprise Service Mesh). Kjo personalizim zgjidh shumic\u00ebn e problemeve q\u00eb lindin kur p\u00ebrpiqeni t\u00eb p\u00ebrdorni versione t\u00eb hapura t\u00eb platform\u00ebs integruese. Duke u shfaqur vet\u00ebm disa vite m\u00eb par\u00eb, arkitektura e Service Mesh vazhdon t\u00eb evoluoj\u00eb, dhe ne jemi t\u00eb lumtur q\u00eb mund t\u00eb kontribuojm\u00eb n\u00eb zhvillimin e saj. Shpresojm\u00eb q\u00eb p\u00ebrvoja jon\u00eb do t'ju ndihmoj\u00eb.<\/i>habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"Service Mesh \u2014 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u044b\u0439 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u043d\u044b\u0439 \u043f\u0430\u0442\u0442\u0435\u0440\u043d \u0434\u043b\u044f \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0438 \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0430 \u043d\u0430 \u043e\u0431\u043b\u0430\u0447\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u043e-\u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043d\u043e\u043c \u043c\u0438\u0440\u0435 \u043e\u0431\u043e\u0439\u0442\u0438\u0441\u044c \u0431\u0435\u0437 \u043d\u0435\u0433\u043e \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u0441\u043b\u043e\u0436\u043d\u043e. \u041d\u0430 \u0440\u044b\u043d\u043a\u0435 \u0443\u0436\u0435 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e open-source \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0439 service mesh, \u043d\u043e \u0438\u0445 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u0438, \u043d\u0430\u0434\u0435\u0436\u043d\u043e\u0441\u0442\u0438 \u0438 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u0430\u043b\u0435\u043a\u043e \u043d\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043a\u043e\u0433\u0434\u0430 \u0440\u0435\u0447\u044c \u0438\u0434\u0435\u0442 \u043e \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0439 \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u0430 \u0432\u0441\u0435\u0439 \u0441\u0442\u0440\u0430\u043d\u044b. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26549,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35388","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"Pse](\"\/wp-content\/uploads\/2019\/06\/90b0df34323399c96548f86b6bd16522.jpg\")