{"id":97706,"date":"2020-10-21T02:42:26","date_gmt":"2020-10-21T00:42:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/pochemu-besservernaya-revolyucziya-zashla-v-tupik"},"modified":"2020-10-21T02:42:26","modified_gmt":"2020-10-21T00:42:26","slug":"pochemu-besservernaya-revolyucziya-zashla-v-tupik","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-besservernaya-revolyucziya-zashla-v-tupik","title":{"rendered":"De ce revolu\u021bia f\u0103r\u0103 server a ajuns \u00eentr-un impas","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<h4>Punctele cheie<\/h4>\n<p><\/p>\n<ul>\n<li>De c\u00e2\u021biva ani ni se promite c\u0103 calculul serverless va deschide o nou\u0103 er\u0103 f\u0103r\u0103 un sistem de operare specific pentru rularea aplica\u021biilor. Ni s-a spus c\u0103 o astfel de structur\u0103 va rezolva numeroase probleme de scalabilitate. \u00cen realitate, lucrurile stau diferit.\n<\/li>\n<li>De\u0219i mul\u021bi consider\u0103 tehnologia serverless o idee nou\u0103, r\u0103d\u0103cinile acesteia pot fi urm\u0103rite p\u00e2n\u0103 \u00een 2006, c\u00e2nd au ap\u0103rut Zimki PaaS \u0219i Google App Engine - ambele utilizeaz\u0103 o arhitectur\u0103 serverless.\n<\/li>\n<li>Exist\u0103 patru motive pentru care revolu\u021bia serverless a ajuns \u00eentr-un impas: de la suportul limitat pentru limbajele de programare p\u00e2n\u0103 la problemele de performan\u021b\u0103.\n<\/li>\n<li>Calculul serverless nu este at\u00e2t de inutil. Deloc. Cu toate acestea, nu ar trebui considerat o \u00eenlocuire direct\u0103 a serverelor. Pentru unele aplica\u021bii, poate fi un instrument util.<\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>Serverul este mort, tr\u0103iasc\u0103 serverul!<\/h1>\n<p>\nA\u0219a sun\u0103 strig\u0103tul de r\u0103zboi al sus\u021bin\u0103torilor revolu\u021biei serverless. Este suficient s\u0103 arunc\u0103m o privire rapid\u0103 asupra presei din domeniu din ultimii c\u00e2\u021biva ani pentru a ajunge u\u0219or la concluzia c\u0103 modelul tradi\u021bional de server este mort \u0219i c\u0103, \u00een c\u00e2\u021biva ani, to\u021bi ne vom folosi de arhitecturi serverless.<\/p>\n<p>A\u0219a cum \u0219tie oricine din domeniu \u0219i a\u0219a cum am subliniat \u0219i \u00een articolul nostru despre <noindex><a rel=\"nofollow\" href=\"https:\/\/www.infoq.com\/presentations\/state-serverless-computing\/\">starea calculului serverless<\/a><\/noindex>, nu este a\u0219a. \u00cen ciuda numeroaselor articole despre beneficiile <noindex><a rel=\"nofollow\" href=\"https:\/\/datafloq.com\/read\/7-reasons-serverless-computing-revolution-cloud\/2871\">revolu\u021biei serverless<\/a><\/noindex>, aceasta nu a avut loc. De fapt, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.infoq.com\/news\/2020\/06\/oreilly-cloud-report\/\">cercet\u0103rile recente arat\u0103<\/a><\/noindex>, c\u0103 aceast\u0103 revolu\u021bie a ajuns, probabil, \u00eentr-un impas.<\/p>\n<p>Unele dintre promisiunile pentru modelele serverless au fost, f\u0103r\u0103 \u00eendoial\u0103, realizate, dar nu toate. Departe de toate.<\/p>\n<p>\u00cen acest articol vreau s\u0103 discut despre motivele unei astfel de situa\u021bii. De ce lipsa de flexibilitate a modelelor serverless r\u0103m\u00e2ne \u00een continuare un obstacol pentru adop\u021bia lor mai larg\u0103, de\u0219i continu\u0103 s\u0103 fie utile \u00een circumstan\u021be specifice \u0219i bine definite.<\/p>\n<h1>Ce promiteau sus\u021bin\u0103torii calculului serverless<\/h1>\n<p>\n\u00cenainte de a trece la problemele calculului serverless, haide\u021bi s\u0103 vedem ce ar fi trebuit s\u0103 ofere. <noindex><a rel=\"nofollow\" href=\"https:\/\/radon-h2020.eu\/2019\/10\/11\/serverless-revolution-radon\/\">Promisiunile revolu\u021biei serverless<\/a><\/noindex> au fost numeroase \u0219i - uneori - foarte ambi\u021bioase.<\/p>\n<p>Pentru cei care nu sunt familiariza\u021bi cu termenul, iat\u0103 o defini\u021bie scurt\u0103. Calculul f\u0103r\u0103 server define\u0219te o arhitectur\u0103 \u00een care aplica\u021biile (sau p\u0103r\u021bi ale aplica\u021biilor) sunt executate la cerere \u00een medii de execu\u021bie care sunt de obicei g\u0103zduite de la distan\u021b\u0103. \u00cen plus, sistemele f\u0103r\u0103 server pot fi g\u0103zduite \u0219i local. \u00cen ultimii c\u00e2\u021biva ani, construc\u021bia de sisteme durabile f\u0103r\u0103 server a fost principala preocupare a administratorilor de sistem \u0219i a companiilor SaaS, deoarece (se sus\u021bine) aceast\u0103 arhitectur\u0103 ofer\u0103 c\u00e2teva avantaje cheie comparativ cu modelul \u201etradi\u021bional\u201d client-server:<\/p>\n<ol>\n<li>Modelele f\u0103r\u0103 server nu necesit\u0103 ca utilizatorii s\u0103 \u00ee\u0219i men\u021bin\u0103 propriile sisteme de operare sau chiar s\u0103 dezvolte aplica\u021bii compatibile cu anumite OS-uri. \u00cen schimb, dezvoltatorii creeaz\u0103 cod comun, \u00eel \u00eencarc\u0103 pe o platform\u0103 f\u0103r\u0103 server \u0219i monitorizeaz\u0103 execu\u021bia acestuia.\n<\/li>\n<li>Resursele din cadrele f\u0103r\u0103 server sunt de obicei pl\u0103tite pe minute (sau chiar pe secunde). Aceasta \u00eenseamn\u0103 c\u0103 clien\u021bii pl\u0103tesc doar pentru timpul \u00een care codul este efectiv executat. Aceasta este o diferen\u021b\u0103 semnificativ\u0103 fa\u021b\u0103 de VM-ul tradi\u021bional \u00een cloud, unde ma\u0219ina st\u0103 de cele mai multe ori inactiv\u0103, dar pentru care trebuie pl\u0103tit.\n<\/li>\n<li>Problema scalabilit\u0103\u021bii a fost, de asemenea, rezolvat\u0103. Resursele din cadrele f\u0103r\u0103 server sunt alocate dinamic, astfel \u00eenc\u00e2t sistemul poate gestiona cu u\u0219urin\u021b\u0103 v\u00e2rfurile bru\u0219te de cerere.<\/li>\n<\/ol>\n<p>\nPe scurt, modelele f\u0103r\u0103 server ofer\u0103 solu\u021bii flexibile, ieftine \u0219i scalabile. Este surprinz\u0103tor c\u0103 nu ne-am g\u00e2ndit la aceast\u0103 idee mai devreme.<\/p>\n<h1>Este aceasta \u00eentr-adev\u0103r o idee nou\u0103?<\/h1>\n<p>\nDe fapt, ideea nu este nou\u0103. Conceptul care permite utilizatorilor s\u0103 pl\u0103teasc\u0103 doar pentru timpul \u00een care codul este efectiv executat exist\u0103 de c\u00e2nd a fost introdus \u00een cadrul <noindex><a rel=\"nofollow\" href=\"https:\/\/www.slideshare.net\/swardley\/zimki-2006\">Zimki PaaS<\/a><\/noindex> \u00een 2006, \u0219i cam \u00een acea perioad\u0103 Google App Engine a propus o solu\u021bie foarte similar\u0103.<\/p>\n<p>De fapt, ceea ce numim acum modelul \u201ef\u0103r\u0103 server\u201d este mai vechi dec\u00e2t multe tehnologii care sunt acum considerate \u201enative cloud\u201d \u0219i care ofer\u0103 practic acela\u0219i lucru. A\u0219a cum s-a men\u021bionat, modelele f\u0103r\u0103 server sunt, \u00een esen\u021b\u0103, doar o continuare a modelului de afaceri SaaS, care exist\u0103 de c\u00e2teva decenii.<\/p>\n<p>De asemenea, este important de recunoscut c\u0103 modelul serverless nu este o arhitectur\u0103 FaaS, de\u0219i \u00eentre ele exist\u0103 o leg\u0103tur\u0103. FaaS este, \u00een esen\u021b\u0103, partea orientat\u0103 pe computa\u021bie a arhitecturii serverless, dar nu reprezint\u0103 \u00eentreaga sistem\u0103.<\/p>\n<p>Deci, de ce toat\u0103 aceast\u0103 agita\u021bie? Ei bine, pe m\u0103sur\u0103 ce viteza de penetrare a internetului \u00een \u021b\u0103rile \u00een dezvoltare continu\u0103 s\u0103 creasc\u0103 rapid, cererea de resurse de calcul cre\u0219te de asemenea. De exemplu, \u00een multe \u021b\u0103ri cu sectoare de comer\u021b electronic \u00een rapid\u0103 expansiune, pur \u0219i simplu nu exist\u0103 infrastructur\u0103 de calcul pentru aplica\u021biile de pe aceste platforme. Aici intervine utilizarea platformelor serverless pl\u0103tite.<\/p>\n<h1>Problemele modelului serverless<\/h1>\n<p>\nProblema este c\u0103 modelele serverless au... probleme. Nu m\u0103 \u00een\u021belege\u021bi gre\u0219it: nu spun c\u0103 sunt proaste \u00een sine sau c\u0103 nu ofer\u0103 o valoare semnificativ\u0103 pentru unele companii \u00een anumite circumstan\u021be. Dar afirmarea principal\u0103 a \u00abrevolu\u021biei\u00bb \u2014 c\u0103 arhitectura serverless va \u00eenlocui rapid tradi\u021bionala \u2014 nu se va realiza niciodat\u0103.<\/p>\n<p>Iat\u0103 de ce.<\/p>\n<h3>Suport limitat pentru limbajele de programare<\/h3>\n<p>\nMajoritatea platformelor serverless permit rularea doar a aplica\u021biilor scrise \u00een anumite limbaje. Acest lucru limiteaz\u0103 grav flexibilitatea \u0219i adaptabilitatea acestor sisteme.<\/p>\n<p>Se consider\u0103 c\u0103 platformele serverless suport\u0103 majoritatea limbajelor de baz\u0103. AWS Lambda \u0219i Azure Functions ofer\u0103, de asemenea, un wrapper pentru rularea aplica\u021biilor \u0219i func\u021biilor \u00een limbaje nesuportate, de\u0219i acest lucru vine adesea cu costuri de performan\u021b\u0103. Deci, pentru majoritatea organiza\u021biilor, de obicei, aceast\u0103 limitare nu conteaz\u0103 prea mult. Dar iat\u0103 \u00een ce const\u0103 problema. Se presupune c\u0103 unul dintre avantajele modelelor serverless este c\u0103 aplica\u021biile mai pu\u021bin cunoscute, folosite rar, pot fi utilizate mai ieftin, deoarece pl\u0103ti\u021bi doar pentru timpul lor de execu\u021bie. \u0218i aplica\u021biile mai pu\u021bin cunoscute, folosite rar, sunt adesea scrise \u00een... limbaje de programare mai pu\u021bin cunoscute, folosite rar.<\/p>\n<p>Aceasta submineaz\u0103 unul dintre avantajele cheie ale modelului serverless.<\/p>\n<h3>Leg\u0103tura cu furnizorul<\/h3>\n<p>\nA doua problem\u0103 cu platformele f\u0103r\u0103 servere sau, cel pu\u021bin, cu modul \u00een care sunt implementate \u00een prezent, este c\u0103 acestea nu sunt de obicei asem\u0103n\u0103toare una cu cealalt\u0103 la nivel opera\u021bional. Exist\u0103 practic nicio standardizare \u00een ceea ce prive\u0219te scrierea func\u021biilor, implementarea \u0219i gestionarea. Aceasta \u00eenseamn\u0103 c\u0103 migrarea func\u021biilor de pe o platform\u0103 pe alta dureaz\u0103 extrem de mult timp.<\/p>\n<p>Cea mai dificil\u0103 parte a trecerii la un model f\u0103r\u0103 server este c\u0103 nu sunt func\u021biile de calcul, care de obicei sunt doar fragmente de cod, ci modul \u00een care aplica\u021biile sunt legate de sistemele conectate, cum ar fi stocarea obiectelor, gestionarea identit\u0103\u021bii \u0219i cozile. Func\u021biile pot fi mutate, dar restul aplica\u021biei nu poate. Aceasta este o opozi\u021bie total\u0103 fa\u021b\u0103 de platformele ieftine \u0219i flexibile promise.<\/p>\n<p>Unii sus\u021bin c\u0103 modelele f\u0103r\u0103 server au ap\u0103rut recent \u0219i c\u0103 nu a fost timpul necesar pentru a le standardiza func\u021bionarea. Dar ele nu sunt at\u00e2t de noi, a\u0219a cum am men\u021bionat mai sus, iar multe alte tehnologii cloud, precum containerele, au devenit deja mult mai convenabile datorit\u0103 dezvolt\u0103rii \u0219i implement\u0103rii pe scar\u0103 larg\u0103 a unor bune standarde.<\/p>\n<h3>Performan\u021b\u0103<\/h3>\n<p>\nPerforman\u021ba de calcul a platformelor f\u0103r\u0103 server este greu de m\u0103surat, \u00een parte deoarece furnizorii caut\u0103 s\u0103 p\u0103streze informa\u021biile secrete. Majoritatea sus\u021bine c\u0103 func\u021biile de pe platformele externe, f\u0103r\u0103 server, func\u021bioneaz\u0103 la fel de repede ca cele de pe serverele interne, cu c\u00e2teva probleme inevitabile de laten\u021b\u0103.<\/p>\n<p>Cu toate acestea, unele fapte indic\u0103 contrariul. Func\u021biile care nu au rulat anterior pe o anumit\u0103 platform\u0103 sau care nu au rulat de ceva vreme necesit\u0103 timp pentru a se ini\u021bializa. Probabil, acest lucru se datoreaz\u0103 faptului c\u0103 codul lor a fost mutat pe un suport de date mai pu\u021bin accesibil, de\u0219i, a\u0219a cum este cazul benchmark-urilor, majoritatea furnizorilor nu v\u0103 vor spune despre mutarea datelor.<\/p>\n<p>Desigur, exist\u0103 c\u00e2teva modalit\u0103\u021bi de a o ocoli. Una dintre ele const\u0103 \u00een optimizarea func\u021biilor pentru orice limbaj cloud pe care func\u021bioneaz\u0103 platforma dumneavoastr\u0103 f\u0103r\u0103 server, dar aceasta submineaz\u0103 oarecum afirma\u021bia c\u0103 aceste platforme sunt \u201eflexibile.\u201d<\/p>\n<p>O alt\u0103 abordare const\u0103 \u00een asigurarea desf\u0103\u0219ur\u0103rii regulate a programelor esen\u021biale pentru performan\u021b\u0103, astfel \u00eenc\u00e2t acestea s\u0103 r\u0103m\u00e2n\u0103 \u201efreshe\u201d. Aceast\u0103 a doua abordare, desigur, contravine \u00eentr-o oarecare m\u0103sur\u0103 afirma\u021biei c\u0103 platformele serverless sunt mai economice, deoarece pl\u0103te\u0219ti doar pentru timpul de func\u021bionare al programelor tale. Furnizorii de cloud au implementat modalit\u0103\u021bi noi de a reduce lans\u0103rile reci, dar multe dintre acestea necesit\u0103 \u201escalare la unu\u201d (scale to one), ceea ce submineaz\u0103 valoarea ini\u021bial\u0103 a FaaS.<\/p>\n<p>Problema \u201elans\u0103rii reci\u201d poate fi par\u021bial rezolvat\u0103 prin desf\u0103\u0219urarea sistemelor serverless pe cont propriu, dar acest lucru vine cu propriile costuri \u0219i r\u0103m\u00e2ne o op\u021biune de ni\u0219\u0103 pentru echipele bine dotate.<\/p>\n<h3>Nu po\u021bi desf\u0103\u0219ura aplica\u021bii \u00eentregi<\/h3>\n<p>\n\u00cen cele din urm\u0103, poate cea mai important\u0103 cauz\u0103 pentru care arhitecturile serverless nu vor \u00eenlocui modelele tradi\u021bionale \u00een cur\u00e2nd: acestea (\u00een general) nu permit desf\u0103\u0219urarea de aplica\u021bii complete.<\/p>\n<p>Mai precis, acest lucru nu este fezabil din punct de vedere al costurilor. Monolitul t\u0103u de succes nu merit\u0103 s\u0103 fie transformat \u00eentr-un set de patruzeci de func\u021bii conectate prin opt gateway-uri, patruzeci de cozi \u0219i o duzin\u0103 de instan\u021be de Baze de Date. Din acest motiv, serverless este mai potrivit pentru dezvolt\u0103ri noi. Practic, nicio aplica\u021bie existent\u0103 (arhitectur\u0103) nu poate fi portat\u0103. Po\u021bi migra, dar va trebui s\u0103 \u00eencepi de la zero.<\/p>\n<p>Aceasta \u00eenseamn\u0103 c\u0103, \u00een cele mai multe cazuri, platformele serverless sunt utilizate ca un supliment la serverele interne pentru a executa sarcini care necesit\u0103 resurse de calcul mari. Aceasta le deosebe\u0219te foarte mult de celelalte dou\u0103 forme de tehnologii cloud \u2013 containere \u0219i ma\u0219ini virtuale, care ofer\u0103 o modalitate integrat\u0103 de desf\u0103\u0219urare a calcului la distan\u021b\u0103. Acest lucru ilustreaz\u0103 una dintre dificult\u0103\u021bile tranzi\u021biei de la microservicii la sistemele serverless.<\/p>\n<p>Desigur, aceasta nu este \u00eentotdeauna o problem\u0103. Posibilitatea de a utiliza periodic enorme resurse de calcul, f\u0103r\u0103 a cump\u0103ra hardware propriu, poate aduce beneficii reale \u0219i pe termen lung pentru multe organiza\u021bii. Dar dac\u0103 unele aplica\u021bii sunt pe servere interne, iar altele pe arhitecturi cloud f\u0103r\u0103 server, atunci gestionarea ajunge la un nou nivel de complexitate.<\/p>\n<h1>Tr\u0103iasc\u0103 revolu\u021bia?<\/h1>\n<p>\n\u00cen ciuda tuturor acestor pl\u00e2ngeri, nu am nimic \u00eempotriva solu\u021biilor f\u0103r\u0103 server ca atare. Promit. Doar c\u0103 dezvoltatorii trebuie s\u0103 \u00een\u021beleag\u0103\u2014mai ales dac\u0103 exploreaz\u0103 pentru prima dat\u0103 modelele f\u0103r\u0103 server\u2014that aceasta nu este o \u00eenlocuire direct\u0103 a serverelor. \u00cen schimb, consulta\u021bi sfaturile \u0219i resursele noastre despre <noindex><a rel=\"nofollow\" href=\"https:\/\/www.infoq.com\/articles\/understanding-serverless-servicefull-applications\/\">crearea aplica\u021biilor f\u0103r\u0103 server<\/a><\/noindex> \u0219i decide\u021bi cea mai bun\u0103 modalitate de a aplica acest model.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/524126\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u043b\u044e\u0447\u0435\u0432\u044b\u0435 \u043c\u043e\u043c\u0435\u043d\u0442\u044b \u0412\u043e\u0442 \u0443\u0436\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043d\u0430\u043c \u043e\u0431\u0435\u0449\u0430\u044e\u0442, \u0447\u0442\u043e \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u044b\u0435 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f (serverless) \u043e\u0442\u043a\u0440\u043e\u044e\u0442 \u043d\u043e\u0432\u0443\u044e \u044d\u043f\u043e\u0445\u0443 \u0431\u0435\u0437 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u041e\u0421 \u0434\u043b\u044f \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439. \u041d\u0430\u043c \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438, \u0447\u0442\u043e \u0442\u0430\u043a\u0430\u044f \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0430 \u0440\u0435\u0448\u0438\u0442 \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u0443\u0435\u043c\u043e\u0441\u0442\u0438. \u041d\u0430 \u0441\u0430\u043c\u043e\u043c \u0434\u0435\u043b\u0435 \u0432\u0441\u0451 \u0438\u043d\u0430\u0447\u0435. \u0425\u043e\u0442\u044f \u043c\u043d\u043e\u0433\u0438\u0435 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u044e\u0442 \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0443\u044e \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e \u043a\u0430\u043a \u043d\u043e\u0432\u0443\u044e \u0438\u0434\u0435\u044e, \u0435\u0451 \u043a\u043e\u0440\u043d\u0438 \u043c\u043e\u0436\u043d\u043e \u043f\u0440\u043e\u0441\u043b\u0435\u0434\u0438\u0442\u044c \u0432\u043f\u043b\u043e\u0442\u044c \u0434\u043e 2006 \u0433\u043e\u0434\u0430, \u043a\u043e\u0433\u0434\u0430 \u043f\u043e\u044f\u0432\u0438\u043b\u0438\u0441\u044c Zimki PaaS [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-97706","post","type-post","status-publish","format-standard","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=\"\u041a\u043b\u044e\u0447\u0435\u0432\u044b\u0435 \u043c\u043e\u043c\u0435\u043d\u0442\u044b \u0412\u043e\u0442 \u0443\u0436\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043d\u0430\u043c \u043e\u0431\u0435\u0449\u0430\u044e\u0442, \u0447\u0442\u043e \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u044b\u0435 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f (serverless) \u043e\u0442\u043a\u0440\u043e\u044e\u0442 \u043d\u043e\u0432\u0443\u044e \u044d\u043f\u043e\u0445\u0443 \u0431\u0435\u0437 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u041e\u0421 \u0434\u043b\u044f \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439.\" \/>\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\/pochemu-besservernaya-revolyucziya-zashla-v-tupik\" \/>\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\u041f\u043e\u0447\u0435\u043c\u0443 \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0430\u044f \u0440\u0435\u0432\u043e\u043b\u044e\u0446\u0438\u044f \u0437\u0430\u0448\u043b\u0430 \u0432 \u0442\u0443\u043f\u0438\u043a | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u043b\u044e\u0447\u0435\u0432\u044b\u0435 \u043c\u043e\u043c\u0435\u043d\u0442\u044b \u0412\u043e\u0442 \u0443\u0436\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043d\u0430\u043c \u043e\u0431\u0435\u0449\u0430\u044e\u0442, \u0447\u0442\u043e \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u044b\u0435 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f (serverless) \u043e\u0442\u043a\u0440\u043e\u044e\u0442 \u043d\u043e\u0432\u0443\u044e \u044d\u043f\u043e\u0445\u0443 \u0431\u0435\u0437 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u041e\u0421 \u0434\u043b\u044f \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-besservernaya-revolyucziya-zashla-v-tupik\" \/>\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=\"2020-10-21T00:42:26+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-10-21T00:42:26+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\udd47De ce revolu\u021bia f\u0103r\u0103 server a ajuns \u00eentr-un impas | ProHoster","description":"Punctele cheie De c\u00e2\u021biva ani ni se promite c\u0103 calculul f\u0103r\u0103 server va deschide o nou\u0103 er\u0103 f\u0103r\u0103 un sistem de operare specific pentru rularea aplica\u021biilor.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-besservernaya-revolyucziya-zashla-v-tupik","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\u041f\u043e\u0447\u0435\u043c\u0443 \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0430\u044f \u0440\u0435\u0432\u043e\u043b\u044e\u0446\u0438\u044f \u0437\u0430\u0448\u043b\u0430 \u0432 \u0442\u0443\u043f\u0438\u043a | ProHoster","og:description":"\u041a\u043b\u044e\u0447\u0435\u0432\u044b\u0435 \u043c\u043e\u043c\u0435\u043d\u0442\u044b \u0412\u043e\u0442 \u0443\u0436\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043d\u0430\u043c \u043e\u0431\u0435\u0449\u0430\u044e\u0442, \u0447\u0442\u043e \u0431\u0435\u0441\u0441\u0435\u0440\u0432\u0435\u0440\u043d\u044b\u0435 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f (serverless) \u043e\u0442\u043a\u0440\u043e\u044e\u0442 \u043d\u043e\u0432\u0443\u044e \u044d\u043f\u043e\u0445\u0443 \u0431\u0435\u0437 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u041e\u0421 \u0434\u043b\u044f \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-besservernaya-revolyucziya-zashla-v-tupik","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":"2020-10-21T00:42:26+00:00","article:modified_time":"2020-10-21T00:42:26+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"97706","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 10:15:26","updated":"2022-09-27 16:29:42","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\/97706","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=97706"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/97706\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=97706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=97706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=97706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}