{"id":33935,"date":"2019-10-31T21:55:27","date_gmt":"2019-10-31T18:55:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/serverless-po-stoechkam\/"},"modified":"2019-10-31T21:55:27","modified_gmt":"2019-10-31T18:55:27","slug":"serverless-po-stoechkam","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/serverless-po-stoechkam","title":{"rendered":"Serverless n\u00eb blloqe","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Serverless n\u00eb blloqe\" src=\"\/wp-content\/uploads\/2019\/05\/cea6dc9da0a3a1b0241246cdf3eba900.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nServerless nuk \u00ebsht\u00eb p\u00ebr munges\u00ebn fizike t\u00eb server\u00ebve. Nuk \u00ebsht\u00eb nj\u00eb \"vras\u00ebs\" i konteiner\u00ebve dhe as nj\u00eb trend kalimtar. \u00cbsht\u00eb nj\u00eb qasje e re p\u00ebr nd\u00ebrtimin e sistemeve n\u00eb re. N\u00eb k\u00ebt\u00eb artikull do t\u00eb flasim p\u00ebr arkitektur\u00ebn e aplikacioneve Serverless, duke par\u00eb rolin q\u00eb luan ofruesi i sh\u00ebrbimeve Serverless dhe projektet open-source. N\u00eb fund do t\u00eb diskutojm\u00eb p\u00ebr \u00e7\u00ebshtjet e aplikimit t\u00eb Serverless.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nDua t\u00eb shkruaj pjes\u00ebn server t\u00eb aplikacionit (madje ndonj\u00eb dyqan online). Mund t\u00eb jet\u00eb nj\u00eb bised\u00eb, nj\u00eb sh\u00ebrbim p\u00ebr publikimin e p\u00ebrmbajtjes, ose nj\u00eb balancues ngarkese. N\u00eb \u00e7do rast, do t\u00eb ket\u00eb shum\u00eb shqet\u00ebsime: do t\u00eb duhet t\u00eb p\u00ebrgatisim infrastruktur\u00ebn, t\u00eb p\u00ebrcaktojm\u00eb var\u00ebsit\u00eb e aplikacionit, dhe t\u00eb mendojm\u00eb p\u00ebr sistemin operativ t\u00eb hostit. M\u00eb pas do t\u00eb nevojitet t\u00eb p\u00ebrdit\u00ebsohen komponent\u00ebt e vegj\u00ebl q\u00eb nuk prekin pun\u00ebn e monolit tjet\u00ebr. Dhe mos ta harrojm\u00eb as skalimin n\u00ebn ngarkes\u00eb.<\/p>\n<p>E \u00e7far\u00eb n\u00ebse t\u00eb merrni konteiner\u00eb efemer\u00eb, n\u00eb t\u00eb cil\u00ebt var\u00ebsit\u00eb e k\u00ebrkuara jan\u00eb tashm\u00eb t\u00eb instaluara, dhe k\u00ebta konteiner\u00eb jan\u00eb t\u00eb izoluar nga nj\u00ebri-tjetri dhe nga OS e hostit? Ne do t\u00eb shnd\u00ebrrojm\u00eb monolitin n\u00eb mikrosh\u00ebrbime, secili prej t\u00eb cilave mund t\u00eb p\u00ebrdit\u00ebsohet dhe t\u00eb shkall\u00ebzohet n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur nga tjer\u00ebt. Duke vendosur kodin n\u00eb nj\u00eb konteiner t\u00eb till\u00eb, do t\u00eb mund ta ekzekutoj at\u00eb n\u00eb \u00e7do infrastruktur\u00eb. Kjo tashm\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb. <\/p>\n<p>E n\u00ebse nuk d\u00ebshiroj t\u00eb konfiguroj konteiner\u00ebt? Nuk dua t\u00eb mendoj p\u00ebr shkall\u00ebzimin e aplikacionit. Nuk dua t\u00eb paguaj p\u00ebr pushimin e konteiner\u00ebve t\u00eb aktivizuar kur ngarkesa n\u00eb sh\u00ebrbim \u00ebsht\u00eb minimale. Dua t\u00eb shkruaj kod. T\u00eb p\u00ebrqendrohem n\u00eb logjik\u00ebn e biznesit dhe t\u00eb nxjerr produktet n\u00eb treg me shpejt\u00ebsi drit\u00eb. <\/p>\n<p>K\u00ebto mendime m\u00eb \u00e7uan n\u00eb llogaritjet pa server. Serverless n\u00eb k\u00ebt\u00eb rast do t\u00eb thot\u00eb <em>jo munges\u00ebn fizike t\u00eb server\u00ebve, por munges\u00ebn e dhimbjes s\u00eb kok\u00ebs nga menaxhimi i infrastruktur\u00ebs.<\/em><\/p>\n<p>Ideja \u00ebsht\u00eb q\u00eb logjika e aplikacionit t\u00eb ndahet n\u00eb funksione t\u00eb pavarura. K\u00ebto kan\u00eb nj\u00eb struktur\u00eb ngjarjesh. \u00c7do funksion ekzekuton nj\u00eb \"mikrodetyr\u00eb\". Gjith\u00e7ka q\u00eb k\u00ebrkohet nga zhvilluesi \u00ebsht\u00eb t\u00eb ngarkohet funksionet n\u00eb konsol\u00ebn e ofruar nga ofruesi i sh\u00ebrbimeve cloud dhe t'i lidh\u00eb ato me burimet e ngjarjeve. Kodi do t\u00eb ekzekutohet me k\u00ebrkes\u00eb n\u00eb nj\u00eb container t\u00eb p\u00ebrgatitur automatikisht, dhe un\u00eb do t\u00eb paguaj vet\u00ebm p\u00ebr koh\u00ebn e ekzekutimit. <\/p>\n<p>Le t\u00eb shohim se si do t\u00eb duket tani procesi i zhvillimit t\u00eb aplikacionit.<\/p>\n<h2>Nga pik\u00ebpamja e zhvilluesit<\/h2>\n<p>\nM\u00eb par\u00eb filluam t\u00eb flasim p\u00ebr nj\u00eb aplikacion p\u00ebr nj\u00eb dyqan online. N\u00eb qasjen tradicionale, logjika kryesore e sistemit ekzekutohet nga nj\u00eb aplikacion monolitik. Dhe serveri me aplikacionin \u00ebsht\u00eb gjithmon\u00eb aktiv, edhe n\u00ebse nuk ka ngarkes\u00eb.<\/p>\n<p><strong>P\u00ebr t\u00eb kaluar n\u00eb serverless, e ndam\u00eb aplikacionin n\u00eb mikrodetyra.<\/strong> P\u00ebr secil\u00ebn prej tyre shkruajm\u00eb funksionin ton\u00eb. Funksionet jan\u00eb t\u00eb pavarura nga nj\u00ebra-tjetra dhe nuk ruajn\u00eb informacion n\u00eb lidhje me gjendjen (stateless). Ato madje mund t\u00eb jen\u00eb shkruar n\u00eb gjuh\u00eb t\u00eb ndryshme. N\u00ebse nj\u00ebra prej tyre \"b\u00ebn r\u00ebnie\", aplikacioni n\u00eb t\u00ebr\u00ebsi nuk do t\u00eb ndaloj\u00eb. Arkitektura e aplikacionit do t\u00eb duket k\u00ebshtu:<\/p>\n<p><img decoding=\"async\" alt=\"Serverless n\u00eb blloqe\" src=\"\/wp-content\/uploads\/2019\/05\/f62c5c08bbf587766198dbb807123273.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nShp\u00ebrndarja e funksioneve n\u00eb Serverless \u00ebsht\u00eb e ngjashme me pun\u00ebn me mikrosh\u00ebrbime. Por nj\u00eb mikrosh\u00ebrbim mund t\u00eb kryej\u00eb disa detyra, nd\u00ebrsa funksioni n\u00eb ideal duhet t\u00eb kryej\u00eb vet\u00ebm nj\u00eb. Imagjinoni nj\u00eb rast ku duhen mbledhur statistika dhe paraqitur sipas k\u00ebrkes\u00ebs s\u00eb p\u00ebrdoruesit. N\u00eb qasjen mikrosh\u00ebrbimore, detyra kryhet nga nj\u00eb sh\u00ebrbim me dy pika hyrjeje: p\u00ebr shkrim dhe p\u00ebr lexim. N\u00eb llogarit\u00eb pa server, k\u00ebto do t\u00eb ishin dy funksione t\u00eb ndryshme, t\u00eb pa lidhura me nj\u00ebra-tjetr\u00ebn. Zhvilluesi kursen burimet llogarike, n\u00ebse, p\u00ebr shembull, statistika p\u00ebrdit\u00ebsohet m\u00eb shpesh sesa eksportohen. <\/p>\n<p>Funksionet Serverless duhet t\u00eb ekzekutohen brenda nj\u00eb periudhe t\u00eb shkurt\u00ebr kohore (timeout), e cila p\u00ebrcaktohet nga ofruesi i sh\u00ebrbimit. P\u00ebr shembull, p\u00ebr AWS, timeout-i \u00ebsht\u00eb 15 minuta. K\u00ebshtu, funksionet e gjata (long-lived) do t\u00eb duhet t\u00eb ndryshojn\u00eb sipas k\u00ebrkesave - kjo \u00ebsht\u00eb \u00e7ka e dallon Serverless nga teknologjit\u00eb e tjera t\u00eb njohura sot (kontejner\u00ebt dhe Platform as a Service).<\/p>\n<p><strong>\u00c7do funksion i caktohet nj\u00eb ngjarje.<\/strong> Ngjarja \u00ebsht\u00eb nj\u00eb aktivizues p\u00ebr veprimin:<\/p>\n<p><strong>Ngjarja<\/strong><br \/>\n<strong>Veprimi q\u00eb kryen funksioni<\/strong><\/p>\n<p>N\u00eb ruajtje \u00ebsht\u00eb ngarkuar nj\u00eb imazh i produktit<br \/>\nKompresoni imazhin dhe eksportoni n\u00eb katalog<\/p>\n<p>N\u00eb baz\u00ebn e t\u00eb dh\u00ebnave \u00ebsht\u00eb p\u00ebrdit\u00ebsuar adresa e dyqanit fizik<br \/>\nNgarko nj\u00eb vendndodhje t\u00eb re n\u00eb mapa<\/p>\n<p>K clienti paguan produktin<br \/>\nFilloni p\u00ebrpunimin e pages\u00ebs<\/p>\n<p>Ngjarjet mund t\u00eb jen\u00eb k\u00ebrkesa HTTP, t\u00eb dh\u00ebna t\u00eb rrjedhshme, radh\u00eb mesazhesh etj. Burimet e ngjarjeve jan\u00eb ndryshimi ose shfaqja e t\u00eb dh\u00ebnave. P\u00ebr m\u00eb tep\u00ebr, funksionet mund t\u00eb aktivizohen me nj\u00eb timer.<\/p>\n<p>Arkitektura \u00ebsht\u00eb punuar dhe aplicacioni pothuajse ka arritur statusin serverless. T\u00eb vazhdojm\u00eb me ofruesin e sh\u00ebrbimit.<\/p>\n<h2>Nga ana e ofruesit<\/h2>\n<p>\nZakonisht, llogarit\u00eb pa server ofrohen nga ofruesit e sh\u00ebrbimeve cloud. I quajn\u00eb ndryshe: Azure Functions, AWS Lambda, Google Cloud Functions, IBM Cloud Functions. <\/p>\n<p>Ne do t\u00eb p\u00ebrdorim sh\u00ebrbimin p\u00ebrmes konsol\u00ebs ose llogaris\u00eb personale t\u00eb ofruesit. Kodi i funksioneve mund t\u00eb ngarkohet n\u00eb nj\u00eb nga k\u00ebto m\u00ebnyra:<\/p>\n<ul>\n<li>t\u00eb shkruajm\u00eb kodin n\u00eb redaktor\u00ebt e integruar p\u00ebrmes konsol\u00ebs web,<\/li>\n<li>t\u00eb ngarkojm\u00eb nj\u00eb arkiv me kodin,<\/li>\n<li>t\u00eb punojm\u00eb me repozitoret git publike ose private.<\/li>\n<\/ul>\n<p>\nK\u00ebtu gjithashtu konfiguroni ngjarjet q\u00eb aktivizojn\u00eb funksionin. Grupi i ngjarjeve mund t\u00eb ndryshoj\u00eb nga ofruesi n\u00eb ofrues.<\/p>\n<p><img decoding=\"async\" alt=\"Serverless n\u00eb blloqe\" src=\"\/wp-content\/uploads\/2019\/05\/98676fa23a9911aae5758ecdb2cd9a03.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Ofruesi ka nd\u00ebrtuar dhe automatizuar nj\u00eb sistem Function as a Service (FaaS) n\u00eb infrastruktur\u00ebn e tij:<\/p>\n<ol>\n<li>Kodi i funksioneve arrin n\u00eb nj\u00eb depo n\u00eb an\u00ebn e ofruesit.<\/li>\n<li>Kur ndodh nj\u00eb ngjarje, kontejner\u00ebt me ambientin e p\u00ebrgatitur krijohen automatikisht n\u00eb server. \u00c7do ekzemplar funksioni ka kontejnerin e vet t\u00eb izoluar.<\/li>\n<li>Nga depoja, funksioni d\u00ebrgohet n\u00eb kontejner, llogaritet dhe jep rezultatin.<\/li>\n<li>Numri i ngjarjeve paralele rritet \u2014 rritet edhe numri i kontejner\u00ebve. Sistemi automatikisht shkall\u00ebzohet. N\u00ebse p\u00ebrdoruesit nuk i japin funksionit, ai do t\u00eb jet\u00eb joaktiv.<\/li>\n<li>Ofruesi p\u00ebrcakton koh\u00ebn e pezullimit t\u00eb kontejner\u00ebve \u2014 n\u00ebse gjat\u00eb k\u00ebtij koh\u00eb funksionet nuk shfaqen n\u00eb kontejner, ai shkat\u00ebrrohet.<\/li>\n<\/ol>\n<p>\nK\u00ebshtu, ne marrim Serverless \u00abt\u00eb gatsh\u00ebm p\u00ebr p\u00ebrdorim\u00bb. Do t\u00eb paguajm\u00eb p\u00ebr sh\u00ebrbimin sipas modelit pay-as-you-go dhe vet\u00ebm p\u00ebr ato funksione q\u00eb p\u00ebrdoren, dhe vet\u00ebm p\u00ebr koh\u00ebn kur ato jan\u00eb p\u00ebrdorur.<\/p>\n<p>P\u00ebr t\u00eb njohur zhvilluesit me sh\u00ebrbimin, ofruesit ofrojn\u00eb deri n\u00eb 12 muaj prov\u00eb falas, por kufizojn\u00eb koh\u00ebn totale t\u00eb llogaritjeve, numrin e k\u00ebrkesave n\u00eb muaj, fondet ose kapacitetin e konsumuar.<\/p>\n<p>Avantazhi kryesor i pun\u00ebs me ofruesit \u00ebsht\u00eb mund\u00ebsia p\u00ebr t\u00eb mos u shqet\u00ebsuar p\u00ebr infrastruktur\u00ebn (server\u00ebt, makinat virtuale, kontejner\u00ebt). Nga ana e saj, ofruesi mund t\u00eb implementoj\u00eb FaaS si n\u00eb zhvillimet e tij, ashtu edhe p\u00ebrmes mjeteve open-source. K\u00ebto do t'i diskutojm\u00eb m\u00eb tej.<\/p>\n<h2>Nga ana e open source<\/h2>\n<p>\nDy vitet e fundit, komuniteti open-source ka punuar aktivisht mbi mjete Serverless. N\u00eb k\u00ebt\u00eb p\u00ebrfshihen edhe kontributet e lojtar\u00ebve m\u00eb t\u00eb m\u00ebdhenj t\u00eb tregut:<\/p>\n<ul>\n<li><strong>Google<\/strong> ofron zhvilluesve mjetin e tij open-source \u2015 <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/knative\/\">Knative<\/a><\/noindex>. N\u00eb zhvillimin e tij mor\u00ebn pjes\u00eb IBM, RedHat, Pivotal dhe SAP;<\/li>\n<li><strong>IBM<\/strong> punuan mbi platform\u00ebn Serverless <noindex><a rel=\"nofollow\" href=\"https:\/\/openwhisk.apache.org\/\">OpenWhisk<\/a><\/noindex>, e cila m\u00eb von\u00eb u b\u00eb projekt i Fondacionit Apache;<\/li>\n<li><strong>Microsoft<\/strong> pjes\u00ebrisht hap\u00ebn kodin e platform\u00ebs <noindex><a rel=\"nofollow\" href=\"https:\/\/azure.microsoft.com\/en-us\/services\/functions\/\">Azure Functions<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\nZhvillimet po b\u00ebhen gjithashtu n\u00eb drejtim t\u00eb framework-\u00ebve serverless. <noindex><a rel=\"nofollow\" href=\"https:\/\/kubeless.io\/\">Kubeless<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/fission.io\/\">Fission<\/a><\/noindex> nd\u00ebrtohen brenda klaster\u00ebve Kubernetes t\u00eb p\u00ebrgatitur m\u00eb par\u00eb, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.openfaas.com\/\">OpenFaaS<\/a><\/noindex> punon si me Kubernetes, ashtu edhe me Docker Swarm. Framework-u sh\u00ebrben si nj\u00eb lloj kontrolluesi \u2015 sipas k\u00ebrkes\u00ebs p\u00ebrgatit mjedisin e ekzekutimit brenda klasterit, pastaj e nis atje funksionin.<\/p>\n<p>Frameworket ofron hap\u00ebsir\u00eb p\u00ebr konfigurimin e mjetit sipas nevojave t\u00eb tij. K\u00ebshtu, n\u00eb Kubeless, zhvilluesi mund t\u00eb konfiguroj\u00eb koh\u00ebn e skadenc\u00ebs p\u00ebr ekzekutimin e funksionit (vlera e paracaktuar \u00ebsht\u00eb 180 sekonda). Fission, n\u00eb p\u00ebrpjekje p\u00ebr t\u00eb zgjidhur problemin e fillimit t\u00eb ftoht\u00eb, ofron q\u00eb disa kontejner\u00eb t\u00eb mbahen gjithmon\u00eb t\u00eb aktivizuar (ndon\u00ebse kjo sjell kosto p\u00ebr burimet e pap\u00ebrdorura). Nd\u00ebrsa OpenFaaS ofron nj\u00eb grup nxit\u00ebsish p\u00ebr \u00e7do shije dhe ngjyr\u00eb: HTTP, Kafka, Redis, MQTT, Cron, AWS SQS, NATs dhe t\u00eb tjer\u00eb.<\/p>\n<p>Udh\u00ebzimet p\u00ebr t\u00eb filluar mund t\u00eb gjenden n\u00eb dokumentacionin zyrtar t\u00eb frameworkeve. Puna me to n\u00ebnkupton njohuri disi m\u00eb t\u00eb m\u00ebdha sesa kur punojm\u00eb me nj\u00eb ofrues \u2014 kjo \u00ebsht\u00eb minimalisht aft\u00ebsia p\u00ebr t\u00eb lan\u00e7uar nj\u00eb cluster Kubernetes p\u00ebrmes CLI. Maksimumi, p\u00ebrfshirja e mjeteve t\u00eb tjera open-source (p.sh., menaxhuesi i radh\u00ebve Kafka).<\/p>\n<p>Pavar\u00ebsisht m\u00ebnyr\u00ebs se si do t\u00eb punojm\u00eb me Serverless \u2014 p\u00ebrmes nj\u00eb ofruesi ose n\u00ebp\u00ebrmjet open-source, ne do t\u00eb p\u00ebrfitojm\u00eb nj\u00eb s\u00ebr\u00eb p\u00ebrpar\u00ebsish dhe mang\u00ebsish t\u00eb trendit Serverless.<\/p>\n<h2>Nga pozita e p\u00ebrpar\u00ebsive dhe mang\u00ebsive<\/h2>\n<p>\nServerless zhvillon ide t\u00eb infrastruktur\u00ebs me kontejner\u00eb dhe qasjes mikrosh\u00ebrbimore, ku ekipet mund t\u00eb punojn\u00eb n\u00eb m\u00ebnyr\u00eb multilinguale, pa u lidhur me nj\u00eb platform\u00eb t\u00eb vetme. Nd\u00ebrtimi i sistemit b\u00ebhet m\u00eb i thjesht\u00eb, dhe korrigjimi i gabimeve \u00ebsht\u00eb m\u00eb i leht\u00eb. Arkitektura mikrosh\u00ebrbimore lejon shtimin e funksionaliteteve t\u00eb reja n\u00eb sistem shum\u00eb m\u00eb shpejt se n\u00eb rastin e nj\u00eb aplikacioni monolit.<\/p>\n<p><strong>Serverless e redukton akoma m\u00eb shum\u00eb koh\u00ebn e zhvillimit,<\/strong> duke i lejuar programuesit t\u00eb fokusohet ekskluzivisht n\u00eb logjik\u00ebn e biznesit t\u00eb aplikacionit dhe n\u00eb shkrimin e kodit. Si pasoj\u00eb, koha p\u00ebr hyrjen e zhvillimeve n\u00eb treg reduktohet.<\/p>\n<p><strong>Si bonus, ne marrim shkall\u00ebzim automatik sipas ngarkes\u00ebs,<\/strong> nd\u00ebrsa paguajm\u00eb vet\u00ebm p\u00ebr burimet e p\u00ebrdorura dhe vet\u00ebm n\u00eb koh\u00ebn kur ato p\u00ebrdoren.<\/p>\n<p>Si \u00e7do teknologji tjet\u00ebr, Serverless ka disavantazhe.<\/p>\n<p><em>P\u00ebr shembull, nj\u00eb prej disavantazheve do t\u00eb ishte koha e nisjes s\u00eb ftoht\u00eb (n\u00eb mesatare deri n\u00eb 1 sekond\u00eb p\u00ebr gjuh\u00eb si JavaScript, Python, Go, Java, Ruby).<\/em><\/p>\n<p>N\u00eb nj\u00ebr\u00ebn an\u00eb, koha e ftoht\u00eb e nisjes varet n\u00eb t\u00eb v\u00ebrtet\u00eb nga shum\u00eb variabla: gjuha n\u00eb t\u00eb cil\u00ebn \u00ebsht\u00eb shkruar funksioni, numri i librarive, volume i kodit, nd\u00ebrlidhja me burime t\u00eb tjera (si databaza apo serverat e autentikimit). Duke qen\u00eb se zhvilluesi menaxhon k\u00ebta variabla, ai mund ta zvog\u00ebloj\u00eb koh\u00ebn e nisjes. Por nga ana tjet\u00ebr, zhvilluesi nuk mund t\u00eb kontrolloj\u00eb koh\u00ebn e nisjes s\u00eb konteinerit \u2014 k\u00ebtu gjith\u00e7ka varet nga ofruesi.<\/p>\n<p>Ftohja mund t\u00eb b\u00ebhet e ngroht\u00eb kur funksioni rip\u00ebrdor nj\u00eb konteiner t\u00eb nisur nga nj\u00eb ngjarje e m\u00ebparshme. Kjo situat\u00eb do t\u00eb ndodh\u00eb n\u00eb tre raste:<\/p>\n<ul>\n<li>n\u00ebse klient\u00ebt p\u00ebrdorin shpesh sh\u00ebrbimin dhe rritet numri i thirrjeve p\u00ebr funksionin;<\/li>\n<li>n\u00ebse ofruesi, platforma ose framework-u lejojn\u00eb mbajtjen e disa konteiner\u00ebve t\u00eb nisur gjithmon\u00eb;<\/li>\n<li>n\u00ebse zhvilluesi nis funksionet n\u00ebp\u00ebrmjet nj\u00eb timeri (p.sh., \u00e7do 3 minuta).<\/li>\n<\/ul>\n<p>\nP\u00ebr shum\u00eb aplikacione, nisja e ftoht\u00eb nuk \u00ebsht\u00eb nj\u00eb problem. K\u00ebtu duhet t\u00eb bazoheni n\u00eb llojin dhe detyrat e sh\u00ebrbimit. Vonesa e nisjes p\u00ebr nj\u00eb sekond\u00eb nuk \u00ebsht\u00eb gjithmon\u00eb kritike p\u00ebr aplikacionet biznesore, por mund t\u00eb b\u00ebhet kritike p\u00ebr sh\u00ebrbimet mjek\u00ebsore. Probabilisht, n\u00eb k\u00ebt\u00eb rast, qasja serverless nuk do t\u00eb jet\u00eb e p\u00ebrshtatshme.<\/p>\n<p><em>Nj\u00eb tjet\u00ebr disavantazh i Serverless \u00ebsht\u00eb koha e shkurt\u00ebr e jet\u00ebs s\u00eb funksionit (timeout, p\u00ebr t\u00eb cilin funksioni duhet t\u00eb p\u00ebrfundoj\u00eb).<\/em><\/p>\n<p>Por, n\u00ebse do t\u00eb punoni me detyra afatgjata, mund t\u00eb p\u00ebrdorni nj\u00eb arkitektur\u00eb hibridike \u2014 t\u00eb kombinoheni Serverless me nj\u00eb teknologji tjet\u00ebr.<\/p>\n<p><em>Jo t\u00eb gjitha sistemet do t\u00eb mund t\u00eb punojn\u00eb n\u00eb skem\u00ebn Serverless.<\/em><\/p>\n<p>Disa aplikacione ende do t\u00eb ruajn\u00eb t\u00eb dh\u00ebna dhe gjendje gjat\u00eb ekzekutimit. Disa arhitektur\u00eb do t\u00eb mbeten monolitike, nd\u00ebrsa disa funksione do t\u00eb jen\u00eb afatgjata. Megjithat\u00eb (si dikur teknologjit\u00eb cloud dhe m\u00eb pas kontejner\u00ebt), Serverless \u00ebsht\u00eb nj\u00eb teknologji me nj\u00eb t\u00eb ardhme t\u00eb madhe.<\/p>\n<p>N\u00eb k\u00ebt\u00eb kuad\u00ebr, do doja t\u00eb kaloj n\u00eb m\u00ebnyr\u00eb t\u00eb qet\u00eb n\u00eb \u00e7\u00ebshtjen e aplikimit t\u00eb qasjes Serverless.<\/p>\n<h2>Nga ana e aplikimit<\/h2>\n<p>\nGjat\u00eb vitit 2018, p\u00ebrqindja e p\u00ebrdorimit t\u00eb Serverless <noindex><a rel=\"nofollow\" href=\"https:\/\/media.flexera.com\/documents\/rightscale-2019-state-of-the-cloud-report-from-flexera.pdf\">u rrit nj\u00eb p\u00ebraf\u00ebrsisht 1.5 her\u00eb<\/a><\/noindex>. N\u00eb mesin e kompanive q\u00eb tashm\u00eb kan\u00eb implementuar teknologjin\u00eb n\u00eb sh\u00ebrbimet e tyre, jan\u00eb gjigand\u00ebt e tregut si Twitter, PayPal, Netflix, T-Mobile, Coca-Cola. Megjithat\u00eb, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet se Serverless nuk \u00ebsht\u00eb nj\u00eb panacee, por nj\u00eb instrument p\u00ebr zgjidhjen e nj\u00eb gam\u00eb t\u00eb caktuar t\u00eb detyrave:<\/p>\n<ul>\n<li><strong>T\u00eb reduktojm\u00eb ndalesat e burimeve.<\/strong> Nuk \u00ebsht\u00eb e nevojshme t\u00eb mbash vazhdimisht nj\u00eb makin\u00eb virtuale p\u00ebr sh\u00ebrbime q\u00eb kan\u00eb pak k\u00ebrkesa.<\/li>\n<li><strong>T\u00eb p\u00ebrpunosh t\u00eb dh\u00ebna \u00abn\u00eb fluturi\u00bb.<\/strong> T\u00eb kompresosh imazhe, t\u00eb t\u00ebrheq\u00ebsh sfondin, t\u00eb ndryshosh kodimin e videos, t\u00eb punosh me sensor\u00eb IoT, t\u00eb kryesh operacione matematikore.\n<\/li>\n<li><strong>T\u00eb \u00ablidhnim\u00bb s\u00eb bashku sh\u00ebrbime t\u00eb tjera.<\/strong> Git-repozitori me programet e brendshme, chatbot n\u00eb Slack me Jira dhe kalendarin.<\/li>\n<li><strong>T\u00eb balancosh ngarkes\u00ebn.<\/strong> K\u00ebtu do t\u00eb ndalemi m\u00eb n\u00eb detaje.<\/li>\n<\/ul>\n<p>\nSupozoni, ka nj\u00eb sh\u00ebrbim, n\u00eb t\u00eb cilin vijn\u00eb 50 njer\u00ebz. P\u00ebr t\u00eb, ka nj\u00eb makin\u00eb virtuale me pajisje t\u00eb dob\u00ebta. Periodikisht ngarkesa n\u00eb sh\u00ebrbim rritet shum\u00ebfish. At\u00ebher\u00eb pajisja e dob\u00ebt nuk \u00ebsht\u00eb n\u00eb gjendje t\u00eb p\u00ebrballoj\u00eb.<\/p>\n<p>Mund t\u00eb implementoni nj\u00eb balancues ngarkese q\u00eb do t\u00eb shp\u00ebrndaj\u00eb ngarkes\u00ebn, le t\u00eb themi, n\u00eb tre makina virtuale. N\u00eb k\u00ebt\u00eb faz\u00eb, nuk mund t\u00eb parashikojm\u00eb sakt\u00ebsisht ngarkes\u00ebn, prandaj mbajm\u00eb disa burime aktive \"p\u00ebr rezerv\u00eb\". Dhe paguajm\u00eb m\u00eb shum\u00eb p\u00ebr inaktivitetin. <\/p>\n<p>N\u00eb nj\u00eb situat\u00eb t\u00eb till\u00eb, ne mund ta optimizojm\u00eb sistemin n\u00ebp\u00ebrmjet nj\u00eb qasjeje hibride: pas balancuesit t\u00eb ngarkes\u00ebs, l\u00ebm\u00eb nj\u00eb makin\u00eb virtuale dhe vendosim nj\u00eb lidhje me Serverless Endpoint me funksionet. N\u00ebse ngarkesa tejkalon pragun, balancuesi aktivizon instancat e funksioneve q\u00eb marrin p\u00ebrsip\u00ebr nj\u00eb pjes\u00eb t\u00eb p\u00ebrpunimit t\u00eb k\u00ebrkesave.<\/p>\n<p><img decoding=\"async\" alt=\"Serverless n\u00eb blloqe\" src=\"\/wp-content\/uploads\/2019\/05\/79262c19faba29a4639a05e3097f7914.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nN\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, Serverless mund t\u00eb p\u00ebrdoret atje ku duhen p\u00ebrpunuar shpesh, por n\u00eb m\u00ebnyr\u00eb intensive, nj\u00eb num\u00ebr i madh k\u00ebrkesh. N\u00eb k\u00ebt\u00eb rast, \u00ebsht\u00eb m\u00eb e dobishme t\u00eb aktivizoni disa funksione p\u00ebr 15 minuta sesa t\u00eb mbani aktiv nj\u00eb makin\u00eb virtuale ose nj\u00eb server gjat\u00eb gjith\u00eb koh\u00ebs.<\/p>\n<p>Pavar\u00ebsisht t\u00eb gjitha p\u00ebrfitimeve t\u00eb p\u00ebrpunimit pa server, para se ta implementoni, n\u00eb radh\u00eb t\u00eb par\u00eb do t\u00eb duhet t\u00eb vler\u00ebsoni logjik\u00ebn e aplikacionit dhe t\u00eb kuptoni se cilat detyra mund t\u00eb zgjidh\u00eb Serverless n\u00eb rastin konkret. <\/p>\n<h2>Serverless dhe Selectel<\/h2>\n<p>\nN\u00eb Selectel ne tashm\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.selectel.ru\/42078178.html?utm_source=habr.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Functions_Serverless_Article_170519\">e kemi thjeshtuar pun\u00ebn me Kubernetes<\/a><\/noindex> p\u00ebrmes panelit ton\u00eb t\u00eb menaxhimit. Tani po nd\u00ebrtojm\u00eb platform\u00ebn ton\u00eb FaaS. Duam q\u00eb zhvilluesit t\u00eb mund t\u00eb zgjidhin problemet e tyre me Serverless p\u00ebrmes nj\u00eb nd\u00ebrfaqeje t\u00eb leht\u00eb dhe fleksible.<\/p>\n<p>N\u00ebse keni ide se si duhet t\u00eb duket platforma ideale FaaS dhe si d\u00ebshironi t\u00eb p\u00ebrdorni Serverless n\u00eb projektet tuaja, ndani ato n\u00eb komentet m\u00eb posht\u00eb. Do t\u00eb kemi parasysh d\u00ebshirat tuaja gjat\u00eb zhvillimit t\u00eb platform\u00ebs.<br \/>\n\u00a0<br \/>\nMaterialet e p\u00ebrdorura n\u00eb artikull:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.rightscale.com\/lp\/state-of-the-cloud\">P\u00ebrdorimi i Serverless \u00ebsht\u00eb rritur 50% (raport i plot\u00eb RightScale)<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/mikhail.io\/serverless\/coldstarts\/aws\/\">Si varet koha e fillimit t\u00eb ftoht\u00eb nga gjuha e aplikacionit<\/a><\/noindex><\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/452266\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>Serverless \u2015 \u044d\u0442\u043e \u043d\u0435 \u043f\u0440\u043e \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u043e\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432. \u042d\u0442\u043e \u043d\u0435 \u00ab\u0443\u0431\u0438\u0439\u0446\u0430\u00bb \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0438 \u043d\u0435 \u043c\u0438\u043c\u043e\u043b\u0435\u0442\u043d\u044b\u0439 \u0442\u0440\u0435\u043d\u0434. \u042d\u0442\u043e \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0434\u0445\u043e\u0434 \u043a \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044e \u0441\u0438\u0441\u0442\u0435\u043c \u0432 \u043e\u0431\u043b\u0430\u043a\u0435. \u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043a\u043e\u0441\u043d\u0435\u043c\u0441\u044f \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b Serverless-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0438\u043c, \u043a\u0430\u043a\u0443\u044e \u0440\u043e\u043b\u044c \u0438\u0433\u0440\u0430\u0435\u0442 \u043f\u0440\u043e\u0432\u0430\u0439\u0434\u0435\u0440 Serverless-\u0443\u0441\u043b\u0443\u0433\u0438 \u0438 open-source \u043f\u0440\u043e\u0435\u043a\u0442\u044b. \u0412 \u043a\u043e\u043d\u0446\u0435 \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0432\u043e\u043f\u0440\u043e\u0441\u0430\u0445 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f Serverless. \u042f \u0445\u043e\u0447\u0443 \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0443\u044e \u0447\u0430\u0441\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f (\u0434\u0430 \u0445\u043e\u0442\u044c \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043c\u0430\u0433\u0430\u0437\u0438\u043d\u0430). [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":25594,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-33935","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.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Serverless \u2015 \u044d\u0442\u043e \u043d\u0435 \u043f\u0440\u043e \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u043e\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432. \u042d\u0442\u043e \u043d\u0435 \u00ab\u0443\u0431\u0438\u0439\u0446\u0430\u00bb \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0438 \u043d\u0435 \u043c\u0438\u043c\u043e\u043b\u0435\u0442\u043d\u044b\u0439 \u0442\u0440\u0435\u043d\u0434. \u042d\u0442\u043e \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0434\u0445\u043e\u0434 \u043a \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044e \u0441\u0438\u0441\u0442\u0435\u043c \u0432 \u043e\u0431\u043b\u0430\u043a\u0435. \u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043a\u043e\u0441\u043d\u0435\u043c\u0441\u044f \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b Serverless-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0438\u043c, \u043a\u0430\u043a\u0443\u044e \u0440\u043e\u043b\u044c \u0438\u0433\u0440\u0430\u0435\u0442 \u043f\u0440\u043e\u0432\u0430\u0439\u0434\u0435\u0440 Serverless-\u0443\u0441\u043b\u0443\u0433\u0438 \u0438 open-source \u043f\u0440\u043e\u0435\u043a\u0442\u044b. \u0412 \u043a\u043e\u043d\u0446\u0435 \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0432\u043e\u043f\u0440\u043e\u0441\u0430\u0445 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f Serverless. \u042f \u0445\u043e\u0447\u0443 \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0443\u044e \u0447\u0430\u0441\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f (\u0434\u0430 \u0445\u043e\u0442\u044c \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043c\u0430\u0433\u0430\u0437\u0438\u043d\u0430).\" \/>\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\/sq\/blog\/administrirovanie\/serverless-po-stoechkam\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\udd47Serverless \u043f\u043e \u0441\u0442\u043e\u0435\u0447\u043a\u0430\u043c | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"Serverless \u2015 \u044d\u0442\u043e \u043d\u0435 \u043f\u0440\u043e \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u043e\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432. \u042d\u0442\u043e \u043d\u0435 \u00ab\u0443\u0431\u0438\u0439\u0446\u0430\u00bb \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0438 \u043d\u0435 \u043c\u0438\u043c\u043e\u043b\u0435\u0442\u043d\u044b\u0439 \u0442\u0440\u0435\u043d\u0434. \u042d\u0442\u043e \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0434\u0445\u043e\u0434 \u043a \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044e \u0441\u0438\u0441\u0442\u0435\u043c \u0432 \u043e\u0431\u043b\u0430\u043a\u0435. \u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043a\u043e\u0441\u043d\u0435\u043c\u0441\u044f \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b Serverless-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0438\u043c, \u043a\u0430\u043a\u0443\u044e \u0440\u043e\u043b\u044c \u0438\u0433\u0440\u0430\u0435\u0442 \u043f\u0440\u043e\u0432\u0430\u0439\u0434\u0435\u0440 Serverless-\u0443\u0441\u043b\u0443\u0433\u0438 \u0438 open-source \u043f\u0440\u043e\u0435\u043a\u0442\u044b. \u0412 \u043a\u043e\u043d\u0446\u0435 \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0432\u043e\u043f\u0440\u043e\u0441\u0430\u0445 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f Serverless. \u042f \u0445\u043e\u0447\u0443 \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0443\u044e \u0447\u0430\u0441\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f (\u0434\u0430 \u0445\u043e\u0442\u044c \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043c\u0430\u0433\u0430\u0437\u0438\u043d\u0430).\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/serverless-po-stoechkam\" \/>\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-31T18:55:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:55:27+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\udd47Serverless n\u00eb rafte | ProHoster","description":"Serverless nuk do t\u00eb thot\u00eb munges\u00eb fizike t\u00eb server\u00ebve. Nuk \u00ebsht\u00eb nj\u00eb 'vras\u00ebs' i kontejner\u00ebve dhe as nj\u00eb trend kalimtar. Ky \u00ebsht\u00eb nj\u00eb qasje e re p\u00ebr nd\u00ebrtimin e sistemeve n\u00eb re. N\u00eb artikullin e sot\u00ebm do t\u00eb diskutojm\u00eb architektur\u00ebn e aplikacioneve Serverless, do t\u00eb shohim rolin e ofruesit t\u00eb sh\u00ebrbimeve Serverless dhe projekteve open-source. N\u00eb fund do t\u00eb flasim p\u00ebr \u00e7\u00ebshtjet e aplikimit t\u00eb Serverless. Dua t\u00eb shkruaj pjes\u00ebn e_backend_ t\u00eb aplikacionit (madje dhe nj\u00eb dyqan online).","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/serverless-po-stoechkam","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\udd47Serverless \u043f\u043e \u0441\u0442\u043e\u0435\u0447\u043a\u0430\u043c | ProHoster","og:description":"Serverless \u2015 \u044d\u0442\u043e \u043d\u0435 \u043f\u0440\u043e \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u043e\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432. \u042d\u0442\u043e \u043d\u0435 \u00ab\u0443\u0431\u0438\u0439\u0446\u0430\u00bb \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0438 \u043d\u0435 \u043c\u0438\u043c\u043e\u043b\u0435\u0442\u043d\u044b\u0439 \u0442\u0440\u0435\u043d\u0434. \u042d\u0442\u043e \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0434\u0445\u043e\u0434 \u043a \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044e \u0441\u0438\u0441\u0442\u0435\u043c \u0432 \u043e\u0431\u043b\u0430\u043a\u0435. \u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043a\u043e\u0441\u043d\u0435\u043c\u0441\u044f \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b Serverless-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0438\u043c, \u043a\u0430\u043a\u0443\u044e \u0440\u043e\u043b\u044c \u0438\u0433\u0440\u0430\u0435\u0442 \u043f\u0440\u043e\u0432\u0430\u0439\u0434\u0435\u0440 Serverless-\u0443\u0441\u043b\u0443\u0433\u0438 \u0438 open-source \u043f\u0440\u043e\u0435\u043a\u0442\u044b. \u0412 \u043a\u043e\u043d\u0446\u0435 \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0432\u043e\u043f\u0440\u043e\u0441\u0430\u0445 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f Serverless. \u042f \u0445\u043e\u0447\u0443 \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u0443\u044e \u0447\u0430\u0441\u0442\u044c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f (\u0434\u0430 \u0445\u043e\u0442\u044c \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043c\u0430\u0433\u0430\u0437\u0438\u043d\u0430).","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/serverless-po-stoechkam","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-31T18:55:27+00:00","article:modified_time":"2019-10-31T18:55:27+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"33935","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 17:17:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:31:21","updated":"2026-01-21 17:17:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/33935","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=33935"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/33935\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/25594"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=33935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=33935"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=33935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}