{"id":39219,"date":"2019-10-31T22:28:31","date_gmt":"2019-10-31T19:28:31","guid":{"rendered":"https:\/\/prohoster.info\/blog\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire\/"},"modified":"2019-10-31T22:28:31","modified_gmt":"2019-10-31T19:28:31","slug":"devops-i-haos-dostavka-po-v-detsentralizovannom-mire","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire","title":{"rendered":"DevOps dhe Kaosi: shp\u00ebrndarja e softuerit n\u00eb bot\u00ebn e decentralizuar","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I sapun dhe drejtor i \u00abOtomato Software\u00bb, nj\u00eb nga iniciator\u00ebt dhe instruktoret e par\u00eb t\u00eb \u00e7ertifikimit DevOps n\u00eb Izrael, Anton Weiss, foli vitin e kaluar DevOpsDays Moscow<\/a><\/noindex> p\u00ebr teorin\u00eb e kaosit dhe parimet kryesore t\u00eb inxhinieris\u00eb s\u00eb kaosit, si dhe shpjegoi si \u00ebsht\u00eb organizata ideale DevOps e t\u00eb ardhmes.<\/p>\n

Kemi p\u00ebrgatitur nj\u00eb version tekstual t\u00eb referatit. <\/p>\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\n<\/a><\/noindex>
\nMir\u00ebm\u00ebngjes! <\/p>\n

DevOpsDays n\u00eb Mosk\u00eb po organizohet p\u00ebr her\u00eb t\u00eb dyt\u00eb, un\u00eb jam p\u00ebr her\u00eb t\u00eb dyt\u00eb n\u00eb k\u00ebt\u00eb sken\u00eb, shum\u00eb nga ju jan\u00eb p\u00ebr her\u00eb t\u00eb dyt\u00eb n\u00eb k\u00ebt\u00eb sall\u00eb. \u00c7far\u00eb do t\u00eb thot\u00eb kjo? Do t\u00eb thot\u00eb se l\u00ebvizja DevOps n\u00eb Rusi po rritet dhe p\u00ebrhapet, dhe m\u00eb e r\u00ebnd\u00ebsishmja, kjo do t\u00eb thot\u00eb se ka ardhur koha t\u00eb flasim p\u00ebr at\u00eb se \u00e7far\u00eb do t\u00eb thot\u00eb DevOps n\u00eb vitin 2018. <\/p>\n

T\u00eb ngrini dor\u00ebn ata q\u00eb mendojn\u00eb se n\u00eb vitin 2018, DevOps \u00ebsht\u00eb tashm\u00eb nj\u00eb profesion? Ka t\u00eb till\u00eb. A ka n\u00eb sall\u00eb inxhinier\u00eb DevOps, t\u00eb cil\u00ebt n\u00eb p\u00ebrshkrimin e pun\u00ebs kan\u00eb shkruar \u00abinxhinier DevOps\u00bb? A ka n\u00eb sall\u00eb menaxher\u00eb DevOps? Asnj\u00eb. Arkitekt\u00eb DevOps? Po ashtu. Paksa e pakt\u00eb. A t\u00eb v\u00ebrtet\u00eb askush nuk ka shkruar se \u00ebsht\u00eb inxhinier DevOps?<\/p>\n

Pra, shumica prej jush mendojn\u00eb se kjo \u00ebsht\u00eb nj\u00eb antipattern? Se nj\u00eb profesion i till\u00eb nuk duhet t\u00eb ekzistoj\u00eb? Ne mund t\u00eb mendojm\u00eb gjith\u00e7ka q\u00eb duam, por nd\u00ebrkoh\u00eb industria po ec\u00ebn p\u00ebrpara n\u00ebn tingujt e tub\u00ebs DevOps.<\/p>\n

Kush ka d\u00ebgjuar p\u00ebr tem\u00ebn e re, q\u00eb quhet DevDevOps? Kjo \u00ebsht\u00eb nj\u00eb metodologji e re q\u00eb ndihmon n\u00eb sigurimin e bashk\u00ebpunimit efektiv midis zhvilluesve dhe DevOps-\u00ebve. Dhe nuk \u00ebsht\u00eb kaq e re. N\u00ebse gjykojm\u00eb sipas Twitter-it, 4 vjet m\u00eb par\u00eb ka filluar t\u00eb flitet p\u00ebr t\u00eb. Dhe deri tani, interesi p\u00ebr t\u00eb po rritet, dometh\u00ebn\u00eb ka nj\u00eb problem. Problemi duhet zgjidhur.<\/p>\n

\"DevOps
\n
\nNe jemi njer\u00ebz kreativ\u00eb, nuk ngushtohemi aq leht\u00eb. Them\u00eb: DevOps nuk \u00ebsht\u00eb nj\u00eb fjal\u00eb mjaft e plot\u00eb, i mungojn\u00eb shum\u00eb elemente interesante. Dhe ne shkojm\u00eb n\u00eb laborator\u00ebt tan\u00eb sekrete dhe fillojm\u00eb t\u00eb prodhojm\u00eb mutacione t\u00eb \u00e7uditshme: DevTestOps, GitOps, DevSecOps, BizDevOps, ProdOps.<\/p>\n

\"DevOps
\n
\nLogjika \u00ebsht\u00eb e fort\u00eb, apo jo? N\u00ebse sistemi yn\u00eb i d\u00ebrgimit nuk funksionon, sistemet tona jan\u00eb t\u00eb paq\u00ebndrueshme dhe p\u00ebrdoruesit jan\u00eb t\u00eb pak\u00ebnaqur, ne nuk arrijm\u00eb t\u00eb nxjerrim softuerin n\u00eb koh\u00ebn e duhur, nuk arrijm\u00eb t\u00eb p\u00ebrputhemi me buxhetin. Si do ta zgjidhim t\u00eb gjith\u00eb k\u00ebt\u00eb? Do t\u00eb shpikim nj\u00eb fjal\u00eb t\u00eb re! Ajo do t\u00eb p\u00ebrfundoj\u00eb me \u00abOps\u00bb, dhe problemi \u00ebsht\u00eb zgjidhur.<\/p>\n

K\u00ebshtu e quaj k\u00ebt\u00eb qasje \u2014 \u00abOps, dhe problemi \u00ebsht\u00eb zgjidhur\u00bb.<\/p>\n

T\u00eb gjitha k\u00ebto bien n\u00eb plan t\u00eb dyt\u00eb, n\u00ebse ne kujtojm\u00eb se p\u00ebrse e kemi shpikur k\u00ebt\u00eb. E kemi shpikur t\u00eb gjith\u00eb k\u00ebt\u00eb DevOps, p\u00ebr ta b\u00ebr\u00eb d\u00ebrgimin e softuerit dhe pun\u00ebn ton\u00eb n\u00eb k\u00ebt\u00eb proces sa m\u00eb t\u00eb pa penguar, pa dhimbje, efikase, dhe m\u00eb e r\u00ebnd\u00ebsishmja, k\u00ebnaq\u00ebse. <\/p>\n

DevOps ka lindur nga dhimbja. Dhe na ka ardhur n\u00eb maj\u00eb t\u00eb hund\u00ebs t\u00eb vuajm\u00eb. Dhe p\u00ebr t\u00eb ndodhur kjo, ne mb\u00ebshtetemi n\u00eb praktika t\u00eb p\u00ebrjetshme: bashk\u00ebpunim efektiv, praktika fluksi, dhe m\u00eb e r\u00ebnd\u00ebsishmja, mendimi sistemor, sepse pa t\u00eb asnj\u00eb DevOps nuk funksionon.<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb nj\u00eb sistem?<\/b><\/h3>\n

\nDhe n\u00ebse po flasim p\u00ebr mendimin sistemor, le t\u00eb kujtojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb sistem.<\/p>\n

\"DevOps
\n
\nN\u00ebse je nj\u00eb haker-revolucionar, p\u00ebr ty sistemi \u00ebsht\u00eb nj\u00eb e keqe e qart\u00eb. \u00cbsht\u00eb nj\u00eb re q\u00eb mbulon ty dhe t\u00eb detyron t\u00eb b\u00ebsh at\u00eb q\u00eb nuk d\u00ebshiron. <\/p>\n

\"DevOps
\n
\nNga perspektiva e mendimit sistemor, sistemi \u00ebsht\u00eb nj\u00eb nj\u00ebsi e caktuar q\u00eb p\u00ebrb\u00ebhet nga pjes\u00eb. N\u00eb k\u00ebt\u00eb kuptim, secili prej nesh \u00ebsht\u00eb nj\u00eb sistem. Organizatave n\u00eb t\u00eb cilat punojm\u00eb, jan\u00eb sisteme. Dhe ajo q\u00eb ne po nd\u00ebrtojm\u00eb, \u00ebsht\u00eb e quajtur nj\u00eb sistem.<\/p>\n

T\u00eb gjitha k\u00ebto jan\u00eb pjes\u00eb e nj\u00eb sistemi t\u00eb madh socio-teknologjik. Dhe vet\u00ebm n\u00ebse ne e kuptojm\u00eb se si funksionon ky sistem socio-teknologjik s\u00eb bashku, vet\u00ebm at\u00ebher\u00eb do t\u00eb mund t\u00eb optimizojm\u00eb v\u00ebrtet di\u00e7ka n\u00eb k\u00ebt\u00eb q\u00ebllim. <\/p>\n

Nga perspektiva e mendimit sistemor, sistemi ka disa pron\u00ebsi interesante. S\u00eb pari, ai p\u00ebrb\u00ebhet nga pjes\u00eb, \u00e7ka do t\u00eb thot\u00eb se sjellja e tij varet nga sjellja e pjes\u00ebve. Megjithat\u00eb, t\u00eb gjitha pjes\u00ebt e tij gjithashtu jan\u00eb t\u00eb varura nga nj\u00ebra-tjetra. K\u00ebshtu, sa m\u00eb shum\u00eb pjes\u00eb t\u00eb ket\u00eb nj\u00eb sistem, aq m\u00eb e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb kuptosh ose parashikosh sjelljen e tij. <\/p>\n

Nga perspektiva e sjelljes, k\u00ebtu ka nj\u00eb fakt t\u00eb tjer\u00eb interesant. Nj\u00eb sistem mund t\u00eb b\u00ebj\u00eb di\u00e7ka q\u00eb asnj\u00eb nga pjes\u00ebt e tij t\u00eb ndara nuk mund ta b\u00ebj\u00eb. <\/p>\n

Si\u00e7 tha doktori Russell Ackoff (nj\u00eb nga themeluesit e mendimit sistemor), ky \u00ebsht\u00eb nj\u00eb provim mjaft i leht\u00eb p\u00ebrmes nj\u00eb eksperimentimi mendor. P\u00ebr shembull, kush n\u00eb sall\u00eb di t\u00eb shkruaj\u00eb kod? Shum\u00eb duar, dhe kjo \u00ebsht\u00eb normale, sepse \u00ebsht\u00eb nj\u00eb nga k\u00ebrkesat kryesore t\u00eb profesionit ton\u00eb. Ju dini t\u00eb shkruani, por duart tuaja ndar\u00eb nga ju mund t\u00eb shkruajn\u00eb kod? Ka disa q\u00eb do t\u00eb thon\u00eb: \u00abDuart e mia nuk shkruajn\u00eb kod, mendja ime shkruan kod\u00bb. Dhe a mund mendja t\u00eb shkruaj\u00eb kod ndar\u00eb nga ju? Shqet\u00ebsisht, ndoshta jo. <\/p>\n

Truri \u2013 nj\u00eb makin\u00eb e mrekullueshme, ne nuk dim\u00eb as 10% se si funksionon aty, por ai nuk mund t\u00eb funksionoj\u00eb ve\u00e7mas nga sistemi q\u00eb \u00ebsht\u00eb organizmi yn\u00eb. Dhe kjo \u00ebsht\u00eb leht\u00ebsisht e provueshme: hapni kutin\u00eb tuaj t\u00eb kafk\u00ebs, nxirrni trurin nga aty, vendoseni p\u00ebrpara kompjuterit dhe lejoni t\u00eb provoj\u00eb t\u00eb shkruaj\u00eb di\u00e7ka t\u00eb thjesht\u00eb. \"Hello, world\" n\u00eb Python, p\u00ebr shembull.<\/p>\n

N\u00ebse nj\u00eb sistem mund t\u00eb b\u00ebj\u00eb di\u00e7ka q\u00eb asnj\u00eb nga pjes\u00ebt e tij nuk mund ta b\u00ebj\u00eb ve\u00e7mas, at\u00ebher\u00eb kjo do t\u00eb thot\u00eb se sjellja e tij nuk p\u00ebrcaktohet nga sjellja e pjes\u00ebve t\u00eb tij. Por \u00e7far\u00eb e p\u00ebrcakton at\u00eb? Ajo p\u00ebrcaktohet nga nd\u00ebrveprimi midis k\u00ebtyre pjes\u00ebve. Dhe p\u00ebr rrjedhoj\u00eb, sa m\u00eb shum\u00eb pjes\u00eb, aq m\u00eb t\u00eb komplikuara jan\u00eb nd\u00ebrveprimet, aq m\u00eb e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb kuptosh dhe parashikosh sjelljen e sistemit. Dhe kjo e b\u00ebn nj\u00eb sistem t\u00eb till\u00eb kaotic, sepse \u00e7do ndryshim i vog\u00ebl, i paduksh\u00ebm p\u00ebr syrin n\u00eb ndonj\u00eb nga pjes\u00ebt e sistemit, mund t\u00eb \u00e7oj\u00eb n\u00eb rezultate plot\u00ebsisht t\u00eb paparashikueshme. <\/p>\n

Kjo ndjeshm\u00ebri ndaj kushteve fillestare u zbulua dhe u studiua p\u00ebr her\u00eb t\u00eb par\u00eb nga meteorologu amerikan Ed Lorenz. M\u00eb pas ajo mori emrin \"efekti flutur\" dhe \u00e7oi n\u00eb zhvillimin e nj\u00eb l\u00ebvizjeje shkencore t\u00eb njohur si \"teoria e kaosit\". Kjo teori u b\u00eb nj\u00eb nga zhvendosjet kryesore t\u00eb paradigmatike n\u00eb shkenc\u00eb n\u00eb shekullin e 20-t\u00eb.<\/p>\n

Teoria e kaosit<\/b><\/h3>\n

\nNjer\u00ebzit q\u00eb merren me studimin e kaosit e quajn\u00eb veten kaosolog\u00eb.<\/p>\n

\"DevOps
\n
\nN\u00eb fakt, arsyeja e k\u00ebtij raporti \u00ebsht\u00eb se, duke punuar me sisteme t\u00eb shp\u00ebrndara komplekse dhe organizata t\u00eb m\u00ebdha nd\u00ebrkomb\u00ebtare, n\u00eb nj\u00eb moment t\u00eb caktuar kuptova se ky \u00ebsht\u00eb ai q\u00eb ndjej p\u00ebr veten time. Un\u00eb \u2013 jam kaosolog. Kjo \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb e zgjuar p\u00ebr t\u00eb th\u00ebn\u00eb: \"Nuk e kuptoj se \u00e7far\u00eb po ndodh k\u00ebtu dhe nuk e di \u00e7far\u00eb t\u00eb b\u00ebj me k\u00ebt\u00eb.\" <\/p>\n

Mendoj se shum\u00eb nga ju gjithashtu ndiheni shpesh k\u00ebshtu, k\u00ebshtu q\u00eb ju gjithashtu jeni kaosolog\u00eb. Ju ftoj n\u00eb guild\u00ebn e kaosolog\u00ebve. Sistemet q\u00eb ne, koleg\u00ebt e dashur kaosolog\u00eb, do t\u00eb studiojm\u00eb quhen \"sisteme adaptuese komplekse\". <\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb adaptiviteti? Adaptiviteti do t\u00eb thot\u00eb q\u00eb sjellja individuale dhe kolektive e pjes\u00ebve n\u00eb nj\u00eb sistem t\u00eb till\u00eb adaptues ndryshon dhe vet\u00eb-organizohet, duke u p\u00ebrgjigjur ndaj ngjarjeve ose zinxhirit t\u00eb mikro-ngjarjeve n\u00eb sistem. K\u00ebshtu, sistemi adaptohet ndaj ndryshimeve p\u00ebrmes vet\u00eb-organizimit. Dhe kjo aft\u00ebsi e vet\u00eb-organizimit bazohet n\u00eb bashk\u00ebpunimin e plot\u00eb, t\u00eb decentralizuar t\u00eb agjent\u00ebve autonom\u00eb t\u00eb lir\u00eb.<\/p>\n

Nj\u00eb tjet\u00ebr cil\u00ebsi interesante e k\u00ebtyre sistemeve \u00ebsht\u00eb se ato jan\u00eb t\u00eb shkall\u00ebzueshme lirisht. \u00c7far\u00eb duhet t\u00eb na interesoj\u00eb ne, si inxhinier\u00eb kaosolog\u00eb? Nd\u00ebrveprimi. <\/p>\n

Ka edhe dy p\u00ebrfundime interesante.
\n \"DevOps
\n
\nS\u00eb pari, ne kuptojm\u00eb se nj\u00eb sistem kompleks nuk mund t\u00eb thjeshtohet p\u00ebrmes thjeshtimit t\u00eb pjes\u00ebve t\u00eb tij. S\u00eb dyti, m\u00ebnyra e vetme p\u00ebr t\u00eb thjeshtuar nj\u00eb sistem kompleks \u00ebsht\u00eb p\u00ebrmes thjeshtimit t\u00eb nd\u00ebrveprimeve midis pjes\u00ebve t\u00eb tij. <\/p>\n

Si nd\u00ebrveprojm\u00eb? Ne t\u00eb gjith\u00eb jemi pjes\u00eb e nj\u00eb sistemi t\u00eb madh informativ q\u00eb quhet shoq\u00ebria njerzore. Ne nd\u00ebrveprojm\u00eb p\u00ebrmes nj\u00eb gjuhe t\u00eb p\u00ebrbashk\u00ebt, n\u00ebse e kemi at\u00eb, n\u00ebse e gjejm\u00eb.<\/p>\n

\"DevOps
\n
\nPor gjuha vet\u00eb \u00ebsht\u00eb nj\u00eb sistem adaptiv kompleks. Prandaj, p\u00ebr t\u00eb nd\u00ebrvepruar m\u00eb efektivisht dhe m\u00eb thjesht, na nevojitet krijimi i disa protokolleve. Kjo do t\u00eb thot\u00eb nj\u00eb rend t\u00eb simboleve dhe veprimeve q\u00eb do t\u00eb b\u00ebjn\u00eb shk\u00ebmbimin e informacionit midis nesh m\u00eb t\u00eb thjesht\u00eb, m\u00eb t\u00eb parashikuesh\u00ebm, m\u00eb kuptimplot\u00eb.<\/p>\n

Dua t\u00eb them se tendencat p\u00ebrkompleksim, adaptivitet, decentralizim, kaoticitet shihen n\u00eb t\u00eb gjith\u00eb. Si n\u00eb sistemet q\u00eb ne nd\u00ebrtojm\u00eb, ashtu edhe n\u00eb sistemet t\u00eb cil\u00ebve ne i p\u00ebrkasim.<\/p>\n

Dhe, p\u00ebr t\u00eb mos qen\u00eb fol\u00ebs goj\u00ebmadh, le t\u00eb shikojm\u00eb se si ndryshojn\u00eb ato sisteme q\u00eb ne krijojm\u00eb.<\/p>\n

\"DevOps
\n
\nE prisnit k\u00ebt\u00eb fjal\u00eb, e kuptoj. Jemi n\u00eb konferenc\u00ebn DevOps, sot kjo fjal\u00eb do t\u00eb shqiptohet diku rreth nj\u00ebqind mij\u00eb her\u00eb dhe m\u00eb pas do t\u00eb na shfaqet nat\u00ebn.<\/p>\n

Mikroservis\u00ebt jan\u00eb arkitektura e par\u00eb e softuerit q\u00eb ka lindur si nj\u00eb reagim ndaj praktikave DevOps, e cila ka p\u00ebr q\u00ebllim ta b\u00ebj\u00eb sistemin ton\u00eb m\u00eb fleksib\u00ebl, m\u00eb t\u00eb shkall\u00ebzuesh\u00ebm dhe t\u00eb siguroj\u00eb dor\u00ebzim t\u00eb vazhduesh\u00ebm. Si e arrin k\u00ebt\u00eb? Duke reduktuar v\u00ebllimin e sh\u00ebrbimeve, duke ngushtuar kufijt\u00eb e problemeve q\u00eb k\u00ebto sh\u00ebrbime p\u00ebrballojn\u00eb dhe duke reduktuar koh\u00ebn e dor\u00ebzimit. Kjo do t\u00eb thot\u00eb se ne e zvog\u00eblojm\u00eb e thjeshtojm\u00eb pjes\u00ebt e sistemit, duke rritur numrin e tyre; p\u00ebr pasoj\u00eb, natyrsh\u00ebm rritet kompleksiteti i nd\u00ebrveprimeve midis k\u00ebtyre pjes\u00ebve, duke shkaktuar probleme t\u00eb reja q\u00eb duhet t\u00eb zgjidhim.<\/p>\n

\"DevOps
\n
\nMikroservis\u00ebt nuk jan\u00eb fundi, ata jan\u00eb, n\u00eb thelb, nj\u00eb dit\u00eb t\u00eb kaluar, sepse po vjen Serverless. T\u00eb gjitha serverat jan\u00eb shkrir\u00eb, nuk ka servera, nuk ka sisteme operative, vet\u00ebm kod t\u00eb past\u00ebr ekzekutiv. Konfigurimet ve\u00e7mas, gjendjet ve\u00e7mas, gjith\u00e7ka menaxhohet p\u00ebrmes ngjarjeve. Bukuri, past\u00ebrti, qet\u00ebsi, nuk ka ngjarje, asgj\u00eb nuk ndodh, \u00ebsht\u00eb gjith\u00e7ka n\u00eb rend. <\/p>\n

Ku \u00ebsht\u00eb kompleksiteti? Kompleksiteti, \u00ebsht\u00eb e qart\u00eb, \u00ebsht\u00eb n\u00eb nd\u00ebrveprime. Sa mund t\u00eb b\u00ebj\u00eb nj\u00eb funksion vet\u00eb? Si nd\u00ebrvepron me funksione t\u00eb tjera? Radh\u00ebt e mesazheve, bazat e t\u00eb dh\u00ebnave, balancuesit. Si mund t\u00eb rifillosh ndonj\u00eb ngjarje kur ndodh nj\u00eb d\u00ebshtim? Nj\u00eb mori pyetjesh dhe pak p\u00ebrgjigjesh.<\/p>\n

Mikroservis\u00ebt dhe Serverless jan\u00eb gjith\u00e7ka q\u00eb ne, hipster\u00ebt e teknologjis\u00eb, i quajm\u00eb Cloud Native. Kjo \u00ebsht\u00eb e gjith\u00eb p\u00ebr cloud. Por cloud, n\u00eb thelb, \u00ebsht\u00eb gjithashtu i kufizuar n\u00eb shkall\u00ebzim. Ne jemi m\u00ebsuar ta shohim si nj\u00eb sistem t\u00eb shp\u00ebrndar\u00eb. N\u00eb t\u00eb v\u00ebrtet\u00eb, ku jetojn\u00eb serverat e ofruesve t\u00eb cloud? N\u00eb qendrat e t\u00eb dh\u00ebnave. K\u00ebshtu q\u00eb kemi nj\u00eb model t\u00eb caktuar, shum\u00eb t\u00eb kufizuar, t\u00eb shp\u00ebrndar\u00eb.<\/p>\n

Sot ne e dim\u00eb se interneti i gj\u00ebrave nuk \u00ebsht\u00eb m\u00eb thjesht nj\u00eb fraz\u00eb e madhe; sipas parashikimeve modeste, n\u00eb pes\u00eb deri n\u00eb dhjet\u00eb vitet e ardhshme do t\u00eb kemi miliarda pajisje t\u00eb lidhura me internetin. Nj\u00eb sasi e madhe e t\u00eb dh\u00ebnave t\u00eb dobishme dhe t\u00eb padobishme q\u00eb do t\u00eb derdhen n\u00eb cloud dhe do t\u00eb nxirren nga cloud. <\/p>\n

Cloud nuk do t\u00eb p\u00ebrballoj\u00eb, prandaj ne flasim gjithnj\u00eb e m\u00eb shum\u00eb p\u00ebr at\u00eb q\u00eb quhet 'kalkulim periferik'. Ose m\u00eb p\u00eblqen nj\u00eb p\u00ebrcaktim i mrekulluesh\u00ebm 'fog computing'. Ka nj\u00eb mistik\u00eb romantike dhe misteri.<\/p>\n

\"DevOps
\n
\nT\u00eb kalkulimet n\u00eb mjegull. B\u00ebhet fjal\u00eb se cloud jan\u00eb grumbuj t\u00eb centralizuar t\u00eb ujit, avujve, akullit, gur\u00ebve. Dhe mjegulla \u00ebsht\u00eb pika e ujit q\u00eb shp\u00ebrndahet p\u00ebrreth nesh n\u00eb atmosfer\u00eb. <\/p>\n

N\u00eb paradigmen e mjegull\u00ebs, pjesa m\u00eb e madhe e pun\u00ebs kryhet nga k\u00ebto pika n\u00eb m\u00ebnyr\u00eb t\u00eb autonomishme ose n\u00eb bashk\u00ebpunim me pika t\u00eb tjera. Ato konsumojn\u00eb cloud vet\u00ebm kur \u00ebsht\u00eb v\u00ebrtet urgjente. <\/p>\n

Pra, p\u00ebrs\u00ebri decentralizimi, autonomi, dhe sigurisht, shum\u00eb prej jush e kuptoni tashm\u00eb se ku po shkon e gjith\u00eb kjo, sepse nuk mund t\u00eb flasim p\u00ebr decentralizimin dhe t\u00eb mos p\u00ebrmendim blockchain. <\/p>\n

\"DevOps
\n
\nKa ata q\u00eb besojn\u00eb, ata jan\u00eb ata q\u00eb kan\u00eb investuar n\u00eb kriptovaluta. Ka ata q\u00eb besojn\u00eb, por kan\u00eb frik\u00eb, si un\u00eb, p\u00ebr shembull. Dhe ka ata q\u00eb nuk besojn\u00eb. Mund t\u00eb ket\u00eb shum\u00eb qasje. Ka teknologji, nj\u00eb gj\u00eb t\u00eb re t\u00eb paqart\u00eb, ka probleme. Si\u00e7 \u00ebsht\u00eb \u00e7do teknologji e re, ajo ngre m\u00eb shum\u00eb pyetje sesa p\u00ebrgjigje. <\/p>\n

Hype rreth blockchain \u00ebsht\u00eb i qart\u00eb. Edhe n\u00ebse e l\u00ebm\u00eb m\u00ebnjan\u00eb zhurm\u00ebn e floririt, vet\u00eb teknologjia ofron premtime t\u00eb shk\u00eblqyera p\u00ebr nj\u00eb t\u00eb ardhme m\u00eb t\u00eb ndritshme: m\u00eb shum\u00eb liri, m\u00eb shum\u00eb autonomi, besim global t\u00eb shp\u00ebrndar\u00eb. \u00c7far\u00eb \u00ebsht\u00eb p\u00ebr t\u00eb mos dashur? <\/p>\n

Si rezultat, gjithnj\u00eb e m\u00eb shum\u00eb inxhinier\u00eb n\u00eb mbar\u00eb bot\u00ebn po zhvillojn\u00eb aplikacione t\u00eb decentralizuara. Dhe kjo \u00ebsht\u00eb nj\u00eb forc\u00eb q\u00eb nuk mund t\u00eb injorohet duke th\u00ebn\u00eb thjesht: 'Ah, blockchain \u00ebsht\u00eb nj\u00eb baz\u00eb t\u00eb shp\u00ebrndar\u00eb e keqimplementuar'. Ose si\u00e7 p\u00eblqejn\u00eb t\u00eb thon\u00eb skeptik\u00ebt: 'Nuk ka aplikacione reale p\u00ebr blockchain'. N\u00ebse mendoni mir\u00eb, 150 vjet m\u00eb par\u00eb ata thonin t\u00eb nj\u00ebjt\u00ebn gj\u00eb p\u00ebr energjin\u00eb elektrike. Dhe madje n\u00eb disa aspekte kishin t\u00eb drejt\u00eb, sepse ajo q\u00eb energjia elektrike mund t\u00eb mund\u00ebsoj\u00eb sot, n\u00eb shekullin e 19-t\u00eb ishte plot\u00ebsisht e pamundur.<\/p>\n

Me rastin, kush e di se \u00e7far\u00eb logoje \u00ebsht\u00eb n\u00eb ekran? Kjo \u00ebsht\u00eb Hyperledger. Ky \u00ebsht\u00eb nj\u00eb projekt q\u00eb po zhvillohet n\u00ebn egid\u00ebn e The Linux Foundation, p\u00ebrfshin nj\u00eb grup teknologjish blockchain. Kjo \u00ebsht\u00eb v\u00ebrtet forca e komunitetit ton\u00eb t\u00eb kodit t\u00eb hapur.<\/p>\n

Inxhinieria e kaosit<\/b><\/h3>\n

\n\"DevOps
\n
\nPra, sistemi q\u00eb ne po zhvillojm\u00eb b\u00ebhet gjithnj\u00eb e m\u00eb i komplikuar, gjithnj\u00eb e m\u00eb kaotik, gjithnj\u00eb e m\u00eb adaptiv. Netflix ka qen\u00eb pionier n\u00eb sistemet mikroservis. Ata ishin disa nga t\u00eb par\u00ebt q\u00eb e kuptuan k\u00ebt\u00eb, ata zhvilluan nj\u00eb grup mjetesh, t\u00eb cilin e quajt\u00ebn Simian Army, m\u00eb i njohuri prej t\u00eb cil\u00ebve ishte Chaos Monkey<\/a><\/noindex>. Ai p\u00ebrcaktoi at\u00eb q\u00eb \u00ebsht\u00eb njohur si \"parimet e inxhinieris\u00eb s\u00eb kaosit\"<\/a><\/noindex>.<\/p>\n

Apropos, n\u00eb procesin e pun\u00ebs mbi raportin, ne madje e p\u00ebrktheu k\u00ebt\u00eb tekst n\u00eb gjuh\u00ebn ruse, k\u00ebshtu q\u00eb vizitoni linkun<\/a><\/noindex>, lexoni, komentoni, kritikoni.<\/p>\n

P\u00ebr t\u00eb qen\u00eb i shkurt\u00ebr, parimet e inxhinieris\u00eb s\u00eb kaosit flasin p\u00ebr k\u00ebt\u00eb. Sistemet e ndara komplekse n\u00eb thelb jan\u00eb t\u00eb paparashikueshme dhe n\u00eb thelb kan\u00eb gabime. Gabimet jan\u00eb t\u00eb pashmangshme, \u00e7ka do t\u00eb thot\u00eb se duhet t'i pranojm\u00eb k\u00ebto gabime dhe t\u00eb punojm\u00eb me k\u00ebto sisteme n\u00eb nj\u00eb m\u00ebnyr\u00eb krejt\u00ebsisht t\u00eb ndryshme. <\/p>\n

Ne duhet t\u00eb p\u00ebrpiqemi t\u00eb futim k\u00ebto gabime n\u00eb sistemet tona t\u00eb prodhimit, p\u00ebr t\u00eb testuar k\u00ebto sisteme p\u00ebr k\u00ebt\u00eb aft\u00ebsi adaptuese, p\u00ebr k\u00ebt\u00eb aft\u00ebsi vet\u00eb-organizimi, p\u00ebr mbijetes\u00eb. <\/p>\n

Dhe kjo ndryshon gjith\u00e7ka. Jo vet\u00ebm se si e nisnim sistemin n\u00eb prodhim, por edhe se si i zhvillojm\u00eb, si i testojm\u00eb. Nuk ka nj\u00eb proces stabilizimi, ngrirjeje t\u00eb kodit, p\u00ebrkundrazi, ka nj\u00eb proces t\u00eb vazhduesh\u00ebm t\u00eb destabilizimit. Ne p\u00ebrpiqemi ta vrasim sistemin dhe t\u00eb shohim se si ai vazhdon t\u00eb mbijoj\u00eb.<\/p>\n

Protokolet e Integrimit t\u00eb Sistemit t\u00eb Distribuar<\/b><\/h3>\n

\n\"DevOps
\n
\nPrandaj, kjo k\u00ebrkon q\u00eb sistemet tona t\u00eb ndodhin ndryshime gjithashtu. Q\u00eb t\u00eb b\u00ebhen m\u00eb t\u00eb q\u00ebndrueshme, u duhen protokolle t\u00eb reja bashk\u00ebpunimi mes pjes\u00ebve t\u00eb tyre. Q\u00eb k\u00ebto pjes\u00eb t\u00eb mund t\u00eb bien dakord dhe t\u00eb arrijn\u00eb nj\u00eb vet\u00eb-organizim. Dhe gjithashtu shfaqen mjete t\u00eb reja, protokolle t\u00eb reja, q\u00eb un\u00eb i quaj \"protokolet e bashk\u00ebpunimit t\u00eb sistemeve t\u00eb distribuar\".<\/p>\n

\"DevOps
\n
\nP\u00ebr \u00e7far\u00eb po flas? S\u00eb pari, projekti Opentracing<\/a><\/noindex>. Nj\u00eb p\u00ebrpjekje p\u00ebr t\u00eb krijuar nj\u00eb protokoll t\u00eb p\u00ebrbashk\u00ebt t\u00eb p\u00ebrcjelljes s\u00eb distribuar, i cili \u00ebsht\u00eb nj\u00eb mjet t\u00ebr\u00ebsisht i nevojsh\u00ebm p\u00ebr debugimin e sistemeve komplekse t\u00eb ndara.<\/p>\n

\"DevOps
\n
\nPastaj \u2014 Open Policy Agent<\/a><\/noindex>. Ne themi se nuk mund t\u00eb parashikojm\u00eb se \u00e7far\u00eb do t\u00eb ndodh\u00eb me sistemin, q\u00eb do t\u00eb thot\u00eb se duhet ta rrisim observabilitetin e tij. Opentracing i p\u00ebrket grupit t\u00eb mjeteve q\u00eb na japin observabilitetin e sistemeve tona. Por na nevojitet observabiliteti p\u00ebr t\u00eb p\u00ebrcaktuar n\u00ebse sistemi sillet si\u00e7 e presim apo jo. Si mund ta p\u00ebrcaktojm\u00eb sjelljen e pritur? Duke caktuar ndonj\u00eb politik\u00eb, nj\u00eb set rregullash. Projekti Open Policy Agent merret me p\u00ebrcaktimin e k\u00ebtij seti rregullash n\u00eb nj\u00eb gam\u00eb t\u00eb gjer\u00eb: nga qasja deri te vendosja e burimeve.<\/p>\n

\"DevOps
\n
\nSi\u00e7 e thash\u00eb, sistemet tona jan\u00eb gjithnj\u00eb e m\u00eb shum\u00eb t\u00eb menaxhuara nga ngjarjet. Serverless \u2014 \u00ebsht\u00eb nj\u00eb shembull i shk\u00eblqyer i sistemeve t\u00eb menaxhuara nga ngjarjet. Q\u00eb t\u00eb mund t\u00eb transmetojm\u00eb ngjarje mes sistemeve dhe t'i ndjekim ato, na nevojitet nj\u00eb gjuh\u00eb e p\u00ebrbashk\u00ebt, nj\u00eb protokoll i p\u00ebrbashk\u00ebt se si flasim p\u00ebr ngjarjet, si i kalojm\u00eb ato nj\u00ebri-tjetrit. K\u00ebt\u00eb e b\u00ebn projekti i quajtur Cloudevents<\/a><\/noindex>.<\/p>\n

\"DevOps
\n
\nNj\u00eb fluks i vazhduesh\u00ebm ndryshimesh q\u00eb mbulon sistemet tona, duke i destabilizuar vazhdimisht, \u00ebsht\u00eb nj\u00eb fluks i vazhduesh\u00ebm i artefakteve t\u00eb softuerit. Q\u00eb t\u00eb mund t\u00eb mbajm\u00eb k\u00ebt\u00eb fluks t\u00eb vazhduesh\u00ebm t\u00eb ndryshimeve, na nevojitet nj\u00eb protokoll i p\u00ebrbashk\u00ebt, me ndihm\u00ebn e t\u00eb cilit mund t\u00eb flasim p\u00ebr at\u00eb \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb artifact softueri, si \u00ebsht\u00eb verifikuar, \u00e7far\u00eb verifikimi ka kaluar. K\u00ebt\u00eb e b\u00ebn projekti i quajtur Grafeas<\/a><\/noindex>. Pra, nj\u00eb protokoll i p\u00ebrbashk\u00ebt p\u00ebr metadatat e artefakteve t\u00eb softuerit.<\/p>\n

\"DevOps
\n
\nDhe, n\u00eb fund, n\u00ebse duam q\u00eb sistemet tona t\u00eb jen\u00eb plot\u00ebsisht autonome, adaptuese, t\u00eb vet\u00eb-organizohen, duhet t'u japim atyre t\u00eb drejt\u00ebn e vet\u00eb-identifikimit. Projekti i quajtur spiffe<\/a><\/noindex> pikerisht k\u00ebt\u00eb b\u00ebn\u00eb. Ky \u00ebsht\u00eb gjithashtu nj\u00eb projekt n\u00ebn egid\u00ebn e Cloud Native Computing Foundation.<\/p>\n

T\u00eb gjitha k\u00ebto projekte jan\u00eb t\u00eb reja, t\u00eb gjitha kan\u00eb nevoj\u00eb p\u00ebr dashurin\u00eb ton\u00eb, p\u00ebr verifikimin ton\u00eb. T\u00eb gjitha jan\u00eb kod i hapur, testimi yn\u00eb, implementimi yn\u00eb. Ato na tregojn\u00eb n\u00eb cilin drejtim po ec\u00ebn teknologjia. <\/p>\n

Por DevOps nuk ka qen\u00eb kurr\u00eb fillimisht p\u00ebr teknologjin\u00eb, gjithmon\u00eb ka qen\u00eb p\u00ebr bashk\u00ebpunimin mes njer\u00ebzve. Dhe k\u00ebshtu, n\u00ebse duam q\u00eb sistemet q\u00eb po zhvillojm\u00eb t\u00eb ndryshojn\u00eb, at\u00ebher\u00eb ne duhet t\u00eb ndryshojm\u00eb vet\u00eb. N\u00eb t\u00eb v\u00ebrtet\u00eb, ne tashm\u00eb po ndryshojm\u00eb, nuk kemi shum\u00eb zgjedhje. <\/p>\n

\"DevOps
\n
\nKa nj\u00eb lib\u00ebr t\u00eb shk\u00eblqyer libri<\/a><\/noindex> nga shkrimtarja britanike Rachael Botsman, n\u00eb t\u00eb cilin ajo shkruan p\u00ebr evolucionin e besimit gjat\u00eb historis\u00eb njer\u00ebzore. Ajo thot\u00eb se n\u00eb fillim, n\u00eb shoq\u00ebrit\u00eb primitive, besimi ishte lokal, dometh\u00ebn\u00eb ne besonim vet\u00ebm atyre q\u00eb i njihnim personalisht. <\/p>\n

M\u00eb pas kishte nj\u00eb periudh\u00eb t\u00eb gjat\u00eb \u2014 nj\u00eb koh\u00eb t\u00eb err\u00ebt, kur besimi ishte centralizuar, kur filluam t\u00eb besojm\u00eb njer\u00ebzve q\u00eb nuk i njihnim n\u00eb baz\u00eb t\u00eb asaj se ishim pjes\u00eb e nj\u00eb institucioni shoq\u00ebror apo shtet\u00ebror.<\/p>\n

Dhe ja, \u00e7far\u00eb shohim n\u00eb bot\u00ebn ton\u00eb moderne: besimi po b\u00ebhet gjithnj\u00eb e m\u00eb shum\u00eb i shp\u00ebrndar\u00eb dhe i decentralizuar, dhe bazohet n\u00eb lirin\u00eb e flukseve t\u00eb informacionit, n\u00eb disponueshm\u00ebrin\u00eb e informacionit. <\/p>\n

N\u00ebse e mendojm\u00eb mir\u00eb, kjo disponibiliteti q\u00eb e b\u00ebn at\u00eb besim t\u00eb mundsh\u00ebm e realizojm\u00eb ne. Kjo do t\u00eb thot\u00eb se m\u00ebnyra se si bashk\u00ebpunojm\u00eb dhe si veprojm\u00eb duhet t\u00eb ndryshoj\u00eb, sepse organizatat IT t\u00eb vjetra, t\u00eb centralizuara dhe hierarkike, po humbasin r\u00ebnd\u00ebsin\u00eb e tyre. Ato po shuhen. <\/p>\n

Bazat e organizatave DevOps<\/b><\/h3>\n

\nOrganizata ideale DevOps e s\u00eb ardhmes \u00ebsht\u00eb nj\u00eb sistem decentralizuar dhe adaptiv, p\u00ebrb\u00ebr\u00eb nga ekipe autonome, secila prej t\u00eb cilave p\u00ebrb\u00ebhet nga individ\u00eb autonom\u00eb. K\u00ebto ekipe jan\u00eb t\u00eb shp\u00ebrndara n\u00eb t\u00eb gjith\u00eb bot\u00ebn dhe bashk\u00ebpunojn\u00eb n\u00eb m\u00ebnyr\u00eb efektive me ndihm\u00ebn e komunikimit asinkron, p\u00ebrmes protokolleve t\u00eb informacionit me transparenc\u00eb t\u00eb lart\u00eb. Mjaft e bukur, apo jo? Nj\u00eb t\u00eb ardhme shum\u00eb e bukur.<\/p>\n

Sigurisht, kjo \u00ebsht\u00eb e pamundur pa ndryshime kulturore. Ne duhet t\u00eb kemi lider\u00eb transformues, p\u00ebrgjegj\u00ebsi personale, motivim t\u00eb brendsh\u00ebm.<\/p>\n

\"DevOps
\n
\nKjo \u00ebsht\u00eb baza e organizatave DevOps: transparenca e informacionit, komunikimet asinkrone, lideri transformues, decentralizimi. <\/p>\n

Shk\u00ebputja<\/b><\/h3>\n

\nSistemet q\u00eb ne jemi pjes\u00eb e tyre, si edhe ato q\u00eb nd\u00ebrtojm\u00eb, po b\u00ebhen gjithnj\u00eb e m\u00eb kaotike, dhe ne, njer\u00ebzit, na v\u00ebshtir\u00ebson t\u00eb pranojm\u00eb k\u00ebt\u00eb mendim, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb heqim dor\u00eb nga iluzioni i kontrollit. Ne p\u00ebrpiqemi t\u00eb vazhdojm\u00eb t'i kontrollojm\u00eb ato, dhe kjo shpeshher\u00eb na \u00e7on n\u00eb shterim. Po e them k\u00ebt\u00eb nga p\u00ebrvoja ime, edhe un\u00eb kam p\u00ebrjetuar, kam qen\u00eb gjithashtu i paaft\u00eb ndaj d\u00ebshtimeve t\u00eb paparashikuara n\u00eb prodhim.<\/p>\n

\"DevOps
\n
\nShk\u00ebputja ndodh kur ne mundohemi t\u00eb kontrollojm\u00eb at\u00eb q\u00eb n\u00eb thelb nuk mund t\u00eb kontrollohet. Kur ne shterim, gjith\u00e7ka humbet kuptimin, sepse humbasim d\u00ebshir\u00ebn p\u00ebr t\u00eb b\u00ebr\u00eb di\u00e7ka t\u00eb re, ne marrim nj\u00eb pozicion mbrojt\u00ebs dhe fillojm\u00eb t\u00eb mbrojm\u00eb at\u00eb q\u00eb kemi. <\/p>\n

Profili i inxhinieris\u00eb, si\u00e7 m\u00eb p\u00eblqen ta kujtoj shpesh, \u00ebsht\u00eb para s\u00eb gjithash nj\u00eb profesion krijues. N\u00ebse humbasim d\u00ebshir\u00ebn p\u00ebr t\u00eb krijuar di\u00e7ka, at\u00ebher\u00eb shnd\u00ebrrohemi n\u00eb hi, shnd\u00ebrrohemi n\u00eb plehra. Njer\u00ebzit shterin, organizatat shterin.<\/p>\n

Sipas mendimit tim, vet\u00ebm pranimi i fuqis\u00eb krijuese t\u00eb kaosit, vet\u00ebm nd\u00ebrtimi i bashk\u00ebpunimit sipas parimeve t\u00eb tij \u2014 kjo do t\u00eb na ndihmoj\u00eb t\u00eb mos humbasim at\u00eb q\u00eb \u00ebsht\u00eb e mir\u00eb n\u00eb profesionin ton\u00eb. <\/p>\n

K\u00ebt\u00eb ju uroj: t\u00eb doni pun\u00ebn tuaj, t\u00eb doni at\u00eb q\u00eb b\u00ebjm\u00eb. Ky bot\u00eb ushqehet me informacionin, na \u00ebsht\u00eb dh\u00ebn\u00eb nderi ta ushqejm\u00eb at\u00eb. Prandaj, le t\u00eb studiojm\u00eb kaosin, le t\u00eb jemi kaosolog\u00eb, le t\u00eb sjellim vler\u00eb, t\u00eb krijojm\u00eb di\u00e7ka t\u00eb re, dhe problemet, si\u00e7 e dim\u00eb, jan\u00eb t\u00eb pashmangshme, dhe kur ato krijohen, ne thjesht do t\u00eb themi 'Ops!', dhe problemi do t\u00eb zgjidhet. <\/p>\n

\u00c7far\u00eb tjet\u00ebr p\u00ebr Chaos Monkey?<\/b><\/p>\n

N\u00eb t\u00eb v\u00ebrtet\u00eb, t\u00eb gjitha k\u00ebto mjete jan\u00eb shum\u00eb t\u00eb reja. Edhe Netflix nd\u00ebrtuan mjete p\u00ebr veten e tyre. Nd\u00ebrtoni mjete p\u00ebr veten tuaj. Lexoni parimet e inxhinieris\u00eb s\u00eb kaosit dhe p\u00ebrputhuni me ato parime, e jo t\u00eb k\u00ebrkoni mjete t\u00eb tjera q\u00eb dikush tjet\u00ebr ka nd\u00ebrtuar. <\/p>\n

Provoni t\u00eb kuptoni si d\u00ebshtojn\u00eb sistemet tuaja dhe filloni t'i b\u00ebni ato t\u00eb d\u00ebshtojn\u00eb dhe shikoni si i p\u00ebrballojn\u00eb goditjet. Kjo \u00ebsht\u00eb n\u00eb radh\u00eb t\u00eb par\u00eb. Dhe mjete mund t\u00eb k\u00ebrkoni. Ka projekte t\u00eb ndryshme. <\/p>\n

Nuk e kuptova plot\u00ebsisht momentin kur ju that\u00eb se sistemi nuk mund t\u00eb thjeshtohet duke thjeshtuar komponent\u00ebt e tij, dhe menj\u00ebher\u00eb kaluat tek mikrosh\u00ebrbimet, t\u00eb cilat p\u00ebr nga ana e tyre thjeshtojn\u00eb sistemin duke thjeshtuar vet\u00eb komponent\u00ebt dhe duke e komplikuar nd\u00ebrlidhjen. K\u00ebto n\u00eb thelb jan\u00eb dy pjes\u00eb q\u00eb p\u00ebrmbysin nj\u00ebra-tjetr\u00ebn. <\/b><\/p>\n

Plot\u00ebsisht e sakt\u00eb, mikrosh\u00ebrbimet jan\u00eb nj\u00eb tem\u00eb shum\u00eb kontradiktore n\u00eb p\u00ebrgjith\u00ebsi. N\u00eb t\u00eb v\u00ebrtet\u00eb, thjeshtimi i pjes\u00ebve rrit fleksibilitetin. \u00c7far\u00eb na japin mikrosh\u00ebrbimet? Na japin fleksibilitet dhe shpejt\u00ebsi, por patjet\u00ebr nuk na japin thjesht\u00ebsi. Ato rrisin kompleksitetin.<\/p>\n

Pra, n\u00eb filozofin\u00eb DevOps, mikrosh\u00ebrbimet nuk jan\u00eb aq t\u00eb mira apo jo?<\/b><\/p>\n

\u00c7do mir\u00eb ka an\u00ebn e saj t\u00eb err\u00ebt. Ka nj\u00eb mir\u00eb: kjo rrit fleksibilitetin, na jep mund\u00ebsin\u00eb p\u00ebr t\u00eb b\u00ebr\u00eb ndryshime m\u00eb shpejt, por rrit kompleksitetin dhe, p\u00ebr pasoj\u00eb, brisht\u00ebsin\u00eb e gjith\u00eb sistemit. <\/p>\n

Megjithat\u00eb, ku \u00ebsht\u00eb akcenti m\u00eb shum\u00eb: tek thjeshtimi i nd\u00ebrlidhjes apo tek thjeshtimi i pjes\u00ebve?<\/b> <\/p>\n

Akcenti, padyshim, \u00ebsht\u00eb tek thjeshtimi i nd\u00ebrlidhjeve, sepse n\u00ebse e shohim nga pik\u00ebpamja se si punojm\u00eb, s\u00eb pari duhet t\u00eb fokusohemi n\u00eb thjeshtimin e nd\u00ebrlidhjeve dhe jo n\u00eb thjeshtimin e pun\u00ebs s\u00eb secilit prej nesh ve\u00e7mas. Sepse thjeshtimi i pun\u00ebs \u2014 kjo \u00ebsht\u00eb shnd\u00ebrrimi n\u00eb robota. Kjo funksionon mjaft mir\u00eb n\u00eb McDonald's, kur je i urdh\u00ebruar: k\u00ebtu v\u00eb hamburgerin, k\u00ebtu i hedh salc\u00ebn. Kjo n\u00eb pun\u00ebn ton\u00eb krijuese nuk funksionon fare.<\/p>\n

A \u00ebsht\u00eb e v\u00ebrtet\u00eb se gjith\u00e7ka q\u00eb keni treguar jeton n\u00eb nj\u00eb bot\u00eb pa konkurrenc\u00eb, dhe kaosi aty \u00ebsht\u00eb kaq i mir\u00eb, dhe nuk ka kontradikta brenda k\u00ebtij kaosi, askush nuk d\u00ebshiron t\u00eb haj\u00eb, t\u00eb vras\u00eb? Si duhet t\u00eb jetojn\u00eb konkurrenca dhe DevOps?<\/b><\/p>\n

Epo, varet se p\u00ebr cilin konkurrenc\u00eb po flasim. A \u00ebsht\u00eb kjo konkurrenca n\u00eb vendin e pun\u00ebs apo konkurrenca midis kompanive? <\/p>\n

Konkurrenca e sh\u00ebrbimeve, t\u00eb cilat ekzistojn\u00eb, sepse sh\u00ebrbimet nuk jan\u00eb thjesht disa kompani. Ne po krijojm\u00eb nj\u00eb tip t\u00eb ri t\u00eb ambientit informacionit, dhe \u00e7do ambient nuk mund t\u00eb jetoj\u00eb pa konkurrenc\u00eb. Konkurenca \u00ebsht\u00eb gjithandej.<\/b><\/p>\n

T\u00eb nj\u00ebjt\u00ebt Netflix, marrim ata si model roli. Pse e shpik\u00ebn k\u00ebt\u00eb? Sepse kishin nevoj\u00eb t\u00eb ishin konkurrues. Kjo fleksibilitet dhe shpejt\u00ebsi l\u00ebvizjeje, \u00ebsht\u00eb k\u00ebrkesa e v\u00ebrtet\u00eb konkurruese, ajo sjell kaos n\u00eb sistemet tona. Pra, kaosi nuk \u00ebsht\u00eb di\u00e7ka q\u00eb e b\u00ebjm\u00eb me vet\u00ebdije, sepse e duam, \u00ebsht\u00eb ajo q\u00eb ndodh p\u00ebr shkak se kjo \u00ebsht\u00eb ajo q\u00eb k\u00ebrkon bota. Na duhet t\u00eb adaptohemi. Dhe kaosi \u00ebsht\u00eb rezultat i konkurrenc\u00ebs.<\/p>\n

Do t\u00eb thot\u00eb, kaosi \u00ebsht\u00eb munges\u00eb e q\u00ebllimeve, apo jo? Apo ato q\u00ebllime q\u00eb nuk duam t'i shohim? Jemi n\u00eb nj\u00eb kasolle dhe nuk e kuptojm\u00eb q\u00ebllimet e t\u00eb tjer\u00ebve. N\u00eb t\u00eb v\u00ebrtet\u00eb, konkurrenca ekziston fal\u00eb q\u00ebllimeve tona t\u00eb qarta, dhe ne e dim\u00eb se ku do t\u00eb shkojm\u00eb n\u00eb \u00e7do moment t\u00eb ardhsh\u00ebm. Kjo, n\u00eb mendimin tim, \u00ebsht\u00eb themeli i DevOps.<\/b><\/p>\n

Nj\u00eb tjet\u00ebr pik\u00ebpamje mbi \u00e7\u00ebshtjen. Mendoj se q\u00ebllimi yn\u00eb \u00ebsht\u00eb i nj\u00ebjt\u00eb: t\u00eb mbijetojm\u00eb dhe ta b\u00ebjm\u00eb k\u00ebt\u00eb me
\nsa m\u00eb shum\u00eb k\u00ebnaq\u00ebsi. Dhe q\u00ebllimi konkurrues i \u00e7do organizate \u00ebsht\u00eb po i till\u00eb. Mbijetesa shpesh ndodh n\u00eb luft\u00ebn konkurruese, k\u00ebtu s'ka \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb.<\/p>\n

Ky vit konferenca DevOpsDays Moscow<\/a><\/noindex> do t\u00eb mbahet m\u00eb 7 dhjetor n\u00eb \"Tehnopolis\". Deri m\u00eb 11 n\u00ebntor pranojm\u00eb aplikime p\u00ebr referate. Na shkruani<\/a><\/noindex> n\u00ebse d\u00ebshironi t\u00eb flisni.<\/p>\n

Regjistrimi p\u00ebr pjes\u00ebmarr\u00ebsit \u00ebsht\u00eb i hapur, bileta kushton 7000 rubla. Bashkohuni! \n<\/p><\/blockquote>\n

Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0438 \u0434\u0438\u0440\u0435\u043a\u0442\u043e\u0440 \u00abOtomato Software\u00bb, \u043e\u0434\u0438\u043d \u0438\u0437 \u0438\u043d\u0438\u0446\u0438\u0430\u0442\u043e\u0440\u043e\u0432 \u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0442\u043e\u0440\u043e\u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0418\u0437\u0440\u0430\u0438\u043b\u0435 DevOps-\u0441\u0435\u0440\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0410\u043d\u0442\u043e\u043d \u0412\u0430\u0439\u0441 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b \u043d\u0430 \u043f\u0440\u043e\u0448\u043b\u043e\u0433\u043e\u0434\u043d\u0435\u043c DevOpsDays Moscow \u043f\u0440\u043e \u0442\u0435\u043e\u0440\u0438\u044e \u0445\u0430\u043e\u0441\u0430 \u0438 \u0433\u043b\u0430\u0432\u043d\u044b\u0435 \u043f\u0440\u0438\u043d\u0446\u0438\u043f\u044b \u0445\u0430\u043e\u0441\u043d\u043e\u0439 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u0438\u0438, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043e\u0431\u044a\u044f\u0441\u043d\u0438\u043b, \u043a\u0430\u043a \u0443\u0441\u0442\u0440\u043e\u0435\u043d\u0430 \u0438\u0434\u0435\u0430\u043b\u044c\u043d\u0430\u044f DevOps-\u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f \u0431\u0443\u0434\u0443\u0449\u0435\u0433\u043e. \u041c\u044b \u043f\u0440\u0438\u0433\u043e\u0442\u043e\u0432\u0438\u043b\u0438 \u0442\u0435\u043a\u0441\u0442\u043e\u0432\u0443\u044e \u0432\u0435\u0440\u0441\u0438\u044e \u0434\u043e\u043a\u043b\u0430\u0434\u0430. \u0414\u043e\u0431\u0440\u043e\u0435 \u0443\u0442\u0440\u043e! DevOpsDays \u0432 \u041c\u043e\u0441\u043a\u0432\u0435 \u0432\u0442\u043e\u0440\u043e\u0439 \u0433\u043e\u0434 \u043f\u043e\u0434\u0440\u044f\u0434, \u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0440\u0430\u0437 \u043d\u0430 \u044d\u0442\u043e\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29435,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39219","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\udd47DevOps dhe Kaosi: dor\u00ebzimi i softuerit n\u00eb nj\u00eb bot\u00eb t\u00eb decentralizuar | ProHoster","description":"I sapun dhe drejtor i \u00abOtomato Software\u00bb, nj\u00eb nga iniciator\u00ebt dhe instruktoret e par\u00eb t\u00eb \u00e7ertifikimit DevOps n\u00eb Izrael, Anton Weiss, foli vitin e kaluar","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire","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\u0414\u0435\u0432\u041e\u043f\u0441 \u0438 \u0425\u0430\u043e\u0441: \u0434\u043e\u0441\u0442\u0430\u0432\u043a\u0430 \u041f\u041e \u0432 \u0434\u0435\u0446\u0435\u043d\u0442\u0440\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u043e\u043c \u043c\u0438\u0440\u0435 | ProHoster","og:description":"\u041e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0438 \u0434\u0438\u0440\u0435\u043a\u0442\u043e\u0440 \u00abOtomato Software\u00bb, \u043e\u0434\u0438\u043d \u0438\u0437 \u0438\u043d\u0438\u0446\u0438\u0430\u0442\u043e\u0440\u043e\u0432 \u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0442\u043e\u0440\u043e\u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0418\u0437\u0440\u0430\u0438\u043b\u0435 DevOps-\u0441\u0435\u0440\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0410\u043d\u0442\u043e\u043d \u0412\u0430\u0439\u0441 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b \u043d\u0430 \u043f\u0440\u043e\u0448\u043b\u043e\u0433\u043e\u0434\u043d\u0435\u043c","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire","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:28:31+00:00","article:modified_time":"2019-10-31T19:28:31+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39219","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-24 01:19:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:54:41","updated":"2026-01-24 01:19:20","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\/39219","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=39219"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/39219\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/29435"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=39219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=39219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=39219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}