{"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\/ro\/blog\/administrirovanie\/servisnaya-set-ploskost-dannyh-i-ploskosti-upravleniya-service-mesh-data-plane-vs-control-plane","title":{"rendered":"Re\u021bea de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanul de control\u201d (Service mesh data plane vs. control plane)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Salut, Habr! V\u0103 prezint traducerea articolului <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.envoyproxy.io\/service-mesh-data-plane-vs-control-plane-2774e720f7fc\">\u00abPlan de date vs plan de control \u00een re\u021belele de servicii\u00bb<\/a><\/noindex> autor <b>Matt Klein<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Re\u021bea de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanul de control\u201d (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/487456689eb832f9e3845966cb0d85d4.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDe data aceasta, am \u201evrut \u0219i am tradus\u201d descrierea ambelor componente ale re\u021belei de servicii, planul de date \u0219i planul de control. Aceast\u0103 descriere mi s-a p\u0103rut cea mai clar\u0103 \u0219i interesant\u0103 \u0219i, cel mai important, preg\u0103te\u0219te cititorul pentru \u00eentrebarea \u201eEste necesar\u0103 de fapt?\u201d.<\/p>\n<p>Deoarece conceptul de \u201eRe\u021bea de servicii (Service mesh)\u201d devine din ce \u00een ce mai popular \u00een ultimii doi ani (Articolul original din 10 octombrie 2017), iar num\u0103rul participan\u021bilor \u00een acest domeniu a crescut, am observat o confuzie propor\u021bional\u0103 \u00een cadrul \u00eentregului comunit\u0103\u021bii tehnice cu privire la modul de comparare \u0219i contrastare a diferitelor solu\u021bii.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nSitua\u021bia este cel mai bine descris\u0103 de urm\u0103toarele serii de tweet-uri pe care le-am scris \u00een iulie:<\/p>\n<blockquote><p>Confuzia cu re\u021beaua de servicii (service mesh) nr. 1: Linkerd ~ = Nginx ~ = Haproxy ~ = Envoy. Niciunul dintre acestea nu este egal cu Istio. Istio este ceva complet diferit. 1 \/<\/p><\/blockquote>\n<blockquote><p>Primele sunt pur \u0219i simplu plane de date (data planes). Ele singure nu fac nimic. Trebuie configurate pentru ceva mai mare. 2 \/<\/p><\/blockquote>\n<blockquote><p>Istio este un exemplu de plan de control (control plane) care leag\u0103 p\u0103r\u021bile \u00eempreun\u0103. Este un alt strat. \/sf\u00e2r\u0219it<\/p><\/blockquote>\n<p>\u00cen tweet-urile anterioare sunt men\u021bionate c\u00e2teva proiecte diferite (Linkerd, NGINX, HAProxy, Envoy \u0219i Istio), dar, mai important, sunt introduse conceptele generale ale planului de date (data plane), re\u021belei de servicii (service mesh) \u0219i planului de control (control plane). \u00cen aceast\u0103 postare, voi face un pas \u00eenapoi \u0219i voi explica ce \u00een\u021beleg prin termenii \u201eplan de date (data plane)\u201d \u0219i \u201eplan de control (control plane)\u201d la un nivel foarte \u00eenalt, apoi voi explica modul \u00een care ace\u0219ti termeni se raporteaz\u0103 la proiectele men\u021bionate \u00een tweet-uri.<\/p>\n<h1>Ce este, de fapt, re\u021beaua de servicii (What is a service mesh, really)?<\/h1>\n<p>\n<img decoding=\"async\" alt=\"Re\u021bea de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanul de control\u201d (Service mesh data plane vs. control plane)\" src=\"\/wp-content\/uploads\/2019\/08\/63c195aa9bcb7080f6924cecbff0fbc1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Imaginea 1: Prezentarea general\u0103 a re\u021belei de servicii (Service mesh overview)<\/b><\/p>\n<p><b>Figura 1<\/b> ilustreaz\u0103 conceptul re\u021belei de servicii (service mesh) la cel mai de baz\u0103 nivel. Exist\u0103 patru clustere de servicii (A-D). Fiecare instan\u021b\u0103 de serviciu este conectat\u0103 la un server proxy local. Tot traficul de re\u021bea (HTTP, REST, gRPC, Redis etc.) de la o instan\u021b\u0103 separat\u0103 a aplica\u021biei este trimis prin serverul proxy local c\u0103tre clusterele de servicii externe corespunz\u0103toare. Astfel, instan\u021ba aplica\u021biei nu \u0219tie despre re\u021bea \u00een \u00eentregul ei \u0219i \u0219tie doar despre propriul s\u0103u proxy local. De fapt, re\u021beaua sistemului distribuit a fost ascuns\u0103 de serviciu.<\/p>\n<h1>Plan de date (Data plane)<\/h1>\n<p>\n\u00cen re\u021beaua de servicii (service mesh), serverul proxy situat local pentru aplica\u021bie \u00eendepline\u0219te urm\u0103toarele sarcini:<\/p>\n<ul>\n<li> <b>Descoperirea serviciilor (Service discovery)<\/b>. Ce servicii \/ aplica\u021bii sunt disponibile pentru aplica\u021bia dumneavoastr\u0103?<\/li>\n<li><b>Verificarea s\u0103n\u0103t\u0103\u021bii (Health checking)<\/b>. Exemplarele serviciilor returnate de descoperirea serviciilor (service discovery) sunt func\u021bionale \u0219i sunt preg\u0103tite s\u0103 accepte trafic de re\u021bea? Acest lucru poate include at\u00e2t verific\u0103ri active (de exemplu, verificarea r\u0103spunsului \/ healthcheck), c\u00e2t \u0219i verific\u0103ri passive (de exemplu, utiliz\u00e2nd 3 erori 5xx consecutive ca indiciu al unui statut de s\u0103n\u0103tate nesatisf\u0103c\u0103tor al serviciului). <\/li>\n<li><b>Rutare (Routing)<\/b>. Dup\u0103 primirea unei solicit\u0103ri REST c\u0103tre &#171;\\\/foo&#187;, \u00een ce cluster de servicii ar trebui s\u0103 se trimit\u0103 solicitarea? <\/li>\n<li> <b>Balansarea \u00eenc\u0103rc\u0103turii (Load balancing)<\/b>. Dup\u0103 ce, \u00een timpul rut\u0103rii, a fost ales un cluster de servicii, \u00een ce exemplar de serviciu ar trebui s\u0103 fie trimis\u0103 cererea? Cu ce timeout? Cu ce set\u0103ri de \u00eentrerupere a circuitului (circuit breaking)? Dac\u0103 cererea nu a reu\u0219it, ar trebui s\u0103 fie repetat\u0103?<\/li>\n<li> <b>Autentificare \u0219i autorizare (Authentication and authorization)<\/b>. Pentru cererile \u00een incoming, poate serviciul apelant s\u0103 fie identificat\/autorized criptografic prin mTLS sau printr-un alt mecanism? Dac\u0103 este identificat\/autorized, i se permite s\u0103 invoce opera\u021bia solicitat\u0103 (endpoint) \u00een serviciu sau ar trebui s\u0103 fie returnat un r\u0103spuns neautentificat?<\/li>\n<li> <b>Observabilitate (Observability)<\/b>. Pentru fiecare cerere, trebuie generate date statistice detaliate, jurnale \u0219i date de trasare distribuit\u0103, astfel \u00eenc\u00e2t operatorii s\u0103 poat\u0103 \u00een\u021belege fluxul de trafic distribuit \u0219i problemele de depanare pe m\u0103sur\u0103 ce acestea apar.<\/li>\n<\/ul>\n<p>\nPentru toate punctele anterioare din re\u021beaua de servicii (service mesh), r\u0103spunde planul de date (data plane). Practic, proxy-ul local pentru serviciu (sidecar) este planul de date (data plane). Cu alte cuvinte, planul de date (data plane) se ocup\u0103 de translatia condi\u021bional\u0103, redirec\u021bionarea \u0219i observarea fiec\u0103rui pachet de re\u021bea care este trimis c\u0103tre un serviciu sau de la acesta.<\/p>\n<h1>Planul de control (The control plane)<\/h1>\n<p>\nAbstrac\u021bia de re\u021bea pe care o ofer\u0103 proxy-ul local \u00een planul de date este magic\u0103 (?). Cu toate acestea, cum afl\u0103 proxy-ul \u00een mod efectiv despre ruta &#171;\\\/foo&#187; c\u0103tre serviciul B? Cum pot fi utilizate datele de descoperire a serviciilor (service discovery), care sunt completate de solicit\u0103rile proxy-ului? Cum sunt configurate op\u021biunile de echilibrare a \u00eenc\u0103rc\u0103rii, timeout, ruperea circuitului (circuit breaking) etc.? Cum se desf\u0103\u0219oar\u0103 desf\u0103\u0219urarea aplica\u021biei utiliz\u00e2nd metoda albastr\u0103\/verzuie (blue\/green) sau metoda de transfer treptat a traficului? Cine configureaz\u0103 parametrii de autentificare \u0219i autorizare a sistemului comun?<\/p>\n<p>Toate punctele men\u021bionate mai sus se afl\u0103 \u00een gestionarea planului de control (control plane) al re\u021belei de servicii (service mesh). <i>Planul de control (control plane) prime\u0219te un set de proxy-uri izolate,<a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/server\/\"   title=\"servere\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1348\">servere<\/a> f\u0103r\u0103 stare \u0219i le transform\u0103 \u00eentr-un sistem distribuit<\/i>.<\/p>\n<p>Cred c\u0103 motivul pentru care mul\u021bi tehnologi g\u0103sesc confuze conceptele distincte ale planului de date (data plane) \u0219i ale planului de control (control plane) este c\u0103, pentru majoritatea oamenilor, planul de date este familiar, \u00een timp ce planul de control este str\u0103in\/neclar. Lucr\u0103m de mult timp cu routere \u0219i comutatoare de re\u021bea fizice. \u00cen\u021belegem c\u0103 pachetele\/solicit\u0103rile trebuie s\u0103 ajung\u0103 din punctul A \u00een punctul B \u0219i ce hardware \u0219i software putem folosi pentru aceasta. Noua genera\u021bie de proxy-uri software sunt doar versiuni la mod\u0103 ale uneltelor pe care le-am folosit de mult timp.<\/p>\n<p><img decoding=\"async\" alt=\"Re\u021bea de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanul de control\u201d (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: Planul de control uman (Human control plane)<\/b><\/p>\n<p>Cu toate acestea, am folosit planuri de control (control plane) de mult timp, de\u0219i majoritatea operatorilor de re\u021bea ar putea s\u0103 nu asocieze aceast\u0103 parte a sistemului cu vreun component tehnologic. Motivul este simplu:<br \/>\n<b>Majoritatea planurilor de control (control plane) utilizate ast\u0103zi sunt\u2026 noi<\/b>.<\/p>\n<p>Pe <b>\u00een figura 2<\/b> Aici este prezentat\u0103 ceea ce numesc \u00abPlanul de control uman (Human control plane)\u00bb. \u00cen acest tip de desf\u0103\u0219urare, care este \u00eenc\u0103 foarte frecvent \u00eent\u00e2lnit, un operator uman, probabil mai nervos, creeaz\u0103 configura\u021bii statice - poten\u021bial cu ajutorul scripturilor - \u0219i le desf\u0103\u0219oar\u0103 printr-un proces special pe toate serverele proxy. Apoi, proxy-urile \u00eencep s\u0103 foloseasc\u0103 aceast\u0103 configura\u021bie \u0219i \u00eencep s\u0103 proceseze planul de date (data plane) folosind set\u0103rile actualizate.<\/p>\n<p><img decoding=\"async\" alt=\"Re\u021bea de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanul de control\u201d (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: Planul de control avansat al re\u021belei de servicii (Advanced service mesh control plane)<\/b><\/p>\n<p>Pe <b>\u00een figura 3<\/b> este prezentat \u00abplanul de control extins (control plane)\u00bb al re\u021belei de servicii (service mesh). Acesta este compus din urm\u0103toarele p\u0103r\u021bi:<\/p>\n<ul>\n<li> <b>Omul (The human)<\/b>: Exist\u0103 \u00eenc\u0103 un om (sper\u0103m, mai pu\u021bin nervos) care ia decizii la un nivel \u00eenalt cu privire la \u00eentreaga sistem.<\/li>\n<li><b>Interfa\u021ba utilizatorului a planului de control (Control plane UI)<\/b>: Omul interac\u021bioneaz\u0103 cu un anumit tip de interfa\u021b\u0103 utilizator pentru a gestiona sistemul. Aceasta poate fi un portal web, o aplica\u021bie de linie de comand\u0103 (CLI) sau o alt\u0103 interfa\u021b\u0103. Prin intermediul interfe\u021bei utilizator, operatorul are acces la parametrii globali de configurare ai sistemului, cum ar fi:\n<ul>\n<li>Gestionarea desf\u0103\u0219ur\u0103rii, albastru \/ verde (blue \/ green) \u0219i \/ sau trecerea gradual\u0103 a traficului <\/li>\n<li>Parametrii de autentificare \u0219i autorizare <\/li>\n<li>Specifica\u021biile tabelei de rutare, de exemplu, c\u00e2nd aplica\u021bia A solicit\u0103 informa\u021bii despre &#171;\\\/foo&#187;, ce se \u00eent\u00e2mpl\u0103 <\/li>\n<li>Set\u0103rile balancerului de sarcin\u0103, cum ar fi delay-urile (timeouts), \u00eencerc\u0103rile repetate (retries), parametrii pentru \u00eentreruperea circuitului (circuit breaking) etc. <\/li>\n<\/ul>\n<\/li>\n<li> <b>Programul de lucru (Workload scheduler)<\/b>: Serviciile sunt desf\u0103\u0219urate \u00een infrastructur\u0103 printr-un sistem de planificare \/ orchestrare de un anumit tip, de exemplu, Kubernetes sau Nomad. Programul este responsabil de \u00eenc\u0103rcarea serviciului \u00eempreun\u0103 cu proxy-ul s\u0103u local.<\/li>\n<li> <b>Descoperirea serviciului (Service discovery)<\/b>. C\u00e2nd programul de lucru porne\u0219te \u0219i opre\u0219te instan\u021bele de serviciu, el raporteaz\u0103 starea de func\u021bionare \u00een sistemul de descoperire a serviciului.<\/li>\n<li> <b>API-urile de configurare ale proxy-ului local (Sidecar proxy configuration APIs) <\/b>: Serverele proxy locale extrag dinamic starea din diferite componente ale sistemului conform modelului \u00abconsisten\u021b\u0103 pe termen lung\u00bb (eventually consistent) f\u0103r\u0103 interven\u021bia operatorului. \u00centreaga sistem\u0103, format\u0103 din toate instan\u021bele de servicii \u0219i serverele proxy locale \u00een func\u021biune, converge \u00een cele din urm\u0103 \u00eentr-o ecosistem\u0103. API-ul planei de date (data plane) din Envoy este un exemplu de cum func\u021bioneaz\u0103 acest lucru \u00een practic\u0103.<\/li>\n<\/ul>\n<p>\nPractic, scopul planei de control (control plane) este de a stabili o politic\u0103 care va fi adoptat\u0103 \u00een cele din urm\u0103 de planul de date (data plane). Planele de control (control planes) mai avansate elimin\u0103 mai multe detalii din sarcina operatorului \u0219i necesit\u0103 mai pu\u021bin management manual, cu condi\u021bia s\u0103 func\u021bioneze corect!...<\/p>\n<h1>Plana de date \u0219i plana de control. Rezumat (Data plane vs. control plane summary)<\/h1>\n<p><\/p>\n<ul>\n<li> <b>Plana de date a re\u021belei de servicii (Service mesh data plane)<\/b>: implic\u0103 fiecare pachet \/ cerere din sistem. Este responsabil\u0103 pentru descoperirea aplica\u021biilor \/ serviciilor, verificarea disponibilit\u0103\u021bii, rutarea, distribu\u021bia \u00eenc\u0103rc\u0103turii, autentificarea \/ autorizarea \u0219i observabilitatea.<\/li>\n<li> <b>Plana de control a re\u021belei de servicii (Service mesh control plane)<\/b>: ofer\u0103 politici \u0219i configura\u021bii pentru toate planurile de date active din re\u021beaua de servicii. Nu intervine \u00een pachetele \/ cererile din sistem. Plana de control transform\u0103 toate planurile de date \u00eentr-un sistem distribuit.<\/li>\n<\/ul>\n<p><\/p>\n<h1>Starea actual\u0103 a proiectului (Current project landscape)<\/h1>\n<p>\nDup\u0103 ce am explicat cele de mai sus, s\u0103 ne uit\u0103m la starea actual\u0103 a proiectului \u00abre\u021belei de servicii (service mesh)\u00bb.<\/p>\n<ul>\n<li> <b>Planele de date (Data planes)<\/b>: Linkerd, NGINX, HAProxy, Envoy, Traefik<\/li>\n<li><b>Planele de control (Control planes)<\/b>: Istio, Nelson, SmartStack <\/li>\n<\/ul>\n<p>\n\u00cen loc s\u0103 fac o analiz\u0103 detaliat\u0103 a fiec\u0103rei dintre solu\u021biile men\u021bionate mai sus, voi aborda pe scurt c\u00e2teva aspecte care, \u00een opinia mea, genereaz\u0103 cea mai mare parte a confuziei \u00een ecosistemul actual.<\/p>\n<p>La \u00eenceputul anului 2016, Linkerd a fost unul dintre primele servere proxy pentru planul de date (data plane) pentru re\u021belele de servicii (service mesh) \u0219i a realizat o treab\u0103 fantastic\u0103 \u00een cre\u0219terea con\u0219tientiz\u0103rii \u0219i atragerea aten\u021biei asupra modelului de proiectare \u201ere\u021bea de servicii\u201d (service mesh). Aproximativ \u0219ase luni mai t\u00e2rziu, Envoy s-a al\u0103turat Linkerd (de\u0219i lucra la Lyft din sf\u00e2r\u0219itul anului 2015). Linkerd \u0219i Envoy sunt dou\u0103 proiecte care sunt adesea men\u021bionate \u00een discu\u021biile despre re\u021belele de servicii (service mesh).<\/p>\n<p>Istio a fost anun\u021bat \u00een mai 2017. Obiectivele proiectului Istio sunt foarte asem\u0103n\u0103toare cu planul extins de control (control plane) ar\u0103tat la <b>\u00een figura 3<\/b>. Envoy pentru Istio este serverul proxy \u201eimplicit\u201d. Astfel, Istio este planul de control (control plane), iar Envoy este planul de date (data plane). \u00cen scurt timp, Istio a generat mult\u0103 agita\u021bie, iar alte planuri de date (data plane) au \u00eenceput integrarea ca \u00eenlocuitor pentru Envoy (at\u00e2t Linkerd, c\u00e2t \u0219i NGINX au demonstrat integrarea cu Istio). Faptul c\u0103 \u00eentr-un singur plan de control (control plane) se pot utiliza diferite planuri de date (data plane) \u00eenseamn\u0103 c\u0103 planul de control (control plane) \u0219i planul de date (data plane) nu sunt neap\u0103rat str\u00e2ns legate. Un API, cum ar fi API-ul universal pentru planul de date (data plane) Envoy, poate forma un pod \u00eentre cele dou\u0103 p\u0103r\u021bi ale sistemului.<\/p>\n<p>Nelson \u0219i SmartStack ajut\u0103 la ilustrarea suplimentar\u0103 a separ\u0103rii planului de control (control plane) \u0219i a planului de date (data plane). Nelson folose\u0219te Envoy ca server proxy \u0219i construie\u0219te un plan de control (control plane) fiabil pentru re\u021beaua de servicii (service mesh) bazat\u0103 pe stiva HashiCorp, adic\u0103 Nomad etc. SmartStack a fost, poate, primul dintr-o nou\u0103 genera\u021bie de re\u021bele de servicii (service mesh). SmartStack formeaz\u0103 un plan de control (control plane) \u00een jurul HAProxy sau NGINX, demonstr\u00e2nd capacitatea decupl\u0103rii planului de control (control plane) de re\u021beaua de servicii (service mesh) \u0219i a planului de date (data plane).<\/p>\n<p>Arhitectura microserviciilor cu re\u021bea de servicii (service mesh) atrage din ce \u00een ce mai mult\u0103 aten\u021bie (corect!), iar din ce \u00een ce mai multe proiecte \u0219i furnizori \u00eencep s\u0103 lucreze \u00een aceast\u0103 direc\u021bie. \u00cen urm\u0103torii c\u00e2\u021biva ani, vom vedea multe inova\u021bii at\u00e2t \u00een planurile de date (data plane), c\u00e2t \u0219i \u00een planurile de control (control plane), precum \u0219i o mai mare integrare a diverselor componente. \u00cen cele din urm\u0103, arhitectura microserviciilor ar trebui s\u0103 devin\u0103 mai transparent\u0103 \u0219i magic\u0103 (?) pentru operator.<br \/>\nSper c\u0103 devin tot mai pu\u021bin enervant.<\/p>\n<h1>Punctele cheie (Key takeaways)<\/h1>\n<p><\/p>\n<ul>\n<li> Re\u021beaua de servicii (service mesh) este alc\u0103tuit\u0103 din dou\u0103 p\u0103r\u021bi distincte: planul de date (data plane) \u0219i planul de control (control plane). Ambele componente sunt esen\u021biale, f\u0103r\u0103 ele sistemul nu va func\u021biona.<\/li>\n<li>Toat\u0103 lumea este familiarizat\u0103 cu planul de control (control plane), iar \u00een acest moment planul de control (control plane) ai putea fi chiar tu! <\/li>\n<li>Toate planurile de date (data plane) concureaz\u0103 \u00eentre ele \u00een ceea ce prive\u0219te func\u021bionalit\u0103\u021bile, performan\u021ba, configurabilitatea \u0219i scalabilitatea. <\/li>\n<li> Toate planurile de control (control plane) concureaz\u0103 \u00eentre ele \u00een func\u021bionalit\u0103\u021bi, configurabilitate, scalabilitate \u0219i u\u0219urin\u021ba \u00een utilizare.<\/li>\n<li>Un plan de control (control plane) poate con\u021bine abstrac\u021bii \u0219i API-uri corecte pentru a permite utilizarea mai multor planuri de date (data plane). <\/li>\n<\/ul>\n<p>Sursa: <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.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440!\" \/>\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\/ro\/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.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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!\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/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\udd47Re\u021beaua de servicii, \u201ePlanul de date\u201d \u0219i \u201ePlanurile de control\u201d (Service mesh data plane vs. control plane) | ProHoster","description":"Salut, Habr!","canonical_url":"https:\/\/prohoster.info\/ro\/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":"ro_RO","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!","og:url":"https:\/\/prohoster.info\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/37030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=37030"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37030\/revisions"}],"predecessor-version":[{"id":158592,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37030\/revisions\/158592"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27757"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}