{"id":35092,"date":"2019-10-31T22:02:18","date_gmt":"2019-10-31T19:02:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim\/"},"modified":"2019-10-31T22:02:18","modified_gmt":"2019-10-31T19:02:18","slug":"bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","title":{"rendered":"\u00abBitrix24\u00bb: \u00abNj\u00eb gj\u00eb e ngritur shpejt nuk konsiderohet e r\u00ebn\u00eb\u00bb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb dit\u00ebt e sotme, sh\u00ebrbimi \"Bitrix24\" nuk ka qindra gigabit trafik dhe as nj\u00eb park t\u00eb madh serverash (edhe pse, natyrisht, ka s\u00ebrish mjaft). Megjithat\u00eb, p\u00ebr shum\u00eb klient\u00eb, ai \u00ebsht\u00eb mjeti kryesor p\u00ebr pun\u00ebn n\u00eb kompani; \u00ebsht\u00eb nj\u00eb aplikacion q\u00eb ka r\u00ebnd\u00ebsi kritike p\u00ebr biznesin. Prandaj, nuk ka m\u00ebnyr\u00eb q\u00eb t\u00eb d\u00ebshtoj\u00eb. E \u00e7far\u00eb ndodh n\u00ebse ndodhi nj\u00eb r\u00ebnie, por sh\u00ebrbimi u rikthye aq shpejt sa askush nuk e vuri re? Dhe si realizohet ndarja n\u00eb rast r\u00ebnies pa humbur cil\u00ebsin\u00eb e pun\u00ebs dhe numrin e klient\u00ebve? Aleksand\u00ebr Demidov, drejtori i deg\u00ebs s\u00eb sh\u00ebrbimeve n\u00eb cloud t\u00eb \"Bitrix24\", rr\u00ebfeu p\u00ebr blogun ton\u00eb se si \u00ebsht\u00eb evolucionuar sistemi i rezervave gjat\u00eb 7 vjet\u00ebve t\u00eb ekzistenc\u00ebs s\u00eb produktit.<\/p>\n

\"\u00abBitrix24\u00bb:
\n<\/a><\/noindex>
\nSi sh\u00ebrbim SaaS, ne lan\u00e7uam \"Bitrix24\" 7 vjet m\u00eb par\u00eb. Sfidat kryesore ndoshta ishin k\u00ebto: para lan\u00e7imit n\u00eb publik si SaaS, ky produkt ekzistonte thjesht n\u00eb formatin e nj\u00eb zgjidhjeje me kutin\u00eb. Klient\u00ebt e blinin prej nesh, e instalonin n\u00eb server\u00ebt e tyre, krijonin nj\u00eb portal korporativ \u2014 nj\u00eb zgjidhje e p\u00ebrbashk\u00ebt p\u00ebr komunikimin e punonj\u00ebsve, ruajtjen e skedar\u00ebve, menaxhimin e detyrave, CRM, dhe k\u00ebshtu me radh\u00eb. Dhe deri n\u00eb vitin 2012 vendos\u00ebm q\u00eb d\u00ebshironim ta lan\u00e7ojm\u00eb k\u00ebt\u00eb si SaaS, me menaxhimin e vet, duke siguruar q\u00ebndrueshm\u00ebri dhe besueshm\u00ebri. P\u00ebrvoja e fituam n\u00eb proces, sepse deri at\u00ebher\u00eb ne thjesht nuk e kishim \u2014 ishim vet\u00ebm prodhues t\u00eb softuerit, jo ofrues sh\u00ebrbimesh. <\/p>\n

Kur filluam sh\u00ebrbimin, e kuptonim se m\u00eb e r\u00ebnd\u00ebsishme \u00ebsht\u00eb t\u00eb sigurojm\u00eb q\u00eb sh\u00ebrbimi t\u00eb jet\u00eb i disponuesh\u00ebm, i besuesh\u00ebm dhe konstant, sepse n\u00ebse keni nj\u00eb faqe t\u00eb zakonshme, nj\u00eb dyqan, p\u00ebr shembull, dhe ajo bie p\u00ebr nj\u00eb or\u00eb, vuani vet\u00ebm ju, humbni porosit\u00eb, humbni klient\u00ebt, por p\u00ebr vet\u00eb klientin tuaj \u2014 p\u00ebr t\u00eb nuk \u00ebsht\u00eb shum\u00eb kritike. Sigurisht, ai m\u00ebrzitet, por shkon dhe blen n\u00eb nj\u00eb faqe tjet\u00ebr. Por n\u00ebse \u00ebsht\u00eb nj\u00eb aplikacion, n\u00eb t\u00eb cilin \u00ebsht\u00eb e varur e gjith\u00eb puna brenda kompanis\u00eb, komunikimet, vendimet, at\u00ebher\u00eb \u00e7el\u00ebsi \u00ebsht\u00eb t\u00eb fitoni besimin e p\u00ebrdoruesve, dometh\u00ebn\u00eb t\u00eb mos i lini ata n\u00eb balt\u00eb dhe t\u00eb mos d\u00ebshtoni. Sepse e gjith\u00eb puna mund t\u00eb ndaloj\u00eb n\u00ebse di\u00e7ka brenda nuk funksionon.<\/p>\n

Bitrix.24 si SaaS<\/h4>\n

\nPrototipi i par\u00eb e kemi nd\u00ebrtuar nj\u00eb vit para lan\u00e7imit publik, n\u00eb vitin 2011. E p\u00ebrfunduam p\u00ebr rreth nj\u00eb jav\u00eb, e shikuam, e kthyem - madje ishte funksional. Pra, mund t\u00eb shkoje n\u00eb form\u00eb, t\u00eb shkruaje emrin e portalit, dhe krijohej nj\u00eb portal i ri, duke u krijuar nj\u00eb baz\u00eb p\u00ebrdoruesish. E shikuam, e vler\u00ebsuam n\u00eb thelb produktin, e mbyll\u00ebm dhe kaluam nj\u00eb vit tjet\u00ebr p\u00ebr ta q\u00ebndruar p\u00ebrpara. Sepse kishim nj\u00eb detyr\u00eb t\u00eb madhe: nuk donim t\u00eb b\u00ebnim dy baza t\u00eb ndryshme kodesh, nuk donim t\u00eb mb\u00ebshtesim produkte t\u00eb ndryshme, ve\u00e7mas, zgjidhje cloud - ne donim ta b\u00ebnim gjith\u00eb k\u00ebt\u00eb brenda nj\u00eb kode. <\/p>\n

\"\u00abBitrix24\u00bb:
\n
\nNj\u00eb aplikacion web tipik n\u00eb at\u00eb koh\u00eb ishte nj\u00eb server, ku filmonte ndonj\u00eb kod php, baza mysql, skedar\u00ebt ngarkoheshin, dokumentet, imazhet vendoseshin n\u00eb dosjen upload - dhe gjith\u00e7ka funksiononte. P\u00ebr fat t\u00eb keq, nuk \u00ebsht\u00eb e mundur t\u00eb nisni nj\u00eb sh\u00ebrbim web kritikisht t\u00eb q\u00ebndruesh\u00ebm n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb. Nuk mb\u00ebshtetet caching i shp\u00ebrndar\u00eb, nuk mb\u00ebshtetet replikimi i bazave t\u00eb t\u00eb dh\u00ebnave. <\/p>\n

Ne kemi formuluar k\u00ebrkesat: kjo \u00ebsht\u00eb aft\u00ebsia p\u00ebr t'u vendosur n\u00eb vende t\u00eb ndryshme, p\u00ebr t\u00eb mb\u00ebshtetur replikimin, idealisht t\u00eb vendoset n\u00eb qendra t\u00eb t\u00eb dh\u00ebnave geografi t\u00eb shp\u00ebrndara. T\u00eb ndajm\u00eb logjik\u00ebn e produktit dhe, n\u00eb thelb, ruajtjen e t\u00eb dh\u00ebnave. T\u00eb jemi n\u00eb gjendje t\u00eb shp\u00ebrndajm\u00eb dinamikisht ngarkesat, duke nxjerr\u00eb jasht\u00eb statik\u00ebn. Nga k\u00ebto konsiderata jan\u00eb formuar, n\u00eb thelb, k\u00ebrkesat p\u00ebr produktin, t\u00eb cilin ne e kemi p\u00ebrmir\u00ebsuar p\u00ebr nj\u00eb vit. Gjat\u00eb k\u00ebtij koh\u00eb, ne krijuam nj\u00eb platform\u00eb t\u00eb unifikuar \u2014 p\u00ebr zgjidhje kutish, p\u00ebr sh\u00ebrbimin ton\u00eb vetjak \u2014 ku kemi b\u00ebr\u00eb mb\u00ebshtetje p\u00ebr ato gj\u00ebra q\u00eb na ishin t\u00eb nevojshme. Mb\u00ebshtetje p\u00ebr replikimin MySQL n\u00eb nivelin e vet\u00eb produktit: pra, programuesi, i cili shkruan kod, nuk mendon se si do t\u00eb shp\u00ebrndahen k\u00ebrkesat e tij, ai p\u00ebrdor API-n ton\u00eb, dhe ne dim\u00eb t\u00eb shp\u00ebrndajm\u00eb sakt\u00eb k\u00ebrkesat p\u00ebr shkrim dhe p\u00ebr lexim midis Master-ave dhe Slave-ave. <\/p>\n

Ne kemi implementuar mb\u00ebshtetje p\u00ebr nivele t\u00eb ndryshme produktesh t\u00eb magazinave objektive cloud: Google Storage, Amazon S3, dhe gjithashtu mb\u00ebshtetje p\u00ebr Open Stack Swift. K\u00ebshtu q\u00eb kjo ishte e p\u00ebrshtatshme si p\u00ebr ne si sh\u00ebrbim, ashtu dhe p\u00ebr zhvilluesit q\u00eb punojn\u00eb me zgjidhje t\u00eb paketuara: n\u00ebse ata p\u00ebrdorin vet\u00ebm API-n\u00eb ton\u00eb, ata nuk mendojn\u00eb se ku do t\u00eb ruhet p\u00ebrfundimisht skedari, n\u00eb sisteme lokale t\u00eb skedar\u00ebve apo do t\u00eb shkonte n\u00eb nj\u00eb magazin\u00eb objektive skedar\u00ebsh.<\/p>\n

N\u00eb p\u00ebrfundim, ne menj\u00ebher\u00eb vendos\u00ebm q\u00eb do t\u00eb rezervojm\u00eb n\u00eb nivelin e nj\u00eb qendre t\u00eb t\u00ebr\u00eb t\u00eb t\u00eb dh\u00ebnave. N\u00eb vitin 2012, ne u nis\u00ebm plot\u00ebsisht n\u00eb Amazon AWS, sepse tashm\u00eb kishim p\u00ebrvoj\u00eb me k\u00ebt\u00eb platform\u00eb - faqja jon\u00eb e internetit ishte vendosur aty. Na t\u00ebrhiqte se n\u00eb \u00e7do rajon n\u00eb Amazon ka disa zona disponueshm\u00ebrie - n\u00eb thelb, (n\u00eb terminologjin\u00eb e tyre) disa qendra t\u00eb t\u00eb dh\u00ebnave, t\u00eb cilat jan\u00eb m\u00eb pak ose m\u00eb shum\u00eb t\u00eb pavarura nga nj\u00ebra-tjetra dhe na lejojn\u00eb t\u00eb rezervojm\u00eb n\u00eb nivelin e nj\u00eb qendre t\u00eb t\u00ebr\u00eb t\u00eb t\u00eb dh\u00ebnave: n\u00ebse ndonj\u00ebher\u00eb d\u00ebshton, bazat replikohen master-master, server\u00ebt e aplikacioneve t\u00eb uebit jan\u00eb t\u00eb rezervuar, dhe statika ka kaluar n\u00eb magazin\u00ebn objektive s3. Ngarkesa balancohet - n\u00eb at\u00eb koh\u00eb me elb t\u00eb Amazon-it, por pak m\u00eb von\u00eb erdh\u00ebm te balancuesit tan\u00eb, sepse na nevojitej nj\u00eb logjik\u00eb m\u00eb e komplikuar. <\/p>\n

\u00c7far\u00eb d\u00ebshiruam - at\u00eb edhe mor\u00ebm...<\/h4>\n

\nT\u00eb gjitha gj\u00ebrat bazike q\u00eb donim t\u00eb siguronim - q\u00ebndrueshm\u00ebria e vet server\u00ebve, aplikacioneve t\u00eb uebit, bazave t\u00eb t\u00eb dh\u00ebnave - t\u00eb gjitha funksiononin mir\u00eb. Scenari m\u00eb i thjesht\u00eb: n\u00ebse ndonj\u00eb aplikacion uebi d\u00ebshton, at\u00ebher\u00eb k\u00ebtu \u00ebsht\u00eb e thjesht\u00eb - ato fik\u00ebn nga balancimi. <\/p>\n

\"\u00abBitrix24\u00bb:
\n
\nMakinat e balansimit q\u00eb kan\u00eb dal\u00eb nga funksioni (at\u00ebher\u00eb ishte elb nga Amazon) vet\u00eb i sh\u00ebnonte si t\u00eb pamundur, duke ndaluar shp\u00ebrndarjen e ngarkes\u00ebs tek ato. Funksiononte automatikisht skelimi i Amazon: kur ngarkesa rritej, shtoheshin makina t\u00eb reja n\u00eb grupin e skelimit, ngarkesa shp\u00ebrndaxehej te makinat e reja - gjith\u00e7ka ishte mir\u00eb. Logjika jon\u00eb e balansuesve \u00ebsht\u00eb p\u00ebraf\u00ebrsisht e nj\u00ebjt\u00eb: n\u00ebse ndodh di\u00e7ka me serverin e aplikacioneve, ne heqim k\u00ebrkesat nga ai, e largojm\u00eb at\u00eb makin\u00eb, fillojm\u00eb makina t\u00eb reja dhe vazhdojm\u00eb t\u00eb punojm\u00eb. Plani ka ndryshuar pak gjat\u00eb k\u00ebtyre viteve, por vazhdon t\u00eb funksionoj\u00eb: \u00ebsht\u00eb i thjesht\u00eb, i qart\u00eb, dhe nuk ka asnj\u00eb sfid\u00eb me t\u00eb. <\/p>\n

Ne punojm\u00eb n\u00eb t\u00eb gjith\u00eb bot\u00ebn, piket e ngarkes\u00ebs s\u00eb klient\u00ebve jan\u00eb plot\u00ebsisht t\u00eb ndryshme, dhe, p\u00ebr t\u00eb q\u00ebn\u00eb t\u00eb sinqert\u00eb, ne duhet t\u00eb kemi mund\u00ebsin\u00eb t\u00eb kryejm\u00eb punime sh\u00ebrbimi me \u00e7do komponent t\u00eb sistemit ton\u00eb n\u00eb \u00e7do koh\u00eb - pa u v\u00ebn\u00eb re nga klient\u00ebt. Prandaj kemi mund\u00ebsi t\u00eb fikim baz\u00ebn e t\u00eb dh\u00ebnave, duke ripjeshkatuar ngarkes\u00ebn n\u00eb qendr\u00ebn e dyt\u00eb t\u00eb t\u00eb dh\u00ebnave. <\/p>\n

Si si funksionon gjith\u00e7ka? \u2014 Ne kalojm\u00eb trafikun n\u00eb qend\u00ebr t\u00eb t\u00eb dh\u00ebnave q\u00eb punon \u2014 n\u00ebse ka nj\u00eb fatkeq\u00ebsi n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave, at\u00ebher\u00eb krejt\u00ebsisht, n\u00ebse jan\u00eb pun\u00eb t\u00eb planifikuara n\u00eb ndonj\u00eb baz\u00eb t\u00eb dh\u00ebnash, at\u00ebher\u00eb ne kalojm\u00eb nj\u00eb pjes\u00eb t\u00eb trafikut q\u00eb sh\u00ebrben p\u00ebr k\u00ebta klient\u00eb n\u00eb qendr\u00ebn e dyt\u00eb t\u00eb t\u00eb dh\u00ebnave, dhe ndalim replikimin. N\u00ebse k\u00ebrkohen makina t\u00eb reja p\u00ebr aplikacione web, pasi \u00ebsht\u00eb rritur ngarkesa n\u00eb qendr\u00ebn e dyt\u00eb t\u00eb t\u00eb dh\u00ebnave, ato startojn\u00eb automatikisht. Puna p\u00ebrfundon, replikimi rikthehet, dhe ne kthejm\u00eb t\u00eb gjith\u00eb ngarkes\u00ebn prapa. N\u00ebse na nevojitet t\u00eb b\u00ebjm\u00eb pun\u00eb t\u00eb ngjashme n\u00eb qendr\u00ebn e dyt\u00eb t\u00eb t\u00eb dh\u00ebnave, p\u00ebr shembull, p\u00ebr t\u00eb instaluar p\u00ebrdit\u00ebsime sistemore ose p\u00ebr t\u00eb ndryshuar cil\u00ebsimet n\u00eb baz\u00ebn e dyt\u00eb t\u00eb dh\u00ebnash, ne, n\u00eb p\u00ebrgjith\u00ebsi, p\u00ebrs\u00ebrisim t\u00eb nj\u00ebjt\u00ebn gj\u00eb, vet\u00ebm n\u00eb drejtim t\u00eb lart\u00eb. Por n\u00ebse ka nj\u00eb fatkeq\u00ebsi, at\u00ebher\u00eb ne b\u00ebjm\u00eb gjith\u00e7ka thjesht: n\u00eb sistemin e monitorimit p\u00ebrdorim mekanizmin e menaxher\u00ebve t\u00eb ngjarjeve. N\u00ebse disa kontrolle aktivizohen dhe statusi kalon n\u00eb kritike, at\u00ebher\u00eb aktivizohet ky menaxher, q\u00eb mund t\u00eb realizoj\u00eb logjik\u00ebn e caktuar. P\u00ebr \u00e7do baz\u00eb t\u00eb dh\u00ebnash kemi rregulluar se cili server \u00ebsht\u00eb failover p\u00ebr t\u00eb dhe ku duhet t\u00eb kalojm\u00eb trafikun n\u00eb rast se ajo b\u00ebhet e pamundur. Ne \u2014 p\u00ebr shkak t\u00eb historis\u00eb \u2014 p\u00ebrdorim n\u00eb nj\u00eb far\u00eb m\u00ebnyre nagios ose ndonj\u00eb nga n\u00ebnformat e tij. N\u00eb principe, mekanizma t\u00eb till\u00eb ka n\u00eb praktikisht \u00e7do sistem monitorimi, por ne p\u00ebr momentin nuk p\u00ebrdorim di\u00e7ka m\u00eb t\u00eb komplikuar, megjithat\u00eb ndoshta do t\u00eb fillojm\u00eb ndonj\u00ebher\u00eb. Tani monitorimi aktivizohet n\u00eb rastin e pamund\u00ebsis\u00eb dhe ka mund\u00ebsin\u00eb t\u00eb kaloj\u00eb di\u00e7ka.<\/p>\n

A \u00ebsht\u00eb rezervuar gjith\u00e7ka prej nesh?<\/h4>\n

\nNe kemi shum\u00eb klient\u00eb nga SHBA, shum\u00eb klient\u00eb nga Europa, shum\u00eb klient\u00eb q\u00eb jan\u00eb m\u00eb af\u00ebr Lindjes \u2014 Japonia, Singapori dhe k\u00ebshtu me radh\u00eb. Natyrisht, nj\u00eb pjes\u00eb e madhe e klient\u00ebve jan\u00eb n\u00eb Rusi. Pra, puna jon\u00eb shtrihet n\u00eb shum\u00eb rajone t\u00eb ndryshme. P\u00ebrdoruesit duan nj\u00eb reagim t\u00eb shpejt\u00eb, ka k\u00ebrkesa p\u00ebr p\u00ebrputhjen me ligjet lokale t\u00eb ndryshme, dhe brenda \u00e7do rajoni ne rezervojm\u00eb dy qendra t\u00eb dh\u00ebnash, plus ka disa sh\u00ebrbime shtes\u00eb, q\u00eb gjithashtu \u00ebsht\u00eb e p\u00ebrshtatshme t\u2019i vendosim brenda nj\u00eb rajoni \u2014 p\u00ebr klient\u00ebt q\u00eb punojn\u00eb n\u00eb at\u00eb rajon. Trajner\u00ebt REST, server\u00ebt e autorizimit, nuk jan\u00eb aq kritik\u00eb p\u00ebr funksionimin e klientit n\u00eb p\u00ebrgjith\u00ebsi, p\u00ebr to mund t\u00eb kalojm\u00eb me nj\u00eb vones\u00eb t\u00eb pranuar, por nuk duam t\u00eb shpikim bi\u00e7ikleta, si t\u2019i monitorojm\u00eb dhe \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb me to. K\u00ebshtu q\u00eb n\u00eb maksimum ne mundohemi t\u00eb p\u00ebrdorim zgjidhje ekzistuese, dhe jo t\u00eb zhvillojm\u00eb ndonj\u00eb kompetenc\u00eb p\u00ebr produkte shtes\u00eb n\u00eb vetveten ton\u00eb. Diku ne thjesht p\u00ebrdorim kalimin n\u00eb nivelin dns, nd\u00ebrsa aktiviteti i sh\u00ebrbimit p\u00ebrcaktohet nga t\u00eb nj\u00ebjtin dns. N\u00eb Amazon ka sh\u00ebrbimin Route 53, por ajo nuk \u00ebsht\u00eb thjesht dns, n\u00eb t\u00eb cilin mund t\u00eb regjistrojm\u00eb nj\u00eb rekord dhe t\u00eb gjitha \u2014 \u00ebsht\u00eb shum\u00eb m\u00eb fleksib\u00ebl dhe e p\u00ebrshtatshme. N\u00ebp\u00ebrmjet saj mund t\u00eb nd\u00ebrtojm\u00eb sh\u00ebrbime t\u00eb shp\u00ebrndara gjeo me gjeolokacione, kur me ndihm\u00ebn e saj p\u00ebrcaktoni nga erdhi klienti, dhe i jepni atij regjistrat p\u00ebrkat\u00ebs \u2014 me ndihm\u00ebn e saj mund t\u00eb nd\u00ebrtoni arkitektura failover. Kontrollimet e sh\u00ebndetit gjithashtu mund t\u00eb konfigurohen n\u00eb Route 53, ju caktoni endpointet q\u00eb monitorohen, caktoni metrike, p\u00ebrcaktoni se me cilat protokolle t\u00eb p\u00ebrcaktoni \"aktivitetin\" e sh\u00ebrbimit \u2014 tcp, http, https; caktoni periodicitetin e kontrollimeve q\u00eb p\u00ebrcaktojn\u00eb n\u00ebse sh\u00ebrbimi \u00ebsht\u00eb aktiv apo jo. Dhe n\u00eb dns vet\u00eb p\u00ebrcaktoni cila do t\u00eb jet\u00eb primary, cila do t\u00eb jet\u00eb secondary, ku do t\u00eb kaloni, n\u00ebse kontrolli i sh\u00ebndetit n\u00eb brend\u00ebsi t\u00eb route 53 ndodh. T\u00eb gjith\u00eb k\u00ebto mund t\u00eb b\u00ebhen me mund\u00ebsi t\u00eb tjera veglash, por ajo \u00e7far\u00eb \u00ebsht\u00eb e p\u00ebrshtatshme \u2014 nj\u00eb her\u00eb e konfigurove dhe pastaj nuk mendojm\u00eb fare p\u00ebr si b\u00ebhen kontrollimet, si b\u00ebhet kalimi: gjith\u00e7ka funksionon vet\u00eb.<\/p>\n

E para, por \u00e7far\u00eb duhet t\u00eb rezervojm\u00eb v\u00ebrtet route 53? E kush e di, ndoshta ndodh ndonj\u00eb gj\u00eb me t\u00eb? Fatmir\u00ebsisht, ne kurr\u00eb nuk kemi p\u00ebrjetuar k\u00ebt\u00eb, por p\u00ebrs\u00ebri, do t\u00eb ndaj nj\u00eb tregim se pse menduam se duhet ta rezervonim. K\u00ebtu po e mbrojm\u00eb veten paraprakisht. Disa her\u00eb n\u00eb dit\u00eb, b\u00ebjm\u00eb nj\u00eb eksport t\u00eb plot\u00eb t\u00eb t\u00eb gjitha zonave q\u00eb kemi regjistruar n\u00eb route 53. API i Amazon na lejon t'i sh\u00ebrbejm\u00eb ato n\u00eb JSON pa ndonj\u00eb problem, dhe kemi ngritur disa server\u00eb rezerv\u00eb ku e konvertojm\u00eb k\u00ebt\u00eb, e eksportojm\u00eb si konfiguracione dhe kemi, n\u00eb thelb, nj\u00eb konfigurim rezerv\u00eb. N\u00eb rast se ndodh ndonj\u00eb gj\u00eb, mund ta rind\u00ebrtojm\u00eb shpejt manualisht, pa humbur t\u00eb dh\u00ebnat e konfigurimeve DNS.<\/b>: si si dhe me \u00e7far\u00eb t\u00eb rezervojm\u00eb vet\u00eb route 53? Mos e di, ndonj\u00ebher\u00eb ndodh ndonj\u00eb gj\u00eb? Fatmir\u00ebsisht, ne nuk kemi hasur ndonj\u00ebher\u00eb n\u00eb k\u00ebto probleme, por p\u00ebrs\u00ebri, kam p\u00ebr t\u00eb treguar se pse menduam se duhet t\u00eb rezervojm\u00eb. K\u00ebtu e vendosim nj\u00eb mbrojtje t\u00eb parakohshme. Disa her\u00eb n\u00eb dit\u00eb ne b\u00ebjm\u00eb nj\u00eb eksport t\u00eb plot\u00eb t\u00eb t\u00eb gjitha zonave q\u00eb kemi t\u00eb regjistruara n\u00eb route 53. API i Amazon-it lejon q\u00eb ato t\u00eb ruhen leht\u00ebsisht n\u00eb JSON, dhe kemi ngritur disa server\u00eb rezerv\u00eb, ku e konvertojm\u00eb, e eksportojm\u00eb si konfigurations dhe kemi, thjesht, nj\u00eb konfigurim rezerv\u00eb. N\u00eb rast ndonj\u00eb problemi, mund ta nisim at\u00eb manualisht shpejt, pa humbur t\u00eb dh\u00ebnat e konfigurimeve DNS.<\/p>\n

Por e dyta<\/b>: \u00e7far\u00eb nuk \u00ebsht\u00eb e rezervuar ende n\u00eb k\u00ebt\u00eb imazh? Balancuesi i vet! Ne kemi b\u00ebr\u00eb ndarjen e klient\u00ebve sipas rajoneve shum\u00eb t\u00eb thjesht\u00eb. Ne kemi domenet bitrix24.ru, bitrix24.com, .de \u2014 tani kemi rreth 13 t\u00eb ndryshme, t\u00eb cilat punojn\u00eb n\u00eb zona t\u00eb ndryshme. Arrit\u00ebm n\u00eb p\u00ebrfundimin se n\u00eb \u00e7do rajon duhet t\u00eb kemi balancues t\u00eb vet\u00eb. K\u00ebshtu \u00ebsht\u00eb m\u00eb e leht\u00eb t\u00eb ndahet sipas rajoneve, n\u00eb var\u00ebsi t\u00eb ngarkes\u00ebs maksimale n\u00eb rrjet. N\u00ebse ka nj\u00eb d\u00ebshtim n\u00eb nivelin e ndonj\u00eb balancuesi, ai thjesht nxirret nga p\u00ebrdorimi dhe hiqet nga DNS. N\u00ebse ndodh ndonj\u00eb problem me grupin e balancuesve, ata rezervohen n\u00eb platforma t\u00eb tjera, dhe kalimi midis tyre b\u00ebhet me an\u00eb t\u00eb route53, sepse me nj\u00eb TTL t\u00eb shkurt\u00ebr kalimi ndodh maksimumi brenda 2, 3, 5 minutash. <\/p>\n

Treta \"po\"<\/b>: \u00e7far\u00eb tjet\u00ebr nuk \u00ebsht\u00eb rezervuar? S3, e sakt\u00eb. Ne, duke ruajtur skedar\u00ebt q\u00eb kemi tek p\u00ebrdoruesit n\u00eb s3, besonim sinqerisht se ishte i papreksh\u00ebm dhe nuk duhej t\u00eb reservonim asgj\u00eb aty. Por historia tregon se ndodhin gj\u00ebra t\u00eb tjera. N\u00eb fakt, Amazon e p\u00ebrshkruan S3 si nj\u00eb sh\u00ebrbim themelor, sepse vet\u00eb Amazon e p\u00ebrdor S3 p\u00ebr t\u00eb ruajtur imazhe makinerish, konfigurimesh, imazhe AMI, snapshot-e\u2026 Dhe n\u00ebse bie s3, si ndodhi nj\u00eb her\u00eb gjat\u00eb k\u00ebtyre 7 viteve q\u00eb po p\u00ebrdorim bitrix24, ai rr\u00ebmben pas tij shum\u00eb t\u00eb tjera \u2014 pap\u00ebrshkrueshm\u00ebri n\u00eb nisjen e virtual\u00ebve, d\u00ebshtim n\u00eb funksionimin e api-ve dhe k\u00ebshtu me radh\u00eb. <\/p>\n

Edhe S3 mund t\u00eb d\u00ebshtoj\u00eb \u2014 k\u00ebshtu ndodhi nj\u00eb her\u00eb. Prandaj arrit\u00ebm n\u00eb skem\u00ebn e m\u00ebposhtme: disa vite m\u00eb par\u00eb nuk kishte depozita objektive publike serioze n\u00eb Rusi, dhe ne po shqyrtonim mund\u00ebsin\u00eb p\u00ebr t\u00eb b\u00ebr\u00eb di\u00e7ka ton\u00ebn\u2026 P\u00ebr fat, ne nuk e filluam k\u00ebt\u00eb, sepse do t\u00eb kishim mbetur t\u00eb humbur n\u00eb at\u00eb ekspertiz\u00eb q\u00eb ne nuk e kemi, dhe ndoshta do t\u00eb kishim b\u00ebr\u00eb gabime. Tani depozitat e p\u00ebrputhshme me s3 jan\u00eb nga Mail.ru, nga Yandex, dhe nga disa ofrues t\u00eb tjer\u00eb. N\u00eb fund erdh\u00ebm n\u00eb p\u00ebrfundimin se duam t\u00eb kemi, s\u00eb pari, rezervim, dhe s\u00eb dyti, mund\u00ebsin\u00eb p\u00ebr t\u00eb punuar me kopje lokale. P\u00ebr rajonin konkret rus ne p\u00ebrdorim sh\u00ebrbimin Mail.ru Hotbox, i cili \u00ebsht\u00eb i p\u00ebrputhsh\u00ebm me api-n\u00eb s3. Nuk na nevojiteshin ndonj\u00eb p\u00ebrmir\u00ebsim serioz n\u00eb kodin brenda aplikacionit, dhe ne krijuam mekanizmin e m\u00ebposht\u00ebm: n\u00eb s3 ka trigger-a q\u00eb veprojn\u00eb n\u00eb krijimin dhe fshirjen e objekteve, dhe Amazon ka nj\u00eb sh\u00ebrbim t\u00eb till\u00eb si Lambda \u2014 kjo \u00ebsht\u00eb nj\u00eb sh\u00ebrbim serverless p\u00ebr ekzekutimin e kodit, i cili do t\u00eb realizohet pik\u00ebrisht kur aktivizohen k\u00ebto trigger-a.<\/p>\n

\"\u00abBitrix24\u00bb:
\n
\nKemi b\u00ebr\u00eb shum\u00eb thjesht\u00eb: n\u00ebse aktivizohet nj\u00eb trigger, ne ekzekutojm\u00eb kodin q\u00eb kopjon objektin n\u00eb ngjarjen Mail.ru. P\u00ebr t\u00eb filluar plot\u00ebsisht pun\u00ebn me kopjet lokale t\u00eb t\u00eb dh\u00ebnave, na nevojitet edhe nj\u00eb sinkronizim i kund\u00ebrt, n\u00eb m\u00ebnyr\u00eb q\u00eb klient\u00ebt q\u00eb jan\u00eb n\u00eb segmentin rus t\u00eb mund t\u00eb punojn\u00eb me nj\u00eb arkiv q\u00eb \u00ebsht\u00eb m\u00eb af\u00ebr tyre. Mail \u00ebsht\u00eb gati t\u00eb p\u00ebrfundoj\u00eb triggerat n\u00eb arkiv \u2014 do t\u00eb jet\u00eb e mundur tashm\u00eb n\u00eb nivelin e infrastruktur\u00ebs t\u00eb ekzekutojm\u00eb sinkronizimin e kund\u00ebrt, p\u00ebr momentin ne e b\u00ebjm\u00eb k\u00ebt\u00eb n\u00eb nivelin e kodit ton\u00eb. N\u00ebse shohim q\u00eb klienti ka vendosur nj\u00eb skedar, ne vendosim nj\u00eb ngjarje n\u00eb radh\u00eb n\u00eb kodin ton\u00eb, e p\u00ebrpunojm\u00eb at\u00eb dhe b\u00ebjm\u00eb replikimin e kund\u00ebrt. \u00c7far\u00eb \u00ebsht\u00eb e keqe n\u00eb k\u00ebt\u00eb: n\u00ebse ndodh ndonj\u00eb pun\u00eb me objektet tona jasht\u00eb produktit ton\u00eb, pra me mjete t\u00eb jashtme, ne nuk do ta kemi parasysh. Prandaj presim deri sa t\u00eb mbarojn\u00eb triggerat n\u00eb nivelin e arkivave, n\u00eb m\u00ebnyr\u00eb q\u00eb, pavar\u00ebsisht se nga ku ekzekutojm\u00eb kodin, objekti q\u00eb erdhi te ne t\u00eb kopjohet n\u00eb an\u00ebn tjet\u00ebr. <\/p>\n

N\u00eb nivelin e kodit, ne regjistrojm\u00eb dy ruajtje p\u00ebr \u00e7do klient: nj\u00eb q\u00eb konsiderohet si kryesore dhe tjetra si backup. N\u00ebse gjith\u00e7ka shkon mir\u00eb, punojm\u00eb me ruajtjen q\u00eb \u00ebsht\u00eb m\u00eb pran\u00eb nesh: klient\u00ebt tan\u00eb q\u00eb jan\u00eb n\u00eb Amazon punojn\u00eb me S3, nd\u00ebrsa ata q\u00eb operojn\u00eb n\u00eb Rusi punojn\u00eb me Hotbox. N\u00ebse ndonj\u00ebher\u00eb aktivizohet nj\u00eb sinjal, ne duhet t\u00eb aktivizojm\u00eb failover dhe t\u00eb kalojm\u00eb klient\u00ebt n\u00eb nj\u00eb ruajtje tjet\u00ebr. Ne mund ta aktivizojm\u00eb k\u00ebt\u00eb sinjal pavar\u00ebsisht nga rajonet dhe t'i kalojm\u00eb disa her\u00eb. N\u00eb praktik\u00eb nuk e kemi p\u00ebrdorur ende, por e kemi parashikuar k\u00ebt\u00eb mekaniz\u00ebm dhe mendojm\u00eb se ndonj\u00ebher\u00eb do na nevojitet kalimi. Nj\u00eb her\u00eb ka ndodhur tashm\u00eb. <\/p>\n

O, dhe Amazon ju iku...<\/h4>\n

\nKy prill \u2014 p\u00ebrvjetori i nisjes s\u00eb bllokimeve t\u00eb Telegramit n\u00eb Rusi. Prodhuesi m\u00eb i prekur nga kjo ishte Amazon. Dhe, fatkeq\u00ebsisht, kompanit\u00eb ruse q\u00eb punonin p\u00ebr t\u00eb gjith\u00eb bot\u00ebn e pat\u00ebn m\u00eb keq. <\/p>\n

N\u00ebse nj\u00eb kompani \u00ebsht\u00eb globale dhe Rusia \u00ebsht\u00eb nj\u00eb segment shum\u00eb i vog\u00ebl p\u00ebr t\u00eb, 3-5% \u2014 po, sidoqoft\u00eb, mund t\u00eb sakrifikohen. <\/p>\n

N\u00ebse kjo \u00ebsht\u00eb nj\u00eb kompani q\u00eb vepron ekskluzivisht n\u00eb Rusi, jam i sigurt se duhet t\u00eb vendoset lokal \u2013 do t\u00eb ishte thjesht m\u00eb e p\u00ebrshtatshme dhe m\u00eb e rehatshme p\u00ebr p\u00ebrdoruesit, dhe do t\u00eb ket\u00eb m\u00eb pak rreziqe. <\/p>\n

Por n\u00ebse kjo \u00ebsht\u00eb nj\u00eb kompani q\u00eb vepron globalisht dhe ka klient\u00eb t\u00eb barabart\u00eb nga Rusia dhe nga vende t\u00eb tjera? R\u00ebnd\u00ebsia e lidhshm\u00ebris\u00eb midis segmenteve \u00ebsht\u00eb e madhe, dhe ata duhet t\u00eb punojn\u00eb s\u00eb bashku n\u00eb nj\u00eb far\u00eb m\u00ebnyre. <\/p>\n

N\u00eb fund t\u00eb marsit 2018, Roskomnadzor d\u00ebrgoi nj\u00eb let\u00ebr operator\u00ebve m\u00eb t\u00eb m\u00ebdhenj, duke informuar se planifikonin t\u00eb bllokonin disa miliona IP nga Amazon p\u00ebr t\u00eb bllokuar\u2026 aplikacionin e mesazheve Zello. Fal\u00eb k\u00ebtyre ofruesve, ata e shp\u00ebrndan\u00eb letr\u00ebn me sukses, dhe u kuptua se lidhshm\u00ebria me Amazon mund t\u00eb prishej. Ishte nj\u00eb t\u00eb premte; ne vrapuam n\u00eb panik tek koleg\u00ebt tan\u00eb nga servers.ru, me fjal\u00ebt: \u00abShok\u00eb, na nevojiten disa server\u00eb q\u00eb t\u00eb vendosen jasht\u00eb Rusis\u00eb, jo n\u00eb Amazon, por, p\u00ebr shembull, diku n\u00eb Amsterdam\u00bb, p\u00ebr t\u00eb pasur mund\u00ebsi ashtu si t\u00eb pakuptuar t\u00eb vendosnim atje t\u00eb pakt\u00ebn di\u00e7ka. vpn<\/a> dhe proxy p\u00ebr disa endpoint-e, t\u00eb cil\u00ebt nuk mund t\u00eb ndikojm\u00eb, p\u00ebr shembull endpoint-et e s3 \u2014 nuk mund t\u00eb p\u00ebrpiqemi t\u00eb ngritim nj\u00eb sh\u00ebrbim t\u00eb ri dhe t\u00eb marrim nj\u00eb IP tjet\u00ebr, ne duhet t\u00eb komunikojm\u00eb me ta. Brenda disa dit\u00ebve, ne i konfigurim k\u00ebta server\u00eb, i ngrit\u00ebm, dhe n\u00eb t\u00ebr\u00ebsi, p\u00ebrpara fillimit t\u00eb bllokimeve ishim p\u00ebrgatitur. E \u00e7uditshme, q\u00eb RKN, duke par\u00eb trazir\u00ebn dhe panikimin e ngritur, tha: \u00abJo, tani nuk do t\u00eb bllokojm\u00eb asgj\u00eb\u00bb. (Por kjo ishte pik\u00ebrisht deri n\u00eb momentin kur filluan t\u00eb bllokonin Telegramin.) Pasi e konfigur\u00ebm mund\u00ebsin\u00eb p\u00ebr t\u00eb kaluar dhe kuptuam q\u00eb bllokimi nuk u vendos, megjithat\u00eb, nuk e zhbllokuam at\u00eb q\u00eb kishim b\u00ebr\u00eb. Thjesht, p\u00ebr rast emergjence. <\/p>\n

\"\u00abBitrix24\u00bb:
\n
\nDhe ja, n\u00eb vitin 2019, ne jetojm\u00eb n\u00ebn kushtet e bllokimeve. D\u00ebgjova nat\u00ebn e kaluar: rreth nj\u00eb milion IP vazhdojn\u00eb t\u00eb bllokohen. N\u00eb t\u00eb v\u00ebrtet\u00eb, Amazon \u00ebsht\u00eb shumica e rikthyer, dhe arrit\u00ebm deri n\u00eb 20 milion adresash n\u00eb kulm... N\u00eb p\u00ebrgjith\u00ebsi, realiteti \u00ebsht\u00eb se lidhshm\u00ebria, lidhshm\u00ebria e mir\u00eb \u2014 ndonj\u00ebher\u00eb nuk mund t\u00eb ekzistoj\u00eb. Papritur. Mund t\u00eb mungoj\u00eb p\u00ebr arsye teknike \u2014 zjarre, ekskavator\u00eb, dhe t\u00eb tjera t\u00eb ngjashme. Ose, si\u00e7 pam\u00eb, jo gjithmon\u00eb p\u00ebr arsye teknike. Prandaj dikush i madh dhe i r\u00ebnd\u00ebsish\u00ebm, me AS-t\u00eb e tij, ndoshta mund ta menaxhoj\u00eb k\u00ebt\u00eb me rrug\u00eb t\u00eb tjera, \u2014 direkt lidhje dhe gj\u00ebra t\u00eb tjera n\u00eb nivelin l2. Por n\u00eb nj\u00eb version t\u00eb thjesht\u00eb, si ne ose m\u00eb t\u00eb vegjlit, \u00ebsht\u00eb mir\u00eb t\u00eb keni nj\u00eb rezervim n\u00eb nivel serverash, t\u00eb ngritur diku tjet\u00ebr, me VPN, proxy t\u00eb konfigurura paraprakisht, me mund\u00ebsin\u00eb p\u00ebr t\u00eb nd\u00ebrruar shpejt konfigurimin n\u00eb ato segmente q\u00eb jan\u00eb kritike p\u00ebr ju n\u00eb lidhshm\u00ebri. Kjo na ka ndihmuar shum\u00eb her\u00eb, kur filluan bllokimet e Amazon, ne kalonim trafikun e S3 n\u00eb rastin m\u00eb t\u00eb keq, por gradualisht gjith\u00e7ka u rregullua.<\/p>\n

Si t\u00eb rezervosh... nj\u00eb t\u00ebr\u00ebsi ofruesi?<\/h4>\n

\nAktualisht nuk kemi nj\u00eb skenar p\u00ebr rastet e d\u00ebshtimit t\u00eb plot\u00eb t\u00eb Amazon. Por, kemi nj\u00eb skenar t\u00eb ngjash\u00ebm p\u00ebr Rusin\u00eb. N\u00eb Rusi, ne ishim t\u00eb akomoduar n\u00eb nj\u00eb ofrues, nga i cili zgjodh\u00ebm t\u00eb kishim disa platforma. Para nj\u00eb viti p\u00ebrball\u00ebm nj\u00eb problem: pavar\u00ebsisht se ishin dy qendra t\u00eb t\u00eb dh\u00ebnash, n\u00eb nivelin e konfigurimit t\u00eb rrjetit t\u00eb ofruesit mund t\u00eb ishin problemet q\u00eb ndikonin edhe t\u00eb dy qendrat. K\u00ebshtu, mund t\u00eb p\u00ebrjetonim munges\u00eb aksesit n\u00eb t\u00eb dy platforma. Natyrisht, k\u00ebshtu ndodhi. N\u00eb fund, ne rishikuan arkitektur\u00ebn ton\u00eb t\u00eb brendshme. Ajo nuk u ndryshua shum\u00eb ndjesh\u00ebm, por p\u00ebr Rusin\u00eb tani kemi dy platforma, t\u00eb cilat nuk jan\u00eb n\u00eb nj\u00eb ofrues, por n\u00eb dy t\u00eb ndrysh\u00ebm. N\u00ebse nj\u00ebra shkat\u00ebrrohet, ne mund t\u00eb kalojm\u00eb te tjetra.<\/p>\n

Hipotetikisht, p\u00ebr Amazon po shqyrtojm\u00eb mund\u00ebsin\u00eb e rezervimit n\u00eb nivelin e nj\u00eb ofruesi tjet\u00ebr; ndoshta Google, ndoshta dikush tjet\u00ebr... Por deri tani kemi v\u00ebzhguar n\u00eb praktik\u00eb se n\u00ebse ndodhin aksidente n\u00eb nj\u00eb zon\u00eb t\u00eb caktuar t\u00eb disponueshm\u00ebris\u00eb n\u00eb Amazon, aksidentet n\u00eb nivelin e t\u00eb gjith\u00eb rajonit jan\u00eb t\u00eb mjaft t\u00eb rralla. Prandaj, teoriisht, kemi nj\u00eb ide se ndoshta do t\u00eb b\u00ebjm\u00eb rezervimet \"Amazon - jo Amazon\", por n\u00eb praktik\u00eb, kjo ende nuk ka ndodhur. <\/p>\n

Nj\u00eb fjal\u00eb p\u00ebr automatizimin<\/h4>\n

\nA ka nevoj\u00eb gjithmon\u00eb p\u00ebr automatizim? K\u00ebtu \u00ebsht\u00eb e p\u00ebrshtatshme t\u00eb kujtojm\u00eb efektin Dunning-Kruger. N\u00eb boshtin \"x\" jan\u00eb njohurit\u00eb dhe p\u00ebrvoja q\u00eb ne fitojm\u00eb, nd\u00ebrsa n\u00eb boshtin \"y\" \u00ebsht\u00eb besimi n\u00eb veprimet tona. Fillimisht nuk dim\u00eb asgj\u00eb dhe nuk jemi aspak t\u00eb sigurt. Pastaj dim\u00eb pak dhe b\u00ebhemi mega t\u00eb sigurt - ky \u00ebsht\u00eb \"pika e marr\u00ebzis\u00eb\", e cila ilustrohet mir\u00eb n\u00eb imazhin \"n\u00ebse nuk je i men\u00e7ur, ke guxim\". Pastaj ne kemi m\u00ebsuar pak dhe jemi gati t\u00eb shkojm\u00eb n\u00eb luft\u00eb. M\u00eb pas shkelim mbi disa gafa t\u00eb r\u00ebnda, bien n\u00eb lugin\u00ebn e d\u00ebshp\u00ebrimit, kur duket se dim\u00eb di\u00e7ka, por n\u00eb t\u00eb v\u00ebrtet\u00eb nuk dim\u00eb shum\u00eb. Pastaj, me kalimin e koh\u00ebs, b\u00ebhemi m\u00eb t\u00eb sigurt.<\/p>\n

\"\u00abBitrix24\u00bb:
\n
\nLogjika jon\u00eb p\u00ebr nd\u00ebrrimet e ndryshme automatikisht p\u00ebr aksidente t\u00eb caktuara \u00ebsht\u00eb shum\u00eb mir\u00eb e p\u00ebrshkruar nga ky grafik. Ne e filluam - nuk dinim asgj\u00eb, pothuajse t\u00eb gjitha pun\u00ebt b\u00ebheshin manualisht. M\u00eb pas kuptuam se mund t\u00eb vendosnim automatik p\u00ebr gjith\u00e7ka dhe t\u00eb flinim qet\u00eb. Papritmas, humbasim kontrollin dhe ndodhim n\u00eb nj\u00eb situat\u00eb problematike: ndodhin false positive dhe ne p\u00ebr\u00e7ojm\u00eb trafikun p\u00ebr andej k\u00ebndej, kur, n\u00eb fakt, nuk duhej ta b\u00ebnim k\u00ebt\u00eb. Kjo do t\u00eb thot\u00eb se ndodhin prishje t\u00eb replikimit ose ndonj\u00eb gj\u00eb tjet\u00ebr - kjo \u00ebsht\u00eb ajo lugin\u00eb e d\u00ebshp\u00ebrimit. Pastaj arrijm\u00eb n\u00eb kuptimin se \u00e7do gj\u00eb duhet ta shohim me mend. K\u00ebshtu q\u00eb ka kuptim t\u00eb mb\u00ebshtetemi n\u00eb automatik\u00eb, duke parashikuar mund\u00ebsin\u00eb e aktivizimit t\u00eb gabuar. Por! n\u00ebse pasojat mund t\u00eb jen\u00eb shkat\u00ebrruese, \u00ebsht\u00eb m\u00eb mir\u00eb ta l\u00ebm\u00eb k\u00ebt\u00eb n\u00eb duar t\u00eb ekipit n\u00eb turn, inxhinier\u00ebve t\u00eb zyr\u00ebs, t\u00eb cil\u00ebt do t\u00eb sigurohen dhe do t\u00eb kontrollojn\u00eb n\u00ebse \u00ebsht\u00eb v\u00ebrtet nj\u00eb emergjenc\u00eb dhe do t\u00eb realizojn\u00eb veprimet e nevojshme manualisht...<\/p>\n

P\u00ebrfundimi<\/h4>\n

\nN\u00eb 7 vjet, kemi kaluar nga panika totale kur ndodhte ndonj\u00eb r\u00ebnie, n\u00eb kuptimin se nuk ka probleme, por vet\u00ebm detyra q\u00eb duhet dhe mund t\u00eb zgjidhen. Kur ndiheni duke nd\u00ebrtuar nj\u00eb sh\u00ebrbim, shikoni at\u00eb nga lart, vler\u00ebsoni t\u00eb gjitha rreziqet q\u00eb mund t\u00eb ndodhin. N\u00ebse i shihni menj\u00ebher\u00eb, parashikoni rezervimin dhe mund\u00ebsin\u00eb p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb infrastruktur\u00eb q\u00eb nuk d\u00ebshtoon, sepse \u00e7do pik\u00eb q\u00eb mund t\u00eb d\u00ebshtoj\u00eb dhe t\u00eb \u00e7oj\u00eb n\u00eb mosfunksionimin e sh\u00ebrbimit, do ta b\u00ebj\u00eb patjet\u00ebr. Dhe edhe n\u00ebse mendoni se disa element\u00eb t\u00eb infrastruktur\u00ebs, si p.sh. s3, nuk do t\u00eb d\u00ebshtojn\u00eb, duhet t\u00eb keni parasysh se ata gjithashtu mund t\u00eb ndodhin. T\u00eb pakt\u00ebn teorikisht, duhet t\u00eb keni nj\u00eb ide se \u00e7far\u00eb do t\u00eb b\u00ebni me ta n\u00ebse ndodh di\u00e7ka. Keni nj\u00eb plan p\u00ebr menaxhimin e rreziqeve. Kur mendoni t\u00eb b\u00ebni gjith\u00e7ka me automatizim ose manualisht, vler\u00ebsoni rreziqet: \u00e7far\u00eb do ndodhe n\u00ebse automatizimi fillon t\u00eb ndryshoj\u00eb gjith\u00e7ka \u2014 a do t\u00eb \u00e7oj\u00eb kjo n\u00eb nj\u00eb sken\u00eb p\u00ebr keq n\u00eb krahasim me nj\u00eb katastrof\u00eb? Ndoshta, diku \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrdoret nj\u00eb kompromis i arsyesh\u00ebm mes p\u00ebrdorimit t\u00eb automatizimit dhe reagimit t\u00eb inxhinierit n\u00eb detyr\u00eb, i cili do t\u00eb vler\u00ebsoj\u00eb situat\u00ebn reale dhe do t\u00eb kuptoj\u00eb n\u00ebse \u00ebsht\u00eb e nevojshme t\u00eb ndryshohet menj\u00ebher\u00eb apo \"po, por jo tani\".<\/p>\n

Nj\u00eb kompromis i arsyesh\u00ebm midis p\u00ebrsosm\u00ebris\u00eb dhe kapacitetit real, koh\u00ebs, parave q\u00eb mund t\u00eb shpenzoni p\u00ebr skem\u00ebn q\u00eb do t\u00eb keni n\u00eb fund.<\/p>\n

Ky tekst \u00ebsht\u00eb nj\u00eb version i zgjeruar dhe i pasuruar i raportit t\u00eb Aleksand\u00ebr Demidov n\u00eb konferenc\u00eb. Uptime dita 4<\/a><\/noindex>.<\/i>
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041d\u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0434\u0435\u043d\u044c \u0443 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb \u043d\u0435\u0442 \u0441\u043e\u0442\u0435\u043d \u0433\u0438\u0433\u0430\u0431\u0438\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430, \u043d\u0435\u0442 \u043e\u0433\u0440\u043e\u043c\u043d\u043e\u0433\u043e \u043f\u0430\u0440\u043a\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 (\u0445\u043e\u0442\u044f \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445, \u043a\u043e\u043d\u0435\u0447\u043d\u043e, \u043d\u0435\u043c\u0430\u043b\u043e). \u041d\u043e \u0434\u043b\u044f \u043c\u043d\u043e\u0433\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u043e\u043d \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u043e\u043c \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u044d\u0442\u043e \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 business-critical \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u043f\u0430\u0434\u0430\u0442\u044c \u2014 \u043d\u0443, \u043d\u0438\u043a\u0430\u043a \u043d\u0435\u043b\u044c\u0437\u044f. \u0410 \u0447\u0442\u043e \u0435\u0441\u043b\u0438 \u043f\u0430\u0434\u0435\u043d\u0438\u0435 \u0432\u0441\u0435-\u0442\u0430\u043a\u0438 \u0441\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u043d\u043e \u00ab\u0432\u043e\u0441\u0441\u0442\u0430\u043b\u00bb \u0441\u0435\u0440\u0432\u0438\u0441 \u0442\u0430\u043a \u0431\u044b\u0441\u0442\u0440\u043e, \u0447\u0442\u043e \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26389,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47\u2018Bitrix24\u2019: \u2018Nj\u00eb sh\u00ebrbim i ngrihir shpejt nuk konsiderohet i r\u00ebn\u00eb\u2019 | ProHoster","description":"Aktualisht, sh\u00ebrbimi \u2018Bitrix24\u2019 nuk ka qindra gigabite trafik, nuk ka nj\u00eb park t\u00eb madh serverash (ndo\u00ebse ka disa). Por p\u00ebr shum\u00eb klient\u00eb, \u00ebsht\u00eb mjeti kryesor i pun\u00ebs n\u00eb kompani, nj\u00eb aplikacion me r\u00ebnd\u00ebsi t\u00eb madhe biznesi. Prandaj, ai nuk duhet t\u00eb bjer\u00eb \u2014 asnj\u00ebher\u00eb. Por \u00e7far\u00eb n\u00ebse ndodh q\u00eb ka r\u00ebn\u00eb, por sh\u00ebrbimi u \u2018ringjall\u2019 kaq shpejt sa askush nuk e vuri re dhe...","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","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\udd47\u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb: \u00ab\u0411\u044b\u0441\u0442\u0440\u043e \u043f\u043e\u0434\u043d\u044f\u0442\u043e\u0435 \u043d\u0435 \u0441\u0447\u0438\u0442\u0430\u0435\u0442\u0441\u044f \u0443\u043f\u0430\u0432\u0448\u0438\u043c\u00bb | ProHoster","og:description":"\u041d\u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0434\u0435\u043d\u044c \u0443 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb \u043d\u0435\u0442 \u0441\u043e\u0442\u0435\u043d \u0433\u0438\u0433\u0430\u0431\u0438\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430, \u043d\u0435\u0442 \u043e\u0433\u0440\u043e\u043c\u043d\u043e\u0433\u043e \u043f\u0430\u0440\u043a\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 (\u0445\u043e\u0442\u044f \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445, \u043a\u043e\u043d\u0435\u0447\u043d\u043e, \u043d\u0435\u043c\u0430\u043b\u043e). \u041d\u043e \u0434\u043b\u044f \u043c\u043d\u043e\u0433\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u043e\u043d \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u043e\u043c \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u044d\u0442\u043e \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 business-critical \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u043f\u0430\u0434\u0430\u0442\u044c \u2014 \u043d\u0443, \u043d\u0438\u043a\u0430\u043a \u043d\u0435\u043b\u044c\u0437\u044f. \u0410 \u0447\u0442\u043e \u0435\u0441\u043b\u0438 \u043f\u0430\u0434\u0435\u043d\u0438\u0435 \u0432\u0441\u0435-\u0442\u0430\u043a\u0438 \u0441\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u043d\u043e \u00ab\u0432\u043e\u0441\u0441\u0442\u0430\u043b\u00bb \u0441\u0435\u0440\u0432\u0438\u0441 \u0442\u0430\u043a \u0431\u044b\u0441\u0442\u0440\u043e, \u0447\u0442\u043e \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u0438","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","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:02:18+00:00","article:modified_time":"2019-10-31T19:02:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35092","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-04 14:51:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:10:27","updated":"2026-02-04 14:51: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\/35092","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=35092"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35092\/revisions"}],"predecessor-version":[{"id":156668,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35092\/revisions\/156668"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26389"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}