{"id":35388,"date":"2019-10-31T22:04:01","date_gmt":"2019-10-31T19:04:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/zachem-my-delaem-enterprise-service-mesh\/"},"modified":"2019-10-31T22:04:01","modified_gmt":"2019-10-31T19:04:01","slug":"zachem-my-delaem-enterprise-service-mesh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/zachem-my-delaem-enterprise-service-mesh","title":{"rendered":"Pro\u010d d\u011bl\u00e1me Enterprise Service Mesh","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Service Mesh \u2014 zn\u00e1m\u00fd architektonick\u00fd vzor pro integraci mikroservis\u016f a p\u0159echod na cloudovou infrastrukturu. Dnes je ve sv\u011bt\u011b cloudov\u00fdch kontejner\u016f obt\u00ed\u017en\u00e9 se bez n\u011bj obej\u00edt. Na trhu je ji\u017e k dispozici n\u011bkolik open-source realizac\u00ed service mesh, ale jejich funk\u010dnost, spolehlivost a bezpe\u010dnost \u010dasto nesta\u010d\u00ed, zejm\u00e9na pokud jde o po\u017eadavky velk\u00fdch finan\u010dn\u00edch spole\u010dnost\u00ed na n\u00e1rodn\u00ed \u00farovni. Proto jsme v Sbertechu se rozhodli p\u0159izp\u016fsobit Service Mesh a chceme \u0159\u00edct, co je na Service Mesh skv\u011bl\u00e9, co ne a co s t\u00edm hodl\u00e1me ud\u011blat.<\/p>\n<p><img decoding=\"async\" alt=\"Pro\u010d d\u011bl\u00e1me Enterprise Service Mesh\" src=\"\/wp-content\/uploads\/2019\/06\/90b0df34323399c96548f86b6bd16522.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nPopularita vzoru Service Mesh roste s oblibou cloudov\u00fdch technologi\u00ed. P\u0159edstavuje dedikovanou infrastrukturn\u00ed vrstvu, kter\u00e1 zjednodu\u0161uje interakci mezi r\u016fzn\u00fdmi s\u00ed\u0165ov\u00fdmi slu\u017ebami. Modern\u00ed cloudov\u00e9 aplikace se skl\u00e1daj\u00ed ze stovek a dokonce tis\u00edc\u016f takov\u00fdch slu\u017eeb, z nich\u017e ka\u017ed\u00e1 m\u016f\u017ee m\u00edt tis\u00edce kopi\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"Pro\u010d d\u011bl\u00e1me Enterprise Service Mesh\" src=\"\/wp-content\/uploads\/2019\/06\/f74229b8d4d75a9b0bb9ad292ec9de85.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nInterakce mezi t\u011bmito slu\u017ebami a jejich spr\u00e1va je kl\u00ed\u010dov\u00fdm \u00fakolem Service Mesh. V podstat\u011b se jedn\u00e1 o s\u00ed\u0165ov\u00fd model z mnoha proxy, kter\u00e9 jsou \u0159\u00edzeny centr\u00e1ln\u011b a vykon\u00e1vaj\u00ed soubor velmi u\u017eite\u010dn\u00fdch funkc\u00ed.<\/p>\n<p><i>Na \u00farovni proxy (data plane):<\/i><\/p>\n<ul>\n<li>P\u0159i\u0159azen\u00ed a \u0161\u00ed\u0159en\u00ed politik sm\u011brov\u00e1n\u00ed a vyva\u017eov\u00e1n\u00ed provozu\n<\/li>\n<li>Distribuce kl\u00ed\u010d\u016f, certifik\u00e1t\u016f, token\u016f\n<\/li>\n<li>Sb\u011br telemetrie, formov\u00e1n\u00ed metrik monitorov\u00e1n\u00ed\n<\/li>\n<li>Integrace s infrastrukturou bezpe\u010dnosti a monitorov\u00e1n\u00ed\n<\/li>\n<\/ul>\n<p>\n<i>Na \u00farovni \u0159\u00eddic\u00ed smy\u010dky (control plane):<\/i><\/p>\n<ul>\n<li>Aplikace politik sm\u011brov\u00e1n\u00ed a vyva\u017eov\u00e1n\u00ed provozu\n<\/li>\n<li>Spr\u00e1va opakov\u00e1n\u00ed a \u010dasov\u00fdch limit\u016f, ur\u010den\u00ed \"mrtv\u00fdch\" uzl\u016f (circuit breaking), spr\u00e1va havarijn\u00edch situac\u00ed (injecting faults) a zaji\u0161t\u011bn\u00ed odolnosti (resilience) slu\u017eeb prost\u0159ednictv\u00edm dal\u0161\u00edch mechanism\u016f\n<\/li>\n<li>Autentizace\/ autorizace vol\u00e1n\u00ed\n<\/li>\n<li>Odbaven\u00ed metrik (observability)\n<\/li>\n<\/ul>\n<p>\nOkruh u\u017eivatel\u016f, kte\u0159\u00ed maj\u00ed z\u00e1jem o rozvoj t\u00e9to technologie, je velmi \u0161irok\u00fd \u2014 od mal\u00fdch startup\u016f po velk\u00e9 internetov\u00e9 korporace, jako je nap\u0159\u00edklad PayPal.<\/p>\n<h2>K \u010demu je Service Mesh v podnikatelsk\u00e9m sektoru<\/h2>\n<p>\nPou\u017e\u00edv\u00e1n\u00ed Service Mesh p\u0159in\u00e1\u0161\u00ed \u0159adu z\u0159ejm\u00fdch v\u00fdhod. P\u0159edev\u0161\u00edm je to jednodu\u0161\u0161\u00ed pro v\u00fdvoj\u00e1\u0159e: pro psan\u00ed k\u00f3du <i>se objevuje technologick\u00e1 platforma<\/i>, kter\u00e1 v\u00fdrazn\u011b usnad\u0148uje integraci do cloudov\u00e9 infrastruktury t\u00edm, \u017ee je transportn\u00ed vrstva pln\u011b izolov\u00e1na od aplika\u010dn\u00ed logiky.<\/p>\n<p>Krom\u011b toho, <i>Service Mesh usnad\u0148uje vztahy mezi poskytovateli a u\u017eivateli.<\/i> Dnes je pro poskytovatele a u\u017eivatele API mnohem snaz\u0161\u00ed vyjednat rozhran\u00ed a smlouvy samostatn\u011b, ani\u017e by byl zapot\u0159eb\u00ed specializovan\u00fd integra\u010dn\u00ed zprost\u0159edkovatel \u010di rozhod\u010d\u00ed \u2013 podnikov\u00e1 servisn\u00ed \u0161ina. Tento p\u0159\u00edstup m\u00e1 z\u00e1sadn\u00ed vliv na dv\u011b metriky. Zv\u00fd\u0161uje se rychlost uv\u00e1d\u011bn\u00ed nov\u00e9 funk\u010dnosti na trh (time-to-market), av\u0161ak z\u00e1rove\u0148 se zvy\u0161uj\u00ed n\u00e1klady na \u0159e\u0161en\u00ed, nebo\u0165 integraci je nutno prov\u00e1d\u011bt samostatn\u011b. Pou\u017eit\u00ed Service Mesh t\u00fdmy vyv\u00edjej\u00edc\u00edmi podnikov\u00e9 funkce umo\u017e\u0148uje udr\u017eet rovnov\u00e1hu. V\u00fdsledkem je, \u017ee poskytovatel\u00e9 API se mohou soust\u0159edit pouze na aplika\u010dn\u00ed slo\u017eku sv\u00e9 slu\u017eby a jednodu\u0161e ji publikovat v Service Mesh \u2013 API bude okam\u017eit\u011b dostupn\u00e9 v\u0161em klient\u016fm, a kvalita integrace bude p\u0159ipravena na produkci a nebude vy\u017eadovat ani \u0159\u00e1dek dal\u0161\u00edho k\u00f3du.<\/p>\n<p>Dal\u0161\u00ed v\u00fdhodou je, \u017ee <i>v\u00fdvoj\u00e1\u0159, pou\u017e\u00edvaj\u00edc\u00ed Service Mesh, se soust\u0159ed\u00ed v\u00fdhradn\u011b na podnikov\u00e9 funkce<\/i> \u2013 na produktovou, nikoli na technologickou slo\u017eku sv\u00e9 slu\u017eby. Nap\u0159\u00edklad ji\u017e nen\u00ed t\u0159eba p\u0159em\u00fd\u0161let o tom, \u017ee v situaci, kdy bude slu\u017eba vyvol\u00e1na p\u0159es s\u00ed\u0165, m\u016f\u017ee n\u011bkde doj\u00edt k p\u0159eru\u0161en\u00ed spojen\u00ed. Krom\u011b toho Service Mesh pom\u00e1h\u00e1 vyv\u00e1\u017eit provoz mezi kopiemi jedn\u00e9 a t\u00e9 sam\u00e9 slu\u017eby: pokud jedna z kopi\u00ed \"zhynula\", syst\u00e9m p\u0159epne ve\u0161ker\u00fd provoz na zb\u00fdvaj\u00edc\u00ed \u017eiv\u00e9 kopie. <\/p>\n<p><i>Service Mesh <\/i>\u2014<i> to je dobr\u00fd z\u00e1klad pro vytv\u00e1\u0159en\u00ed distribuovan\u00fdch aplikac\u00ed<\/i>, kter\u00e1 skr\u00fdv\u00e1 p\u0159ed u\u017eivateli detaily zaji\u0161t\u011bn\u00ed vol\u00e1n\u00ed jejich slu\u017eeb jak z vnit\u0159n\u00ed, tak z vn\u011bj\u0161\u00ed strany. V\u0161echny aplikace, kter\u00e9 pou\u017e\u00edvaj\u00ed Service Mesh, jsou na transportn\u00ed \u00farovni izolov\u00e1ny jak od s\u00edt\u011b, tak i mezi sebou navz\u00e1jem: neexistuje mezi nimi \u017e\u00e1dn\u00e9 spojen\u00ed. Nicm\u00e9n\u011b v\u00fdvoj\u00e1\u0159 z\u00edsk\u00e1v\u00e1 plnou kontrolu nad sv\u00fdmi slu\u017ebami.<\/p>\n<p>Nelze opomenout, \u017ee<i> aktualizace distribuovan\u00fdch aplikac\u00ed v prost\u0159ed\u00ed, kde se pou\u017e\u00edv\u00e1 Service Mesh, se st\u00e1v\u00e1 snaz\u0161\u00ed.<\/i> Nap\u0159\u00edklad blue\/green nasazen\u00ed, kde jsou k dispozici dv\u011b prost\u0159ed\u00ed aplikace, z nich\u017e jedno nen\u00ed aktualizov\u00e1no a \u010dek\u00e1. V p\u0159\u00edpad\u011b ne\u00fasp\u011b\u0161n\u00e9ho vyd\u00e1n\u00ed je zp\u011btn\u00fd p\u0159echod na p\u0159edchoz\u00ed verzi proveden speci\u00e1ln\u00edm routerem, s jeho\u017e rol\u00ed si skv\u011ble porad\u00ed Service Mesh.<i>. <\/i>Pro testov\u00e1n\u00ed nov\u00e9 verze lze pou\u017e\u00edt i <i>kan\u00e1rkovou verzi <\/i>\u2013 p\u0159epnout na novou verzi pouze 10 % provozu nebo po\u017eadavky od pilotn\u00ed skupiny z\u00e1kazn\u00edk\u016f. Hlavn\u00ed provoz jde na starou verzi, nic se nezhrout\u00ed.<\/p>\n<p>Tak\u00e9<i> Service Mesh n\u00e1m poskytuje kontrolu SLA v re\u00e1ln\u00e9m \u010dase.<\/i>Syst\u00e9m distribuovan\u00fdch proxy neumo\u017en\u00ed zkolabovat slu\u017eb\u011b, kdy\u017e n\u011bkdo ze z\u00e1kazn\u00edk\u016f p\u0159ekro\u010d\u00ed jemu p\u0159id\u011blenou kv\u00f3tu. Pokud je \u0161\u00ed\u0159ka p\u00e1sma API omezena, nikdo jej nebude moci obt\u011b\u017eovat velk\u00fdm mno\u017estv\u00edm transakc\u00ed: Service Mesh stoj\u00ed p\u0159ed slu\u017ebou a nepropust\u00ed nadbyte\u010dn\u00fd provoz. Ten jednodu\u0161e odraz\u00ed v integra\u010dn\u00edm layeru, zat\u00edmco samotn\u00e9 slu\u017eby budou pokra\u010dovat v provozu, jako by si ni\u010deho nev\u0161imly.<\/p>\n<p>Pokud chce spole\u010dnost sn\u00ed\u017eit n\u00e1klady na v\u00fdvoj integra\u010dn\u00edch \u0159e\u0161en\u00ed, Service Mesh rovn\u011b\u017e pom\u00e1h\u00e1: <i>na jeho open-source verzi lze p\u0159ej\u00edt z komer\u010dn\u00edch produkt\u016f.<\/i>N\u00e1\u0161 Enterprise Service Mesh je zalo\u017een na open-source verzi Service Mesh. <\/p>\n<p>Dal\u0161\u00ed v\u00fdhodou je <i>existence jednotn\u00e9 komplexn\u00ed sady integra\u010dn\u00edch slu\u017eeb.<\/i>Vzhledem k tomu, \u017ee cel\u00e1 integrace prob\u00edh\u00e1 prost\u0159ednictv\u00edm t\u00e9to prost\u0159edn\u00ed vrstvy, m\u016f\u017eeme \u0159\u00eddit cel\u00fd integra\u010dn\u00ed provoz a vztahy mezi aplikacemi, kter\u00e9 tvo\u0159\u00ed obchodn\u00ed j\u00e1dro spole\u010dnosti. To je velmi pohodln\u00e9.<\/p>\n<p>A nakonec <i>Service Mesh povzbuzuje spole\u010dnost k p\u0159echodu na dynamickou infrastrukturu.<\/i> V sou\u010dasnosti se mnoho lid\u00ed d\u00edv\u00e1 na kontejnery. Rozd\u011blen\u00ed monolitu na mikroslu\u017eby a jejich elegantn\u00ed zav\u00e1d\u011bn\u00ed - toto t\u00e9ma je v kurzu. Kdy\u017e se ale pokou\u0161\u00edte p\u0159ev\u00e9st syst\u00e9m, kter\u00fd b\u011b\u017e\u00ed v produkci ji\u017e \u0159adu let, na nov\u00fd model, naraz\u00edte na \u0159adu probl\u00e9m\u016f: VM\u00edstit to v\u0161e do kontejner\u016f a nasadit to na platform\u011b nen\u00ed snadn\u00e9. Implementace, synchronizace a interakce t\u011bchto distribuovan\u00fdch komponent\u016f je dal\u0161\u00ed velmi slo\u017eit\u00e9 t\u00e9ma. Jak spolu budou komunikovat? Nebudou zde kask\u00e1dov\u00e9 selh\u00e1n\u00ed? Service Mesh umo\u017e\u0148uje \u010d\u00e1ste\u010dn\u011b vy\u0159e\u0161it tyto probl\u00e9my a usnadnit migraci ze star\u00e9 architektury na novou d\u00edky tomu, \u017ee se m\u016f\u017eete p\u0159estat zab\u00fdvat logikou s\u00ed\u0165ov\u00e9 v\u00fdm\u011bny.<\/p>\n<h2>Pro\u010d je pot\u0159eba p\u0159izp\u016fsoben\u00ed Service Mesh<\/h2>\n<p>\nNa\u0161e spole\u010dnost si porad\u00ed se stovkami syst\u00e9m\u016f a modul\u016f, p\u0159i\u010dem\u017e runtime je velmi zat\u00ed\u017een\u00fd. Proto jednoduch\u00fd vzor, kdy jeden syst\u00e9m vol\u00e1 druh\u00fd a dost\u00e1v\u00e1 odpov\u011b\u010f, nesta\u010d\u00ed, proto\u017ee v produkci chceme v\u00edce. Co dal\u0161\u00edho pot\u0159ebujeme od podnikov\u00e9ho Service Mesh? <\/p>\n<p><img decoding=\"async\" alt=\"Pro\u010d d\u011bl\u00e1me Enterprise Service Mesh\" src=\"\/wp-content\/uploads\/2019\/06\/a4d40151f03b45d72117f678b7996bb6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Slu\u017eba zpracov\u00e1n\u00ed ud\u00e1lost\u00ed<\/h3>\n<p>\nP\u0159edstavme si, \u017ee pot\u0159ebujeme vytvo\u0159it syst\u00e9m pro zpracov\u00e1n\u00ed ud\u00e1lost\u00ed v re\u00e1ln\u00e9m \u010dase, kter\u00fd analyzuje akce klienta a m\u016f\u017ee mu okam\u017eit\u011b nab\u00eddnout relevantn\u00ed nab\u00eddku. Pro implementaci takov\u00e9 funk\u010dnosti se pou\u017e\u00edv\u00e1 <i>architektonick\u00fd vzor nazvan\u00fd event-driven architecture (EDA)<\/i>. \u017d\u00e1dn\u00fd z aktu\u00e1ln\u00edch Service Mesh tento vzor nativn\u011b nepodporuje, co\u017e je velmi d\u016fle\u017eit\u00e9, zejm\u00e9na pro banku!<\/p>\n<p>Je pom\u011brn\u011b podivn\u00e9, \u017ee \u201evzd\u00e1len\u00e9 vol\u00e1n\u00ed\u201c Remote Procedure Call (RPC) podporuj\u00ed v\u0161echny verze Service Mesh, zat\u00edmco s EDA nemaj\u00ed dobr\u00e9 vztahy. Proto\u017ee Service Mesh je podobn\u00e9 modern\u00ed distribuovan\u00e9 integraci, zat\u00edmco EDA je velmi aktu\u00e1ln\u00ed architektonick\u00fd vzor, kter\u00fd umo\u017e\u0148uje vytv\u00e1\u0159et jedine\u010dn\u00e9 mo\u017enosti, pokud jde o z\u00e1kaznickou zku\u0161enost.<\/p>\n<p>Na\u0161e Enterprise Service Mesh by m\u011blo tento probl\u00e9m \u0159e\u0161it. Krom\u011b toho chceme, aby obsahovalo implementaci zaru\u010den\u00e9 dod\u00e1vky, streamov\u00e9ho a komplexn\u00edho zpracov\u00e1n\u00ed ud\u00e1lost\u00ed s vyu\u017eit\u00edm r\u016fzn\u00fdch filtr\u016f a \u0161ablon.<\/p>\n<h3>Slu\u017eba p\u0159enosu soubor\u016f<\/h3>\n<p>\nKrom\u011b EDA by bylo dobr\u00e9 m\u00edt mo\u017enost p\u0159en\u00e1\u0161et soubory: v r\u00e1mci podnik\u016f je velmi \u010dasto mo\u017en\u00e1 pouze souborov\u00e1 integrace. Konkr\u00e9tn\u011b se pou\u017e\u00edv\u00e1 architektonick\u00fd vzor ETL (Extract, Transform, Load \u2014 \u201eextrakce, transformace, na\u010d\u00edt\u00e1n\u00ed\u201c). V n\u011bm obvykle v\u0161echny strany vym\u011b\u0148uj\u00ed v\u00fdhradn\u011b soubory: pou\u017e\u00edvaj\u00ed se velk\u00e1 data, kter\u00e1 nen\u00ed efektivn\u00ed pos\u00edlat jednotliv\u00fdmi dotazy. Mo\u017enost nativn\u00ed podpory p\u0159enosu soubor\u016f v Enterprise Service Mesh poskytuje pot\u0159ebnou flexibilitu pro podnik\u00e1n\u00ed.<\/p>\n<h3>Slu\u017eba orchestrace<\/h3>\n<p>\nVe velk\u00fdch organizac\u00edch t\u00e9m\u011b\u0159 v\u017edy existuj\u00ed r\u016fzn\u00e9 t\u00fdmy, kter\u00e9 vyv\u00edjej\u00ed r\u016fzn\u00e9 produkty. Nap\u0159\u00edklad v bance n\u011bkter\u00e9 t\u00fdmy pracuj\u00ed s vklady, zat\u00edmco jin\u00e9 se zab\u00fdvaj\u00ed \u00fav\u011brov\u00fdmi produkty, a takov\u00fdch p\u0159\u00edpad\u016f je dost. Jsou to r\u016fzn\u00ed lid\u00e9, r\u016fzn\u00e9 t\u00fdmy, kter\u00e9 vytv\u00e1\u0159ej\u00ed sv\u00e9 produkty, vyv\u00edjej\u00ed sv\u00e9 API a poskytuj\u00ed je ostatn\u00edm. A velmi \u010dasto vznik\u00e1 pot\u0159eba slo\u017eitosti t\u011bchto slu\u017eeb, stejn\u011b jako implementace slo\u017eit\u00e9 logiky sekven\u010dn\u00edho vol\u00e1n\u00ed sady API. Pro \u0159e\u0161en\u00ed tohoto probl\u00e9mu je zapot\u0159eb\u00ed \u0159e\u0161en\u00ed na integra\u010dn\u00edm vrstv\u011b, kter\u00e9 usnadn\u00ed celou tuto kompozi\u010dn\u00ed logiku (vol\u00e1n\u00ed n\u011bkolika API, popis trasy dotaz\u016f atd.). To je slu\u017eba orchestrace v Enterprise Service Mesh.<\/p>\n<h3>AI a ML<\/h3>\n<p>\nKdy\u017e mikroservisy komunikuj\u00ed p\u0159es jednotnou integra\u010dn\u00ed vrstvu, Service Mesh samoz\u0159ejm\u011b v\u00ed v\u0161e o vol\u00e1n\u00edch ka\u017ed\u00e9 slu\u017eby. Shroma\u017e\u010fujeme telemetrii: kdo koho volal, kdy, jak dlouho, kolikr\u00e1t a tak d\u00e1le. Kdy\u017e je t\u011bchto slu\u017eeb stovky tis\u00edc a vol\u00e1n\u00ed miliardy, v\u0161echno se to shroma\u017e\u010fuje a tvo\u0159\u00ed Big Data. Tyto \u00fadaje lze analyzovat pomoc\u00ed AI, strojov\u00e9ho u\u010den\u00ed atd., a pot\u00e9 na z\u00e1klad\u011b v\u00fdsledk\u016f anal\u00fdzy vytvo\u0159it n\u011bjak\u00e9 u\u017eite\u010dn\u00e9 v\u011bci. Bylo by vhodn\u00e9 alespo\u0148 \u010d\u00e1ste\u010dn\u011b p\u0159en\u00e9st um\u011bl\u00e9 inteligenci \u0159\u00edzen\u00ed cel\u00e9ho tohoto s\u00ed\u0165ov\u00e9ho provozu a vol\u00e1n\u00ed aplikac\u00ed integrovan\u00fdch do Service Mesh.<\/p>\n<h3>Slu\u017eba API Gateway (API br\u00e1na)<\/h3>\n<p>\nObecn\u011b v Service Mesh existuj\u00ed proxy a slu\u017eby, kter\u00e9 si vz\u00e1jemn\u011b volaj\u00ed uvnit\u0159 d\u016fv\u011brn\u00e9ho prostoru. Existuj\u00ed v\u0161ak i extern\u00ed partne\u0159i. Po\u017eadavky na API poskytovan\u00e9 t\u00e9to skupin\u011b z\u00e1kazn\u00edk\u016f jsou mnohem p\u0159\u00edsn\u011bj\u0161\u00ed. Tuto \u00falohu d\u011bl\u00edme na dv\u011b hlavn\u00ed \u010d\u00e1sti. <\/p>\n<ul>\n<li><i>Bezpe\u010dnost<\/i>. Ot\u00e1zky souvisej\u00edc\u00ed s ddos, zranitelnost\u00ed protokol\u016f, aplikac\u00ed, opera\u010dn\u00edch syst\u00e9m\u016f atd. \n<\/li>\n<li><i>M\u011b\u0159\u00edtka<\/i>. Kdy\u017e po\u010det API, kter\u00e9 je t\u0159eba poskytnout klient\u016fm, dosahuje tis\u00edc\u016f nebo dokonce stovek tis\u00edc, vznik\u00e1 pot\u0159eba n\u00e1stroje pro spr\u00e1vu t\u00e9to sady API. Je t\u0159eba neust\u00e1le sledovat API: zda funguj\u00ed, jak\u00fd maj\u00ed stav, jak\u00fd je na nich provoz, jak\u00e9 jsou statistiky atd. API br\u00e1na mus\u00ed tuto \u00falohu splnit, aby byl cel\u00fd proces \u0159\u00edzen\u00fd a bezpe\u010dn\u00fd. D\u00edky t\u00e9to komponent\u011b se Enterprise Service Mesh u\u010d\u00ed bez zbyte\u010dn\u00fdch slo\u017eitost\u00ed publikovat jak intern\u00ed API, tak extern\u00ed.\n<\/li>\n<\/ul>\n<p><\/p>\n<h3>Slu\u017eba podpory specifick\u00fdch protokol\u016f a datov\u00fdch form\u00e1t\u016f (br\u00e1na AS)<\/h3>\n<p>\nV sou\u010dasnosti v\u011bt\u0161ina \u0159e\u0161en\u00ed Service Mesh nativn\u011b pracuje pouze s provozem HTTP a HTTP2 nebo v omezen\u00e9m re\u017eimu na \u00farovni TCP\/IP. Enterprise Service Mesh m\u00e1 k dispozici \u0159adu dal\u0161\u00edch velmi specifick\u00fdch protokol\u016f pro p\u0159enos dat. N\u011bkter\u00e9 syst\u00e9my mohou pou\u017e\u00edvat zprost\u0159edkovatele zpr\u00e1v, jin\u00e9 jsou integrov\u00e1ny na \u00farovni datab\u00e1z\u00ed. Pokud m\u00e1 spole\u010dnost SAP, m\u016f\u017ee tak\u00e9 pou\u017e\u00edt vlastn\u00ed integra\u010dn\u00ed syst\u00e9m. A to v\u0161e funguje a je d\u016fle\u017eitou sou\u010d\u00e1st\u00ed podnik\u00e1n\u00ed.<\/p>\n<p>Nelze jednodu\u0161e \u0159\u00edct: \u201ePoj\u010fme se vzd\u00e1t legacy a vytvo\u0159it nov\u00e9 syst\u00e9my, kter\u00e9 budou schopny pou\u017e\u00edvat Service Mesh\u201c. Aby se v\u0161echny star\u00e9 syst\u00e9my sp\u0159\u00e1telily s nov\u00fdmi (na mikroservisn\u00ed architektu\u0159e), syst\u00e9my, kter\u00e9 mohou pou\u017e\u00edvat Service Mesh, pot\u0159ebuj\u00ed n\u011bjak\u00fd adapt\u00e9r, prost\u0159edn\u00edka, br\u00e1nu. P\u0159iznejte, bylo by skv\u011bl\u00e9, kdyby byl dod\u00e1v\u00e1n spole\u010dn\u011b se slu\u017ebou. Br\u00e1na AS pr\u00e1v\u011b m\u016f\u017ee podpo\u0159it jakoukoli mo\u017enost integrace. Jen si p\u0159edstavte, \u017ee prost\u011b nainstalujete Enterprise Service Mesh a je ji\u017e p\u0159ipravena komunikovat se v\u0161emi protokoly, kter\u00e9 pot\u0159ebujete. Tento p\u0159\u00edstup je pro n\u00e1s velmi d\u016fle\u017eit\u00fd.<\/p>\n<p><i>Takto si p\u0159edstavujeme podnikov\u00e9 \u0159e\u0161en\u00ed Service Mesh (Enterprise Service Mesh). Popsan\u00e1 customizace \u0159e\u0161\u00ed v\u011bt\u0161inu probl\u00e9m\u016f, kter\u00e9 se objevuj\u00ed p\u0159i pokusech o pou\u017eit\u00ed hotov\u00fdch open-source verz\u00ed integra\u010dn\u00ed platformy. Architektura Service Mesh, kter\u00e1 se objevila p\u0159ed pouh\u00fdmi dv\u011bma lety, pokra\u010duje ve v\u00fdvoji a jsme r\u00e1di, \u017ee m\u016f\u017eeme p\u0159isp\u011bt k jej\u00edmu rozvoji. Douf\u00e1me, \u017ee na\u0161e zku\u0161enosti budou pro v\u00e1s u\u017eite\u010dn\u00e9.<\/i><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/sberbank\/blog\/456136\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>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 [&hellip;]<\/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<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"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.\" \/>\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\/cs\/blog\/administrirovanie\/zachem-my-delaem-enterprise-service-mesh\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\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\u0417\u0430\u0447\u0435\u043c \u043c\u044b \u0434\u0435\u043b\u0430\u0435\u043c Enterprise Service Mesh | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"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.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/zachem-my-delaem-enterprise-service-mesh\" \/>\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:04:01+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:04:01+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\udd47Pro\u010d vytv\u00e1\u0159\u00edme Enterprise Service Mesh | ProHoster","description":"Service Mesh \u2014 zn\u00e1m\u00fd architektonick\u00fd vzor pro integraci mikroservis\u016f a p\u0159echod na cloudovou infrastrukturu. Dnes je v cloudu a kontejnerech velmi obt\u00ed\u017en\u00e9 se bez n\u011bj obej\u00edt.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/zachem-my-delaem-enterprise-service-mesh","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\u0417\u0430\u0447\u0435\u043c \u043c\u044b \u0434\u0435\u043b\u0430\u0435\u043c Enterprise Service Mesh | ProHoster","og:description":"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.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/zachem-my-delaem-enterprise-service-mesh","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:04:01+00:00","article:modified_time":"2019-10-31T19:04:01+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35388","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-01-21 23:01:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:04:24","updated":"2026-01-21 23:01:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=35388"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35388\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/26549"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=35388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=35388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=35388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}