{"id":39302,"date":"2019-10-31T22:29:40","date_gmt":"2019-10-31T19:29:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh\/"},"modified":"2019-10-31T22:29:40","modified_gmt":"2019-10-31T19:29:40","slug":"kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh","title":{"rendered":"Si si AWS \"gatuan\" sh\u00ebrbimet e saj elastike. Zgjerimi i server\u00ebve dhe bazave t\u00eb t\u00eb dh\u00ebnave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Reformat jan\u00eb si nj\u00eb kuti magjike \u2014 k\u00ebrkon at\u00eb q\u00eb t\u00eb nevojitet dhe burimet thjesht shfaqen nga asgj\u00eb. Makina virtuale, bazat e t\u00eb dh\u00ebnave, rrjeti \u2014 gjith\u00e7ka i takon vet\u00ebm ty. Ka edhe tenda t\u00eb tjera n\u00eb re, por n\u00eb universin t\u00ebnd je sundimtari i vet\u00ebm. Je i sigurt se do t\u00eb marr\u00ebsh gjithmon\u00eb resurset e nevojshme, pa u shqet\u00ebsuar p\u00ebr ask\u00ebnd dhe e p\u00ebrcakton vet\u00eb se si do t\u00eb jet\u00eb rrjeti. Si funksionon kjo magji q\u00eb b\u00ebn q\u00eb reja t\u00eb alocoj\u00eb elastikisht resurset dhe t\u00eb izoloj\u00eb plot\u00ebsisht tenda nga nj\u00ebra-tjetra?<\/p>\n

\"Si
\n
\nReformat AWS \u00ebsht\u00eb nj\u00eb sistem super kompleks, i cili \u00ebsht\u00eb duke u zhvilluar evolutivisht q\u00eb nga viti 2006. Nj\u00eb pjes\u00eb e k\u00ebsaj zhvillimi e p\u00ebrjetoi Vasili Pantiukhin<\/strong> \u2014 arkitekt i Amazon Web Services. Si arkitekt, ai shikoni nga brenda jo vet\u00ebm rezultatet p\u00ebrfundimtare, por edhe sfidat q\u00eb kalon AWS. Sa m\u00eb shum\u00eb t\u00eb kuptoni funksionimin e sistemit, aq m\u00eb shum\u00eb besim do t\u00eb keni. Prandaj, Vasili do t\u00eb ndaj\u00eb sekretet e sh\u00ebrbimeve cloud t\u00eb AWS. N\u00ebn k\u00ebt\u00eb, do t\u00eb shqyrtojm\u00eb nd\u00ebrtimin e server\u00ebve fizik\u00eb t\u00eb AWS, elastikshm\u00ebrin\u00eb dhe shkall\u00ebzueshm\u00ebrin\u00eb e baz\u00ebs s\u00eb dh\u00ebnash, baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb personalizuara Amazon dhe metodat p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar performanc\u00ebn e makinave virtuale duke ulur nj\u00ebkoh\u00ebsisht kostot e tyre. Njohurit\u00eb mbi qasjet arkitektonike t\u00eb Amazon do t\u00eb ndihmojn\u00eb n\u00eb p\u00ebrdorimin m\u00eb efikas t\u00eb sh\u00ebrbimeve t\u00eb AWS dhe ndoshta do t\u00eb ofrojn\u00eb ide t\u00eb reja p\u00ebr nd\u00ebrtimin e zgjidhjeve tuaja t\u00eb veta.
\n<\/a><\/noindex>
\nRreth fol\u00ebsit: Vasili Pantyukhin (Hen<\/a><\/noindex>) filloi si administrator Unix n\u00eb kompanit\u00eb .ru, p\u00ebr 6 vjet u angazhua me pajisje t\u00eb m\u00ebdha Sun Microsystem, dhe p\u00ebr 11 vjet predikoi r\u00ebnd\u00ebsin\u00eb e qendrave t\u00eb t\u00eb dh\u00ebnave n\u00eb EMC. N\u00eb m\u00ebnyr\u00eb natyrale evoluoi n\u00eb cloud-e private dhe n\u00eb 2017 u p\u00ebrkushtua n\u00eb ato publike. Tani ofron k\u00ebshilla teknike p\u00ebr t\u00eb jetuar dhe zhvilluar n\u00eb cloud-in AWS.<\/p>\n

Diskleimer: gjith\u00e7ka m\u00eb posht\u00eb \u00ebsht\u00eb mendimi personal i Vasilit dhe mund t\u00eb mos p\u00ebrputhet me q\u00ebndrimin e Amazon Web Services. Regjistrimi video<\/a><\/noindex> i prezantimit, mbi t\u00eb cilin \u00ebsht\u00eb krijuar artikulli, \u00ebsht\u00eb n\u00eb dispozicion n\u00eb kanalin ton\u00eb YouTube.<\/i><\/p>\n

Pse po flas p\u00ebr aparatin Amazon<\/h2>\n

\nMakina ime e par\u00eb kishte \"dorez\u00eb\" \u2014 me transmetim mekanik. Ishte fantastike p\u00ebr shkak t\u00eb ndjenj\u00ebs se mund t\u00eb kontrolloja makin\u00ebn dhe ta menaxhoja plot\u00ebsisht. Gjithashtu, m\u00eb p\u00eblqente q\u00eb t\u00eb pakt\u00ebn e kuptoja n\u00eb nj\u00eb far\u00eb mase si funksiononte ajo. Natyrisht, e imagjinoja aparatin e kutis\u00eb mjaft primitivisht \u2014 nj\u00ebsoj si kutin\u00eb e transmetimit n\u00eb nj\u00eb bi\u00e7iklet\u00eb.<\/p>\n

\"Si
\n
\nIshte gjithcka e shk\u00eblqyer, p\u00ebrve\u00e7 nj\u00eb gj\u00ebje \u2014 q\u00ebndronte n\u00eb trafik. Duket sikur rri dhe nuk b\u00ebj asgj\u00eb, por vazhdimisht nd\u00ebrron transmetimet, shtyp pedalin e lidhjes, gazit, frenave \u2014 dhe kjo \u00ebsht\u00eb realisht lodh\u00ebse. Problemi i trafikut u zgjidh disi, kur n\u00eb familje erdhi nj\u00eb makin\u00eb me automatik. Pas timonit fillova t\u00eb kisha koh\u00eb t\u00eb mendoja p\u00ebr di\u00e7ka, t\u00eb d\u00ebgjoja audiokitabe.<\/p>\n

Gjithashtu, n\u00eb jet\u00ebn time u shfaq nj\u00eb mister, sepse un\u00eb n\u00eb p\u00ebrgjith\u00ebsi e humba kuptimin se si funksionon makina ime. Automjeti modern \u00ebsht\u00eb nj\u00eb aparat kompleks. Makina p\u00ebrshtatet nj\u00ebkoh\u00ebsisht me dhjet\u00ebra parametra t\u00eb ndrysh\u00ebm: shtypja e gazit, frenimi, stili i drejtimit, cil\u00ebsia e rrug\u00ebs. Tani nuk e kuptoj m\u00eb se si funksionon.<\/p>\n

Kur fillova t\u00eb merrem me Amazon Cloud, edhe p\u00ebr mua kjo ishte nj\u00eb mister. Vet\u00ebm ky mister \u00ebsht\u00eb n\u00eb nj\u00eb shkall\u00eb m\u00eb t\u00eb lart\u00eb, sepse n\u00eb makin\u00eb ka nj\u00eb drejtues, nd\u00ebrsa n\u00eb AWS jan\u00eb miliona. T\u00eb gjith\u00eb p\u00ebrdoruesit nj\u00ebkoh\u00ebsisht drejtojn\u00eb, shtypin gazin dhe frenin. \u00cbsht\u00eb e habitshme se ata shkojn\u00eb atje ku duan \u2014 p\u00ebr mua kjo \u00ebsht\u00eb nj\u00eb mrekulli! Sistemi automatikisht adaptohet, skalon dhe p\u00ebrshtatet elastikisht me \u00e7do p\u00ebrdorues, saq\u00eb atij i duket se \u00ebsht\u00eb vet\u00ebm ai n\u00eb k\u00ebt\u00eb Univers.<\/p>\n

Magjia paksa u shp\u00ebrb\u00eb kur m\u00eb von\u00eb erdha t\u00eb punoja si arkitekt n\u00eb Amazon. Pash\u00eb se me cilat probleme p\u00ebrballeshim, si i zgjidhnim ato dhe si zhvillonim sh\u00ebrbimet. Me rritjen e kuptimit t\u00eb funksionit t\u00eb sistemit, besimi n\u00eb sh\u00ebrbim rritet. Prandaj d\u00ebshiroj t\u00eb ndaj nj\u00eb pamje t\u00eb atij q\u00eb ndodhet n\u00ebn kapak\u00ebt e AWS Cloud.<\/p>\n

P\u00ebr \u00e7far\u00eb do t\u00eb flasim<\/h2>\n

\nKam zgjedhur nj\u00eb qasje t\u00eb diversifikuar \u2014 kam p\u00ebrzgjedhur 4 sh\u00ebrbime interesante q\u00eb meritojn\u00eb t\u00eb flasim.<\/p>\n

Optimizimi i server\u00ebve<\/strong>. Cloud-et efemere me nj\u00eb ekzistenc\u00eb fizike: qendrat e t\u00eb dh\u00ebnave fizike, ku ndodhen server\u00eb fizik\u00eb, t\u00eb cil\u00ebt humbin, ngrohen dhe ndri\u00e7ohen me drita.<\/p>\n

Funksionet pa server <\/strong>(Lambda) \u2014 ndoshta sh\u00ebrbimi m\u00eb i shkall\u00ebzuar n\u00eb cloud.<\/p>\n

Zgjerimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave<\/strong>. Do t'ju tregoj se si krijojm\u00eb bazat tona t\u00eb dh\u00ebnash t\u00eb zgjerueshme.<\/p>\n

Zgjerimi i rrjetit<\/strong>. Pjesa e fundit, ku do t\u00eb zbuloj struktur\u00ebn e rrjetit ton\u00eb. Kjo \u00ebsht\u00eb nj\u00eb gj\u00eb e mrekullueshme \u2014 secili p\u00ebrdorues i njohur i cloud-it mendon se \u00ebsht\u00eb n\u00eb cloud vet\u00ebm dhe nuk sheh tenant\u00eb t\u00eb tjer\u00eb.<\/p>\n

Sh\u00ebnim. N\u00eb k\u00ebt\u00eb artikull do t\u00eb flas p\u00ebr optimizimin e server\u00ebve dhe zgjerimin e bazave t\u00eb t\u00eb dh\u00ebnave. Zgjerimin e rrjetit do ta trajtojm\u00eb n\u00eb artikullin e ardhsh\u00ebm. Ku jan\u00eb funksionet serverless? P\u00ebr to ka dal\u00eb nj\u00eb shkrim i ve\u00e7ant\u00eb \"I vog\u00ebl, por i fuqish\u00ebm. Unboxing mikrovirtualizuesi Firecracker<\/a><\/noindex>\". N\u00eb t\u00eb jan\u00eb treguar disa m\u00ebnyra t\u00eb ndryshme t\u00eb zgjerimit dhe \u00ebsht\u00eb shqyrtuar me detaje zgjidhja Firecracker \u2014 nj\u00eb simbioz\u00eb e cil\u00ebsive m\u00eb t\u00eb mira t\u00eb makinerive virtuale dhe konteiner\u00ebve.<\/i><\/p><\/blockquote>\n

<\/p>\n

Server\u00ebt<\/h2>\n

\nCloud-i \u00ebsht\u00eb efemer. Por kjo efem\u00ebsi ka nj\u00eb shprehje fizike \u2014 server\u00ebt. Fillimisht, arkitektura e tyre ishte klasike. Nj\u00eb chipset standard x86, karta rrjeti, Linux, hypervizori Xen, mbi t\u00eb cilin ishin aktivizuar makinerit\u00eb virtuale.<\/p>\n

\"Si
\n
\nN\u00eb vitin 2012, nj\u00eb arkitektur\u00eb e till\u00eb p\u00ebrballonte plot\u00ebsisht detyrat e saj. Xen \u00ebsht\u00eb nj\u00eb hypervizor i shk\u00eblqyer, por me nj\u00eb disavantazh t\u00eb r\u00ebnd\u00ebsish\u00ebm. Ai ka mjaft shpenzime t\u00eb larta p\u00ebr emulimin e pajisjeve<\/strong>. Me shfaqjen e kartave rrjet m\u00eb t\u00eb shpejta ose SSD-ve, k\u00ebto shpenzime b\u00ebhen shum\u00eb t\u00eb larta. Si t\u00eb veprojm\u00eb me k\u00ebt\u00eb problem? Vendos\u00ebm t\u00eb punojm\u00eb n\u00eb dy fronte \u2014 optimizimin e harduerit dhe hipervizorit<\/strong>. Detyra \u00ebsht\u00eb shum\u00eb serioze.<\/p>\n

Optimizimi i harduerit dhe hipervizorit<\/h3>\n

\nNuk \u00ebsht\u00eb e mundur t\u00eb b\u00ebhet gjith\u00e7ka menj\u00ebher\u00eb dhe mir\u00eb. \u00c7far\u00eb do t\u00eb thot\u00eb \u00abmir\u00eb\u00bb, gjithashtu nuk ishte e qart\u00eb n\u00eb fillim.<\/p>\n

Vendos\u00ebm t\u00eb aplikojm\u00eb nj\u00eb qasje evolucionare \u2014 ndryshojm\u00eb nj\u00eb element t\u00eb r\u00ebnd\u00ebsish\u00ebm t\u00eb arkitektur\u00ebs dhe e nxjerrim n\u00eb prodhim.<\/p><\/blockquote>\n

Hapim t\u00eb gjitha pengesat, d\u00ebgjojm\u00eb ankesat dhe propozimet. Pastaj ndryshojm\u00eb nj\u00eb komponent tjet\u00ebr. K\u00ebshtu, me inkrementet e vogla, radikalisht ndryshojm\u00eb t\u00eb gjith\u00eb arkitektur\u00ebn mbi baz\u00ebn e reagimeve nga p\u00ebrdoruesit dhe mb\u00ebshtetjes.<\/p>\n

Transformimet filluan n\u00eb 2013 me gj\u00ebn\u00eb m\u00eb t\u00eb komplikuar \u2014 rrjeti. N\u00eb C3<\/strong> instance, iu shtua nj\u00eb kart\u00eb e ve\u00e7ant\u00eb Network Accelerator, e cila lidhej me nj\u00eb kabllo t\u00eb shkurt\u00ebr loopback n\u00eb panelet e p\u00ebrparme. Nuk duket bukur, por nuk \u00ebsht\u00eb e dukshme n\u00eb cloud. Megjithat\u00eb, interaksioni i drejtp\u00ebrdrejt\u00eb me harduerin p\u00ebrmir\u00ebsoi ndjesh\u00ebm jitter-in dhe kapacitetin e rrjetit.<\/p>\n

M\u00eb pas, vendos\u00ebm t\u00eb p\u00ebrmir\u00ebsojm\u00eb qasjen n\u00eb ruajtjen e blokut EBS \u2014 Elastic Block Storage. Kjo \u00ebsht\u00eb nj\u00eb kombinim i rrjetit dhe ruajtjes. V\u00ebshtir\u00ebsia ishte se, ndon\u00ebse n\u00eb treg ekzistonin karta Network Accelerator, nuk kishte mund\u00ebsi t\u00eb blenim harduer Storage Accelerator. Prandaj, iu drejtua nj\u00eb startup Annapurna Labs<\/strong>, i cili zhvilloi p\u00ebr ne \u00e7ipe t\u00eb ve\u00e7anta ASIC. K\u00ebta na lejuan t\u00eb lidhnim volume t\u00eb larg\u00ebta EBS si pajisje NVMe.<\/p>\n

N\u00eb instancat C4<\/strong> , zgjidh\u00ebm dy \u00e7\u00ebshtje. S\u00eb pari \u2014 realizuam nj\u00eb p\u00ebrgatitje p\u00ebr t\u00eb ardhmen t\u00eb teknologjis\u00eb NVMe, q\u00eb ishte e re n\u00eb at\u00eb koh\u00eb. S\u00eb dyti \u2014 ngarkuam ndjesh\u00ebm procesorin qendror duke transferuar p\u00ebrpunimin e k\u00ebrkesave p\u00ebr EBS n\u00eb kart\u00ebn e re. Kjo rezultoi me sukses, ndaj tani Annapurna Labs \u00ebsht\u00eb pjes\u00eb e Amazon.<\/p>\n

Derisa arrit\u00ebm n\u00eb n\u00ebntor 2017, kuptuam se ishte koha t\u00eb ndryshonim edhe hipervizorin.<\/p>\n

Hipervizori i ri u zhvillua mbi modulat e p\u00ebrmir\u00ebsuara t\u00eb kernelit KVM.<\/p><\/blockquote>\n

Ai lejojti nj\u00eb ulje t\u00eb r\u00ebnd\u00ebsishme t\u00eb kostove t\u00eb simulimit t\u00eb pajisjeve dhe t\u00eb punonte direkt me ASIC t\u00eb rinj. Instancat C5<\/strong> ishin virtualizimet e para, n\u00ebn kapak t\u00eb cilave funksiononte hipervizori i ri. Ne e quajt\u00ebm at\u00eb Nitro<\/strong>.<\/p>\n

\"SiEvolucioni i instancave n\u00eb nj\u00eb vij\u00eb kohore.<\/em><\/p>\n

T\u00eb gjitha llojet e reja t\u00eb makinave virtuale, t\u00eb cilat jan\u00eb shfaqur q\u00eb nga n\u00ebntori 2017, punojn\u00eb mbi k\u00ebt\u00eb hypervisor. Instancat e nd\u00ebrlikuara Bare Metal nuk kan\u00eb nj\u00eb hypervisor<\/strong>, por ato quhen gjithashtu Nitro, pasi p\u00ebrdorin karta t\u00eb specializuara Nitro.<\/p>\n

N\u00eb dy vitet e ardhshme, numri i llojeve t\u00eb instancave Nitro e kaloi disa dhjet\u00ebra: A1, C5, M5, T3 dhe t\u00eb tjer\u00eb.<\/p>\n

\"Si
\nLlojet e instancave.<\/em><\/p>\n

Si jan\u00eb nd\u00ebrtuar makinat moderne Nitro<\/h3>\n

\nAto kan\u00eb tre komponent\u00eb kryesor\u00eb: hypervisori Nitro (p\u00ebr t\u00eb cilin u p\u00ebrmend m\u00eb par\u00eb), \u00e7ipi i siguris\u00eb dhe kartat Nitro.<\/p>\n

\u00c7ipi i siguris\u00eb<\/strong> \u00ebsht\u00eb i integruar direkt n\u00eb pllak\u00ebn e n\u00ebn\u00ebs. Ai kontrollon shum\u00eb funksione t\u00eb r\u00ebnd\u00ebsishme, p\u00ebr shembull, kontrollin e ngarkes\u00ebs s\u00eb sistemit operativ host.<\/p>\n

Kartat Nitro<\/strong> \u2014 ekzistojn\u00eb kat\u00ebr lloje t\u00eb tyre. T\u00eb gjitha jan\u00eb zhvilluar nga Annapurna Labs dhe bazohen n\u00eb ASIC t\u00eb p\u00ebrbashk\u00ebt. Disa nga firmware e tyre gjithashtu \u00ebsht\u00eb e p\u00ebrbashk\u00ebt.<\/p>\n

\"Si
\nKat\u00ebr lloje t\u00eb kartave Nitro.<\/em><\/p>\n

Nj\u00eb nga kartat \u00ebsht\u00eb e destinuar p\u00ebr t\u00eb punuar me rrjetin<\/strong>VPC<\/strong>. Pik\u00ebrisht ajo duket n\u00eb virtualka si karta rrjeti ENA \u2014 Elastic Network Adaptor<\/strong>. Ajo gjithashtu inkapsulon trafikun kur e transferon at\u00eb p\u00ebrmes rrjetit fizik (p\u00ebr k\u00ebt\u00eb do t\u00eb flasim n\u00eb pjes\u00ebn e dyt\u00eb t\u00eb artikullit), kontrollon firewall Security Groups, p\u00ebrgjigjet p\u00ebr ruterin dhe \u00e7\u00ebshtje t\u00eb tjera rrjetesh.<\/p>\n

Kartat individuale funksionojn\u00eb me ruajtjen bllok EBS<\/strong> dhe disqet q\u00eb jan\u00eb t\u00eb nd\u00ebrtuara n\u00eb server. Ato paraqiten n\u00eb makinat virtuale si adapter\u00eb NVMe<\/strong>. Po ashtu, ato jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr enkriptimin e t\u00eb dh\u00ebnave dhe monitorimin e disqeve.<\/p>\n

Sistemi i kartave Nitro, hipervizori dhe \u00e7ipi i siguris\u00eb jan\u00eb t\u00eb lidhura n\u00eb nj\u00eb rrjet SDN ose Rrjet t\u00eb Definuar me Program<\/strong>. Menaxhimi i k\u00ebtij rrjeti (Control Plane) \u00ebsht\u00eb i p\u00ebrgjegjsh\u00ebm nga karta-kontrollore<\/strong>.<\/p>\n

Sigurisht, ne vazhdojm\u00eb zhvillimin e ASIC t\u00eb rinj. P\u00ebr shembull, n\u00eb fund t\u00eb vitit 2018, publikuan \u00e7ipin Inferentia, i cili leht\u00ebson pun\u00ebn me detyrat e m\u00ebsimit automat.<\/p>\n

\"Si
\n\u00c7ipi Inferentia Procesori i M\u00ebsimit Automat.<\/em><\/p>\n

Baza e t\u00eb dh\u00ebnave e shkall\u00ebzuar<\/h2>\n

\nNj\u00eb baz\u00eb e dh\u00ebnash tradicionale ka nj\u00eb struktur\u00eb t\u00eb stratifikuar. N\u00ebse e thjeshtojm\u00eb shum\u00eb, mund t\u00eb identifikojm\u00eb nivelet e m\u00ebposhtme.<\/p>\n