<\/a><\/noindex>
N\u00eb nivelin e proxy-it (data plane):<\/i><\/p>\n\nCaktimi dhe shp\u00ebrndarja e politikave t\u00eb routing-ut dhe balancimit t\u00eb trafikut\n<\/li>\n Shp\u00ebrndarja e \u00e7el\u00ebsave, certifikatave, tokeneve\n<\/li>\n Grumbullimi i telemetris\u00eb, krijimi i metrikeve t\u00eb monitorimit\n<\/li>\n Integrimi me infrastruktur\u00ebn e siguris\u00eb dhe monitorimit\n<\/li>\n<\/ul>\n\nN\u00eb nivelin e qarkut t\u00eb menaxhimit (control plane):<\/i><\/p>\n\nZbatimi i politikave t\u00eb routing-ut dhe balancimit t\u00eb trafikut\n<\/li>\n Menaxhimi i p\u00ebrs\u00ebritjeve dhe koh\u00ebzgjatjeve, p\u00ebrcaktimi i \u2018niveleve\u2019 t\u00eb vdekura (circuit breaking), menaxhimi i situatave me d\u00ebshtim (injecting faults) dhe sigurimi i q\u00ebndrueshm\u00ebris\u00eb (resilience) s\u00eb sh\u00ebrbimeve p\u00ebrmes mekanizmave t\u00eb tjer\u00eb\n<\/li>\n Autentikimi\/autorizimi i thirrjeve\n<\/li>\n Heqja e metrikave (observability)\n<\/li>\n<\/ul>\n\nGrupi 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, si PayPal.<\/p>\n
P\u00ebr \u00e7far\u00eb nevojitet Service Mesh n\u00eb sektorin e korporatave<\/h2>\n \nP\u00ebrdorimi i Service Mesh sjell nj\u00eb s\u00ebr\u00eb p\u00ebrfitimesh t\u00eb dukshme. Para s\u00eb gjithash, kjo \u00ebsht\u00eb e p\u00ebrshtatshme p\u00ebr zhvilluesit: p\u00ebr shk \u03b3\u03c1\u03acmin e kodit shfaqet nj\u00eb platform\u00eb teknologjike<\/i>, e cila ndihmon ndjesh\u00ebm n\u00eb 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 e thjeshton marr\u00ebdh\u00ebnien midis ofruesve dhe konsumator\u00ebve.<\/i> Sot, ofruesit dhe konsumator\u00ebt e API-ve kan\u00eb shum\u00eb m\u00eb t\u00eb leht\u00eb t\u00eb bien dakord p\u00ebr interfesat dhe kontratat vet\u00eb, pa t\u00ebrhequr nj\u00eb nd\u00ebrmjet\u00ebs t\u00eb ve\u00e7ant\u00eb integrimi dhe arbitri \u2013 nj\u00eb autobus sh\u00ebrbimesh korporative. Ky qasje ndikon ndjesh\u00ebm n\u00eb dy tregues. Rritet shpejt\u00ebsia e nxjerrjes s\u00eb funksionaliteteve t\u00eb reja n\u00eb treg (time-to-market), por n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb rritet kostoja e zgjidhjes, pasi integrimi duhet t\u00eb b\u00ebhet vet\u00eb. P\u00ebrdorimi i Service Mesh nga ekipet e zhvillimit t\u00eb funksionaliteteve t\u00eb biznesit lejon ruajtjen e ekuilibrave k\u00ebtu. Si rezultat, ofruesit e API-ve mund t\u00eb fokusohen ekskluzivisht te elementi aplikativ t\u00eb sh\u00ebrbimit t\u00eb tyre dhe thjesht ta publikojn\u00eb at\u00eb n\u00eb Service Mesh \u2014 API do t\u00eb b\u00ebhet menj\u00ebher\u00eb i disponuesh\u00ebm p\u00ebr t\u00eb gjith\u00eb klient\u00ebt dhe cil\u00ebsia e integrimit do t\u00eb jet\u00eb e gatshme p\u00ebr prodhim dhe nuk do t\u00eb k\u00ebrkoj\u00eb asnj\u00eb rresht kodi t\u00eb shtuar.<\/p>\n
Avantazhi tjet\u00ebr \u00ebsht\u00eb ai q\u00eb zhvilluesi, duke p\u00ebrdorur Service Mesh, fokusohet ekskluzivisht n\u00eb funksionalitetin e biznesit<\/i> \u2014 n\u00eb aspektin produktiv, e jo n\u00eb at\u00eb teknologjik t\u00eb sh\u00ebrbimit t\u00eb tij. P\u00ebr shembull, nuk \u00ebsht\u00eb m\u00eb e nevojshme t\u00eb mendosh se n\u00eb situat\u00ebn kur sh\u00ebrbimi do t\u00eb thirret p\u00ebrmes rrjetit, mund t\u00eb ndodh\u00eb nj\u00eb nd\u00ebrprerje e lidhjes. P\u00ebr m\u00eb tep\u00ebr, Service Mesh ndihmon n\u00eb balancimin e trafikut mes kopjeve t\u00eb nj\u00ebjt\u00eb t\u00eb sh\u00ebrbimit: n\u00ebse nj\u00eb nga kopjet \"ka vdekur\", sistemi do t\u00eb kaloj\u00eb t\u00ebr\u00eb trafikun n\u00eb kopjet e mbetura t\u00eb gjalla. <\/p>\n
Service Mesh <\/i>\u2014 kjo \u00ebsht\u00eb nj\u00eb baz\u00eb e mir\u00eb p\u00ebr krijimin e aplikacioneve t\u00eb shp\u00ebrndara<\/i>, e cila e fsheh nga klienti detajet e sigurimit t\u00eb thirrjeve t\u00eb 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 izoluar n\u00eb nivelin e transportit si nga rrjeti, ashtu edhe nga nj\u00ebra-tjetra: nuk ka asnj\u00eb lidhje midis tyre. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, zhvilluesi merr kontrollin e plot\u00eb mbi sh\u00ebrbimet e tij.<\/p>\n
Nuk mund t\u00eb neglizhohet se aktualizimi i aplikacioneve t\u00eb shp\u00ebrndara n\u00eb nj\u00eb mjedis ku p\u00ebrdoret Service Mesh b\u00ebhet m\u00eb i leht\u00eb.<\/i> P\u00ebr shembull, implementimi blue\/green, ku ka dy mjedise aplikacioni n\u00eb dispozicion p\u00ebr instalim, nj\u00ebra nga t\u00eb cilat nuk p\u00ebrdit\u00ebsohet dhe ndodhet n\u00eb presje. R\u00ebnia n\u00eb versionin e kaluar n\u00eb rast t\u00eb nj\u00eb l\u00ebshimi t\u00eb d\u00ebshtuar b\u00ebhet p\u00ebrmes nj\u00eb router-i t\u00eb ve\u00e7ant\u00eb, nj\u00eb rol q\u00eb e kryen mjaft mir\u00eb Service Mesh.. <\/i>P\u00ebr testimin e versionit t\u00eb ri mund t\u00eb p\u00ebrdoret gjithashtu l\u00ebshimi kanadez <\/i>\u2014 t\u00eb kaloni n\u00eb versionin e ri vet\u00ebm p\u00ebr 10% t\u00eb trafikut ose k\u00ebrkesave nga grupi pilot i klient\u00ebve. Trafiku kryesor shkon n\u00eb versionin e vjet\u00ebr, asgj\u00eb nuk prish.<\/p>\n
Gjithashtu Service Mesh na jep kontrollin SLA n\u00eb koh\u00eb reale<\/i>. Sistemi i proxy-ve t\u00eb shp\u00ebrndar\u00eb nuk do t'i lejoj\u00eb sh\u00ebrbimit t\u00eb d\u00ebshtoj\u00eb kur ndonj\u00eb klient kalon kuot\u00ebn e dh\u00ebn\u00eb. N\u00ebse kapaciteti p\u00ebr API \u00ebsht\u00eb i kufizuar, askush nuk mund ta godas\u00eb at\u00eb me nj\u00eb num\u00ebr t\u00eb madh transaksionesh: Service Mesh q\u00ebndron para sh\u00ebrbimit dhe nuk l\u00ebviz trafik t\u00eb tep\u00ebrt. Ai thjesht do t\u00eb mbrohet 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 kompania d\u00ebshiron t\u00eb reduktoj\u00eb shpenzimet p\u00ebr zhvillimin e zgjidhjeve integruese, Service Mesh gjithashtu ndihmon: mund t\u00eb kaloni n\u00eb versionin e tij open-source nga produktet komerciale.<\/i>. Service Mesh-i yn\u00eb Enterprise bazohet n\u00eb versionin open-source t\u00eb Service Mesh. <\/p>\n
Nj\u00eb tjet\u00ebr avantazh \u00ebsht\u00eb prania e nj\u00eb grupe t\u00eb vet\u00ebm dhe t\u00eb plot\u00eb sh\u00ebrbimesh integruese<\/i>. Duke qen\u00eb se e gjith\u00eb integrimi nd\u00ebrtohet p\u00ebrmes k\u00ebtij shtres\u00eb nd\u00ebrmjet\u00ebse, ne mund t\u00eb menaxhojm\u00eb t\u00eb gjith\u00eb trafikun integrues dhe lidhjet midis aplikacioneve, t\u00eb cilat formojn\u00eb thelbin e biznesit t\u00eb kompanis\u00eb. Kjo \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme.<\/p>\n
Dhe m\u00eb n\u00eb fund Service Mesh inkurajon kompanin\u00eb t\u00eb kaloj\u00eb n\u00eb nj\u00eb infrastruktur\u00eb dinamike.<\/i> Tani tani n\u00eb shum\u00eb njer\u00ebz po shikojn\u00eb drejt konteinerizimit. T\u00eb ndahen monolit\u00ebt n\u00eb mikrosherbime, t\u00eb implementohen t\u00eb gjitha k\u00ebto bukur \u2014 tema \u00ebsht\u00eb n\u00eb rritje. Por kur p\u00ebrpiqesh t\u00eb kalosh n\u00eb nj\u00eb sistem t\u00eb ri, q\u00eb ka qen\u00eb n\u00eb prodhim p\u00ebr shum\u00eb vite, menj\u00ebher\u00eb p\u00ebrballesh me nj\u00eb s\u00ebr\u00eb problemasht: e b\u00ebn t\u00eb v\u00ebshtir\u00eb vendosjen e t\u00eb gjitha k\u00ebtyre n\u00eb kontejner\u00eb dhe shp\u00ebrndarjen n\u00eb platform\u00eb. Dhe implementimi, sinkronizimi dhe nd\u00ebrveprimi i k\u00ebtyre p\u00ebrb\u00ebr\u00ebsve t\u00eb shp\u00ebrndar\u00eb \u2014 \u00ebsht\u00eb nj\u00eb tjet\u00ebr tem\u00eb shum\u00eb e v\u00ebshtir\u00eb. Si do t\u00eb komunikojn\u00eb ata me nj\u00ebri-tjetrin? A do t\u00eb ket\u00eb d\u00ebshtime kaskad\u00eb? Service Mesh lejon t\u00eb zgjidhen disa nga 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 rrjetit t\u00eb harrohet.<\/p>\nPse \u00ebsht\u00eb e nevojshme personalizimi i Service Mesh<\/h2>\n
\nN\u00eb kompanin\u00eb ton\u00eb bashk\u00ebjetojn\u00eb qindra sisteme dhe module, dhe runtime \u00ebsht\u00eb shum\u00eb i ngarkuar. K\u00ebshtu q\u00eb 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 ne n\u00eb prodhim duam m\u00eb shum\u00eb. \u00c7far\u00eb tjet\u00ebr k\u00ebrkohet nga Service Mesh-i korporativ? <\/p>\n
Sh\u00ebrbimi i p\u00ebrpunimit t\u00eb ngjarjeve<\/h3>\n \nImagjinoni se na nevojitet t\u00eb realizojm\u00eb p\u00ebrpunimin n\u00eb koh\u00eb reale t\u00eb ngjarjeve \u2014 nj\u00eb sistem q\u00eb analizon veprimet e klientit n\u00eb koh\u00eb reale dhe mund menj\u00ebher\u00eb t\u00eb i b\u00ebj\u00eb nj\u00eb propozim rethues. P\u00ebr t\u00eb realizuar nj\u00eb funksionalitet t\u00eb till\u00eb, p\u00ebrdoret nj\u00eb model arkitektonik i quajtur arkitektur\u00eb e drejtuar nga ngjarjet (EDA)<\/i>. Asnj\u00eb nga Service Mesh aktuale nuk mb\u00ebshtet natyrsh\u00ebm k\u00ebto modele, dhe kjo \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme, sidomos p\u00ebr bank\u00ebn!<\/p>\n
\u00cbsht\u00eb mjaft \u00e7uditshme q\u00eb \"thirrja e larg\u00ebt\" Remote Procedure Call (RPC) mb\u00ebshtetet nga t\u00eb gjitha versionet e Service Mesh, nd\u00ebrsa me EDA nuk bashk\u00ebveprojn\u00eb. Sepse Service Mesh \u00ebsht\u00eb nj\u00eb e ngjashme e integrimit modern t\u00eb shp\u00ebrndar\u00eb, nd\u00ebrsa EDA \u00ebsht\u00eb nj\u00eb model arkitektonik shum\u00eb aktual q\u00eb lejon t\u00eb realizohen gj\u00ebra unike n\u00eb p\u00ebrvoj\u00ebn e klientit.<\/p>\n
Enterprise Service Mesh yn\u00eb duhet t\u00eb zgjidh\u00eb k\u00ebt\u00eb problem. P\u00ebr m\u00eb tep\u00ebr, ne duam t\u00eb shohim n\u00eb t\u00eb realizimin e dor\u00ebzimit t\u00eb garantuar, p\u00ebrpunimin e ngjarjeve n\u00eb rrjedh\u00eb dhe t\u00ebr\u00ebsor me p\u00ebrdorimin e filtrave dhe jack-podave t\u00eb ndrysh\u00ebm.<\/p>\n
Sh\u00ebrbimi i transferimit t\u00eb skedar\u00ebve<\/h3>\n \nP\u00ebrve\u00e7 EDA, do t\u00eb ishte mir\u00eb t\u00eb kishte mund\u00ebsin\u00eb p\u00ebr t\u00eb transferuar skedar\u00eb: n\u00eb shkall\u00ebn e Enterprise shpesh her\u00eb \u00ebsht\u00eb e mundur vet\u00ebm integrimi i skedar\u00ebve. Konkretisht, p\u00ebrdoret modeli arkitektonik ETL (Extract, Transform, Load \u2014 \"ekstraktim, transformim, ngarkim\"). N\u00eb t\u00eb, zakonisht, t\u00eb gjith\u00eb ndajn\u00eb skedar\u00eb: p\u00ebrpunohen t\u00eb dh\u00ebna t\u00eb m\u00ebdha q\u00eb nuk jan\u00eb t\u00eb arsyeshme t\u00eb d\u00ebrgohen me k\u00ebrkesa t\u00eb ve\u00e7anta. Mund\u00ebsia e mb\u00ebshtetjes natyrore 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.sh., n\u00eb nj\u00eb bank\u00eb disa ekipe punojn\u00eb me depozita, nd\u00ebrsa t\u00eb tjer\u00eb \u2014 me produkte krediti, dhe ka mjaft raste t\u00eb tilla. 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 t\u00eb tjer\u00ebve. Dhe shpesh lind nevoja p\u00ebr kompozimin e k\u00ebtyre sh\u00ebrbimeve, si dhe p\u00ebr implementimin e logjik\u00ebs s\u00eb nd\u00ebrlikuar t\u00eb thirrjes s\u00eb nj\u00eb grupi API-sh. 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 k\u00ebsaj logjike kompozite (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 mikrosherbimet komunikohet p\u00ebrmes nj\u00eb shtrese integruese t\u00eb vetme, Service Mesh, natyrsh\u00ebm, di gjith\u00e7ka rreth thirrjeve t\u00eb \u00e7do sh\u00ebrbimi. Ne mbledhim telemetrin\u00eb: kush e thirri cilin, kur, sa gjat\u00eb, sa her\u00eb etj. Kur k\u00ebto sh\u00ebrbime jan\u00eb qindra mij\u00ebra, dhe thirrjet \u2014 miliarda, t\u00eb gjitha k\u00ebto akumulohen dhe formojn\u00eb Big Data. K\u00ebto t\u00eb dh\u00ebna mund t\u00eb analizohen me mjete t\u00eb AI, machine learning etj., dhe pastaj t\u00eb b\u00ebhen disa gj\u00ebra t\u00eb dobishme bazuar n\u00eb rezultatet e analiz\u00ebs. Do ishte e duhur, t\u00eb pakt\u00ebn pjes\u00ebrisht, t\u2019i kalonim inteligjenc\u00ebs artificiale menaxhimin e gjith\u00eb k\u00ebtij trafiku rrjeth\u00ebs dhe thirrjeve t\u00eb aplikacioneve, t\u00eb integuara n\u00eb Service Mesh.<\/p>\n
Sh\u00ebrbimi API Gateway<\/h3>\n \nSi rregull, n\u00eb Service Mesh ka proxy dhe sh\u00ebrbime q\u00eb komunikojn\u00eb mes tyre brenda nj\u00eb perimetrin t\u00eb besuesh\u00ebm. Por ka gjithashtu edhe kontraktor\u00eb t\u00eb jasht\u00ebm. K\u00ebrkesat ndaj API-ve q\u00eb ofrohen p\u00ebr k\u00ebt\u00eb grup konsumator\u00ebsh jan\u00eb shum\u00eb m\u00eb serioze. Ne e ndajm\u00eb k\u00ebt\u00eb detyr\u00eb n\u00eb dy pjes\u00eb kryesore. <\/p>\n
\nSiguria<\/i>. Pyetje, t\u00eb lidhura me ddos, cenueshm\u00ebrin\u00eb e protokolleve, aplikacioneve, sistemeve operative etj. \n<\/li>\nShkall\u00ebt<\/i>. Kur vendi i API, q\u00eb duhet t'u jepet klient\u00ebve, \u00ebsht\u00eb n\u00eb mij\u00ebra ose madje qindra mij\u00ebra, ndjenja e nevoj\u00ebs p\u00ebr nj\u00eb mjet p\u00ebr menaxhimin e k\u00ebtij grupi API krijohet. Duhet t\u00eb monitorohet vazhdimisht API: a funksionojn\u00eb ata apo jo, \u00e7far\u00eb statusi kan\u00eb, \u00e7far\u00eb trafiku po shkon, cilat jan\u00eb statistikat, etj. Portali API duhet ta p\u00ebrballoj\u00eb k\u00ebt\u00eb detyr\u00eb, duke b\u00ebr\u00eb q\u00eb e gjith\u00eb procesi t\u00eb jet\u00eb i menaxhuesh\u00ebm dhe i sigurt. Fal\u00eb k\u00ebsaj komponente, Enterprise Service Mesh m\u00ebson t\u00eb publikoj\u00eb pa asnj\u00eb v\u00ebshtir\u00ebsi API si t\u00eb brendsh\u00ebm ashtu edhe t\u00eb jasht\u00ebm.\n<\/li>\n<\/ul>\n <\/p>\n
Sh\u00ebrbimi i mb\u00ebshtetjes p\u00ebr protokollet specifik\u00eb dhe formatet e t\u00eb dh\u00ebnave (portali API)<\/h3>\n \nAktualisht, shumica e zgjidhjeve Service Mesh din\u00eb t\u00eb punojn\u00eb natyrsh\u00ebm vet\u00ebm me trafik HTTP dhe HTTP2 ose n\u00eb nj\u00eb modalitet t\u00eb kufizuar n\u00eb nivelin TCP\/IP. Enterprise Service Mesh ka shum\u00eb protokolle t\u00eb tjera t\u00eb p\u00ebrcjelljes s\u00eb t\u00eb dh\u00ebnave shum\u00eb specifike. Disa sisteme mund t\u00eb p\u00ebrdorin broker\u00eb mesazhesh, t\u00eb tjera integrohen n\u00eb nivelin e bazave t\u00eb t\u00eb dh\u00ebnave. N\u00ebse n\u00eb kompanin\u00eb tuaj ka SAP, ai gjithashtu mund t\u00eb p\u00ebrdor\u00eb sistemin e tij t\u00eb integrimit. Dhe e gjith\u00eb kjo funksionon dhe \u00ebsht\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 legjenda dhe t\u00eb b\u00ebjm\u00eb sisteme t\u00eb reja q\u00eb do t\u00eb jen\u00eb n\u00eb gjendje t\u00eb p\u00ebrdorin Service Mesh\". P\u00ebr t\u00eb lidhur t\u00eb gjitha sistemet e vjetra me ato t\u00eb reja (n\u00eb arkitektur\u00ebn mikrosh\u00ebrbimeve), sistemet q\u00eb mund t\u00eb p\u00ebrdorin Service Mesh do t\u00eb ken\u00eb nevoj\u00eb p\u00ebr nj\u00eb adaptues, nj\u00eb nd\u00ebrmjet\u00ebs, nj\u00eb portal. Pajtohuni, do t\u00eb ishte e shk\u00eblqyer n\u00ebse ai do gjendej si nj\u00eb paket\u00eb bashk\u00eb me sh\u00ebrbimin. Portali API sakt\u00ebsisht mund t\u00eb mb\u00ebshtes\u00eb \u00e7do opsion integrimi. Imagjinoni, thjesht instaluat Enterprise Service Mesh, dhe ai \u00ebsht\u00eb tashm\u00eb i gatsh\u00ebm t\u00eb bashk\u00ebpunoj\u00eb me t\u00eb gjith\u00eb protokollet q\u00eb ju nevojiten. Ky qasje \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ne.<\/p>\n
Pik\u00ebrisht k\u00ebshtu ne e paraqesim versionin korporativ t\u00eb Service Mesh (Enterprise Service Mesh). Personalizimi i p\u00ebrshkruar zgjidh shumic\u00ebn e problemeve q\u00eb shfaqen kur p\u00ebrpiqeni t\u00eb p\u00ebrdorni versionet e gatshme open-source t\u00eb platform\u00ebs integruese. Pasi \u00ebsht\u00eb shfaqur vet\u00ebm disa vjet m\u00eb par\u00eb, arkitektura Service Mesh vazhdon t\u00eb zhvillohet, 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\u00eb jet\u00eb e dobishme p\u00ebr ju.<\/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\")