{"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: dor\u00ebzimi i softuerit n\u00eb nj\u00eb bot\u00eb t\u00eb decentralizuar","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Krijuesi dhe drejtor i \u00abOtomato Software\u00bb, nj\u00eb nga iniciator\u00ebt dhe instruktor\u00ebt e certifikimit t\u00eb par\u00eb DevOps n\u00eb Izrael, Anton Vajs tregoi n\u00eb 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 se si \u00ebsht\u00eb organizata ideale DevOps e s\u00eb ardhmes.<\/p>\n

Ne p\u00ebrgatit\u00ebm versionin tekstual t\u00eb referatit. <\/p>\n

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

DevOpsDays n\u00eb Mosk\u00eb p\u00ebr vitin e dyt\u00eb radhazi, un\u00eb p\u00ebr her\u00eb t\u00eb dyt\u00eb n\u00eb k\u00ebt\u00eb sken\u00eb, shumica nga ju 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, po shumizohet, dhe m\u00eb e r\u00ebnd\u00ebsishmja, do t\u00eb thot\u00eb se ka ardhur koha t\u00eb flasim p\u00ebr at\u00eb se \u00e7far\u00eb n\u00ebnkupton DevOps n\u00eb vitin 2018. <\/p>\n

Ngrini duar ata q\u00eb mendojn\u00eb se n\u00eb vitin 2018 DevOps \u00ebsht\u00eb tashm\u00eb nj\u00eb profesion? Ka disa. Ka ndonj\u00eb DevOps-inxhinier n\u00eb sall\u00eb, q\u00eb n\u00eb p\u00ebrshkrimin e pun\u00ebs shkruan \u00abDevOps-inxhinier\u00bb? Ka ndonj\u00eb DevOps-menaxher? Asnj\u00eb. DevOps-arkitekt\u00eb? Po ashtu, asnj\u00eb. Pak shum\u00eb. A \u00ebsht\u00eb v\u00ebrtet askush q\u00eb nuk e ka shkruar se \u00ebsht\u00eb DevOps-inxhinier?<\/p>\n

Dhe k\u00ebshtu, shumica prej jush mendon se \u00ebsht\u00eb nj\u00eb antipattern? Se nuk duhet t\u00eb ekzistoj\u00eb nj\u00eb profesion i till\u00eb? Ne mund t\u00eb mendojm\u00eb gjith\u00e7ka, por derisa t\u00eb mendojm\u00eb, industria vazhdon t\u00eb l\u00ebviz\u00eb 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, e cila siguron bashk\u00ebpunim efektiv midis zhvilluesve dhe devops-\u00ebve. E megjithat\u00eb, nuk \u00ebsht\u00eb aq e re. N\u00ebse d\u00ebshmojm\u00eb p\u00ebr Twitter-in, kat\u00ebr vjet m\u00eb par\u00eb filluan t\u00eb flisnin p\u00ebr k\u00ebt\u00eb. Dhe deri tani, interesi p\u00ebr k\u00ebt\u00eb po rritet e po rritet, dometh\u00ebn\u00eb problemi ekziston. Duhet zgjidhur problemi.<\/p>\n

\"DevOps
\n
\nNe jemi krijues, nuk e ndalim leht\u00eb veten. Ne themi: DevOps nuk \u00ebsht\u00eb nj\u00eb fjal\u00eb mjaft gjith\u00ebp\u00ebrfshir\u00ebse, i mungojn\u00eb shum\u00eb elemente interesante. Dhe ne shkojm\u00eb n\u00eb laborator\u00ebt tan\u00eb sekret\u00eb dhe fillojm\u00eb t\u00eb krijojm\u00eb mutacione kurioze: DevTestOps, GitOps, DevSecOps, BizDevOps, ProdOps.<\/p>\n

\"DevOps
\n
\nLogjika \u00ebsht\u00eb e fort\u00eb, apo jo? Ne kemi nj\u00eb sistem shp\u00ebrndarjeje jo funksional, kemi sisteme t\u00eb paq\u00ebndrueshme dhe p\u00ebrdorues t\u00eb pak\u00ebnaqur, nuk arrijm\u00eb t\u00eb nxjerrim software-n n\u00eb koh\u00eb, nuk p\u00ebrputhemi me buxhetin. Si do ta zgjidhim t\u00eb gjith\u00eb k\u00ebt\u00eb? Ne do t\u00eb shpikim nj\u00eb fjal\u00eb t\u00eb re! Ajo do t\u00eb p\u00ebrfundoj\u00eb me \u00abOps\u00bb, dhe problemi zgjidhet.<\/p>\n

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

Kjo \u00ebsht\u00eb nj\u00eb gj\u00eb q\u00eb largohet nga sfondi, n\u00ebse ne i kujtojm\u00eb vetes pse e kemi krijuar gjith\u00eb k\u00ebt\u00eb. E kemi shpikur k\u00ebt\u00eb DevOps p\u00ebr t\u00eb b\u00ebr\u00eb dor\u00ebzimin e softuerit dhe pun\u00ebn ton\u00eb n\u00eb k\u00ebt\u00eb proces sa m\u00eb t\u00eb leht\u00eb, pa dhembje, efikase dhe, m\u00eb e r\u00ebnd\u00ebsishmja, t\u00eb k\u00ebndshme. <\/p>\n

DevOps ka dal\u00eb nga dhimbja. Dhe na ka lodhur t\u00eb vuajm\u00eb. Dhe p\u00ebr t'u siguruar q\u00eb kjo ndodh, ne bazojm\u00eb praktikat tona n\u00eb praktikat e p\u00ebrjetshme: bashk\u00ebpunim efektiv, praktika t\u00eb rrjedh\u00ebs dhe m\u00eb e r\u00ebnd\u00ebsishmja, mendimi sistemik, 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 sistemik, le t\u00eb kujtojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb sistem.<\/p>\n

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

\"DevOps
\n
\nNga k\u00ebndv\u00ebshtrimi i mendimit sistemik, sistemi \u00ebsht\u00eb nj\u00eb e t\u00ebr\u00eb q\u00eb p\u00ebrb\u00ebhet nga pjes\u00ebt. N\u00eb k\u00ebt\u00eb kuptim, secili prej nesh \u00ebsht\u00eb nj\u00eb sistem. Organizatat ku punojm\u00eb jan\u00eb sisteme. Dhe ajo q\u00eb ne po nd\u00ebrtojm\u00eb s\u00eb bashku quhet sistem.<\/p>\n

E gjith\u00eb kjo \u00ebsht\u00eb pjes\u00eb e nj\u00eb sistemi socioteknologjik t\u00eb madh. Dhe vet\u00ebm n\u00ebse e kuptojm\u00eb se si ky sistem socioteknologjik punon s\u00eb bashku, mund t\u00eb optimizojm\u00eb di\u00e7ka n\u00eb k\u00ebt\u00eb drejtim. <\/p>\n

Nga k\u00ebndv\u00ebshtrimi i mendimit sistemik, sistemi ka disa cil\u00ebsi interesante. S\u00eb pari, ai p\u00ebrb\u00ebhet nga pjes\u00eb, do t\u00eb thot\u00eb q\u00eb sjellja e tij varet nga sjellja e pjes\u00ebve. T\u00eb gjitha pjes\u00ebt e tij jan\u00eb gjithashtu t\u00eb nd\u00ebrlidhura. Pra, 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 kuptohet ose parashikohet sjellja e tij. <\/p>\n

Nga k\u00ebndv\u00ebshtrimi i sjelljes, ka nj\u00eb fakt tjet\u00ebr interesant. Nj\u00eb sistem mund t\u00eb b\u00ebj\u00eb di\u00e7ka q\u00eb asnj\u00eb nga pjes\u00ebt e tij t\u00eb ve\u00e7anta nuk mund ta b\u00ebj\u00eb. <\/p>\n

Si\u00e7 tha doktor Russell Ackoff (nj\u00eb nga themeluesit e mendimit sistemik), kjo \u00ebsht\u00eb mjaft e leht\u00eb t\u00eb provohet p\u00ebrmes nj\u00eb eksperimentin mendor. P\u00ebr shembull, kush n\u00eb sall\u00eb di t\u00eb shkruaj\u00eb kod? Shum\u00eb duar, dhe kjo \u00ebsht\u00eb e natyrshme, sepse \u00ebsht\u00eb nj\u00eb nga k\u00ebrkesat kryesore p\u00ebr profesionin ton\u00eb. Ju dini t\u00eb shkruani, por duar tua ndaras mund t\u00eb shkruajn\u00eb kod? Ka t\u00eb till\u00eb q\u00eb do t\u00eb thon\u00eb: \u00abNuk jan\u00eb duar q\u00eb shkruajn\u00eb kod, \u00ebsht\u00eb truri im q\u00eb shkruan kod\u00bb. Dhe truri mund t\u00eb shkruaj\u00eb kod ndaras nga ju? S\u00eb paku, ndoshta jo. <\/p>\n

Truri \u00ebsht\u00eb nj\u00eb makin\u00eb e jasht\u00ebzakonshme, ne as 10% nuk e dim\u00eb se si funksionon, por nuk mund t\u00eb funksionoj\u00eb t\u00ebr\u00ebsisht ndaras nga sistemi q\u00eb \u00ebsht\u00eb organizmi yn\u00eb. Dhe kjo \u00ebsht\u00eb leht\u00eb e provueshme: hapni kutin\u00eb e kafk\u00ebs, nxirrni trurin jasht\u00eb, vendoseni p\u00ebrpara kompjuterit, le t\u00eb provoj\u00eb dikush t\u00eb shkruaj\u00eb di\u00e7ka t\u00eb thjesht\u00eb. \u201eHello, world\u201d n\u00eb Python, p\u00ebr shembull.<\/p>\n

N\u00ebse sistemi mund t\u00eb b\u00ebj\u00eb di\u00e7ka q\u00eb asnj\u00ebra nga pjes\u00ebt e tij ve\u00e7mas nuk mund ta b\u00ebj\u00eb, 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 at\u00ebher\u00eb \u00e7far\u00eb e p\u00ebrcakton? Ajo p\u00ebrcaktohet nga nd\u00ebrveprimi midis k\u00ebtyre pjes\u00ebve. Dhe p\u00ebr pasoj\u00eb, sa m\u00eb shum\u00eb pjes\u00eb ka, aq m\u00eb t\u00eb komplikuara jan\u00eb nd\u00ebrveprimet, aq m\u00eb e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb kuptojm\u00eb dhe parashikojm\u00eb sjelljen e sistemit. Kjo e b\u00ebn nj\u00eb sistem t\u00eb till\u00eb kaotik, sepse \u00e7do ndryshim edhe m\u00eb t\u00eb vog\u00ebl, q\u00eb nuk \u00ebsht\u00eb i duksh\u00ebm p\u00ebr syrin, n\u00eb ndonj\u00ebr\u00ebn nga pjes\u00ebt e sistemit mund t\u00eb sjell\u00eb rezultate krejt\u00ebsisht t\u00eb paparashikueshme. <\/p>\n

Kjo ndjeshm\u00ebri ndaj kushteve fillestare u zbulua dhe u studua p\u00ebr her\u00eb t\u00eb par\u00eb nga meteorologu amerikan Ed Lorenz. M\u00eb von\u00eb, ajo mori emrin \u201eefekti flutur\u201d dhe \u00e7oi n\u00eb zhvillimin e nj\u00eb l\u00ebvizjeje t\u00eb till\u00eb t\u00eb mendimit shkencor, e cila quhet \u201eteoria e kaosit\u201d. Kjo teori u b\u00eb nj\u00eb nga ndryshimet kryesore t\u00eb paradigmatike n\u00eb shkenc\u00eb t\u00eb shekullit t\u00eb 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 ndara komplekse dhe organizata t\u00eb m\u00ebdha nd\u00ebrkomb\u00ebtare, n\u00eb nj\u00eb moment kuptova se kjo \u00ebsht\u00eb ajo q\u00eb ndjej p\u00ebr veten time. Un\u00eb jam kaosolog. Kjo, n\u00eb thelb, \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb e zgjuar p\u00ebr t\u00eb th\u00ebn\u00eb: \u201eNuk e kuptoj se \u00e7far\u00eb ndodh k\u00ebtu dhe nuk e di se \u00e7far\u00eb t\u00eb b\u00ebj me k\u00ebt\u00eb.\u201d <\/p>\n

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

\u00c7far\u00eb \u00ebsht\u00eb adaptiviteti? Adaptiviteti do t\u00eb thot\u00eb se sjellja individuale dhe kolektive e pjes\u00ebve n\u00eb nj\u00eb sistem adaptiv ndryshon dhe auto-organizohet, duke reaguar ndaj ngjarjeve ose zinxhir\u00ebve t\u00eb mikro-ngjarjeve brenda sistemit. K\u00ebshtu, sistemi p\u00ebrshtatet me ndryshimet p\u00ebrmes auto-organizimit. Dhe kjo aft\u00ebsi p\u00ebr auto-organizim bazohet n\u00eb bashk\u00ebpunimin vullnetar, plot\u00ebsisht t\u00eb decentralizuar t\u00eb agjent\u00ebve autonom\u00eb t\u00eb lir\u00eb.<\/p>\n

Nj\u00eb tjet\u00ebr pron\u00eb interesante e till\u00eb e sistemeve \u00ebsht\u00eb se ato jan\u00eb t\u00eb shkall\u00ebzuara lirisht. \u00c7ka duhet t\u00eb na interesoj\u00eb si inxhinier\u00eb t\u00eb kaosit. Pra, n\u00ebse tham\u00eb se sjellja e nj\u00eb sistemi t\u00eb nd\u00ebrlikuar p\u00ebrcaktohet nga nd\u00ebrveprimi i pjes\u00ebve t\u00eb tij, \u00e7far\u00eb duhet t\u00eb na interesoj\u00eb? Nd\u00ebrveprimi. <\/p>\n

Ka dy p\u00ebrfundime t\u00eb tjera interesante.
\n \"DevOps
\n
\nS\u00eb pari, ne kuptojm\u00eb se nuk \u00ebsht\u00eb e mundur t\u00eb thjeshtohet nj\u00eb sistem t\u00eb nd\u00ebrlikuar duke e thjeshtuar pjes\u00ebt e tij. S\u00eb dyti, m\u00ebnyra e vetme p\u00ebr t\u00eb thjeshtuar nj\u00eb sistem t\u00eb nd\u00ebrlikuar \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 informacioni, i cili quhet shoq\u00ebria njer\u00ebzore. Ne nd\u00ebrveprojm\u00eb p\u00ebrmes nj\u00eb gjuhe t\u00eb p\u00ebrbashk\u00ebt, n\u00ebse e kemi, n\u00ebse e gjejm\u00eb at\u00eb.<\/p>\n

\"DevOps
\n
\nPor gjuha vet\u00eb \u00ebsht\u00eb nj\u00eb sistem adaptiv i nd\u00ebrlikuar. N\u00eb p\u00ebrputhje, p\u00ebr t\u00eb nd\u00ebrvepruar m\u00eb efektivisht dhe thjesht, ne kemi nevoj\u00eb p\u00ebr krijimin e disa protokollesh. Do t\u00eb thot\u00eb nj\u00eb s\u00ebr\u00eb simbolesh dhe veprimesh q\u00eb do ta b\u00ebjn\u00eb shk\u00ebmbimin e informacionit midis nesh m\u00eb t\u00eb leht\u00eb, m\u00eb t\u00eb parashikuesh\u00ebm, m\u00eb t\u00eb kuptuesh\u00ebm.<\/p>\n

Dua t\u00eb them se tendencat p\u00ebr nd\u00ebrlikim, adaptivitet, decentralizim, p\u00ebr kaosit jan\u00eb t\u00eb pranishme n\u00eb gjith\u00e7ka. Si n\u00eb sistemet q\u00eb ne nd\u00ebrtuam, ashtu edhe n\u00eb ato q\u00eb jemi pjes\u00eb.<\/p>\n

Dhe p\u00ebr t\u00eb mos u ndier\u00eb boshe, le t\u00eb shikojm\u00eb se si ndryshojn\u00eb ato sisteme q\u00eb ne i krijojm\u00eb.<\/p>\n

\"DevOps
\n
\nE prisni k\u00ebt\u00eb fjal\u00eb, e kuptoj. Ne jemi n\u00eb nj\u00eb konferenc\u00eb DevOps, sot kjo fjal\u00eb do t\u00eb p\u00ebrmendet diku rreth nj\u00ebqind mij\u00eb her\u00eb dhe pastaj do t\u00eb na vij\u00eb n\u00eb \u00ebndrrat tona nat\u00ebn.<\/p>\n

Mikrosh\u00ebrbimet jan\u00eb arkitektura e par\u00eb softuerike q\u00eb ka lindur si p\u00ebrgjigje ndaj praktikave DevOps, e cila ka p\u00ebr q\u00ebllim t\u00eb b\u00ebj\u00eb sistemet tona m\u00eb fleksibile, m\u00eb t\u00eb shkall\u00ebzueshme dhe t\u00eb siguroj\u00eb dor\u00ebzimin e vazhduesh\u00ebm. Si e arrin k\u00ebt\u00eb? Duke reduktuar v\u00ebllimin e sh\u00ebrbimeve, duke shkurtuar kufijt\u00eb e problemeve q\u00eb k\u00ebto sh\u00ebrbime trajtojn\u00eb dhe duke shkurtuar koh\u00ebn e dor\u00ebzimit. Pra, ne e zvog\u00eblojm\u00eb, e thjeshtojm\u00eb pjes\u00ebt e sistemit, rrisim numrin e tyre dhe, p\u00ebr pasoj\u00eb, rritet kompleksiteti i nd\u00ebrveprimeve midis k\u00ebtyre pjes\u00ebve, q\u00eb do t\u00eb thot\u00eb se lindin probleme t\u00eb reja q\u00eb duhet t'i zgjidhim.<\/p>\n

\"DevOps
\n
\nMikrosh\u00ebrbimet nuk jan\u00eb fundi, ato n\u00eb thelb jan\u00eb dje, sepse po vjen Serverless. T\u00eb gjitha server\u00ebt jan\u00eb djegur, nuk ka servera, nuk ka sisteme operative, vet\u00ebm kod ekzekutues i past\u00ebr. Konfigurimet ve\u00e7mas, gjendjet ve\u00e7mas, gjith\u00e7ka menaxhohet nga ngjarjet. Bukuri, past\u00ebrti, qet\u00ebsi, nuk ka ngjarje, nuk ndodh asgj\u00eb, \u00e7do gj\u00eb \u00ebsht\u00eb n\u00eb rregull. <\/p>\n

Ku \u00ebsht\u00eb kompleksiteti? Komplexiteti, si\u00e7 e din\u00eb t\u00eb gjith\u00eb, \u00ebsht\u00eb n\u00eb nd\u00ebrveprime. Sa mund t\u00eb b\u00ebj\u00eb nj\u00eb funksion vet\u00eb? Si nd\u00ebrvepron me funksionet e tjera? Radh\u00ebt e mesazheve, bazat e t\u00eb dh\u00ebnave, balancuesit. Si t\u00eb rikrijojm\u00eb nj\u00eb ngjarje kur ndodhi nj\u00eb d\u00ebshtim? Nj\u00eb mori pyetjesh dhe pak p\u00ebrgjigjesh.<\/p>\n

Mikrosh\u00ebrbimet dhe Serverless jan\u00eb gjith\u00e7ka q\u00eb ne, hipster\u00ebt e kompjuter\u00ebve, i quajm\u00eb Cloud Native. Kjo \u00ebsht\u00eb gjith\u00e7ka p\u00ebr re. Por reja n\u00eb thelb \u00ebsht\u00eb gjithashtu e kufizuar n\u00eb shkall\u00ebzim. Ne jemi m\u00ebsuar ta mendojm\u00eb si nj\u00eb sistem t\u00eb shp\u00ebrndar\u00eb. N\u00eb t\u00eb v\u00ebrtet\u00eb, ku Jetojn\u00eb server\u00ebt e ofruesve t\u00eb rejeve? N\u00eb qendrat e t\u00eb dh\u00ebnave. K\u00ebshtu q\u00eb kemi nj\u00eb model rrethor, shum\u00eb t\u00eb kufizuar dhe t\u00eb shp\u00ebrndar\u00eb.<\/p>\n

Sot ne kuptojm\u00eb q\u00eb interneti i gj\u00ebrave nuk \u00ebsht\u00eb m\u00eb vet\u00ebm fjal\u00eb t\u00eb z\u00ebshme p\u00ebr faktin se, 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 num\u00ebr t\u00eb madh t\u00eb dh\u00ebnash t\u00eb dobishme dhe t\u00eb padobishme, t\u00eb cilat do t\u00eb derdhen n\u00eb re dhe do t\u00eb iven nga re. <\/p>\n

Reja nuk do ta p\u00ebrballoj\u00eb, prandaj ne flasim gjithnj\u00eb e m\u00eb shum\u00eb p\u00ebr at\u00eb q\u00eb quhet \"p\u00ebrpunim periferik.\" Apo m\u00eb p\u00eblqen edhe nj\u00eb p\u00ebrkufizim tjet\u00ebr \"fog computing\". Ai \u00ebsht\u00eb i mbushur me misterin e romantizmit dhe enigmat.<\/p>\n

\"DevOps
\n
\nKompjuter\u00ebt e mjegull\u00ebs. B\u00ebhet fjal\u00eb p\u00ebr at\u00eb se si re jan\u00eb grumbuj t\u00eb centralizuar t\u00eb ujit, avullit, akullit, gur\u00ebve. Nd\u00ebrsa mjegulla \u00ebsht\u00eb pika uji q\u00eb jan\u00eb shp\u00ebrndara rreth nesh n\u00eb atmosfer\u00eb. <\/p>\n

N\u00eb paradigmen e mjegull\u00ebs, shumica e pun\u00ebs kryhet nga k\u00ebto pika n\u00eb m\u00ebnyr\u00eb krejt\u00ebsisht autonome ose n\u00eb bashk\u00ebpunim me pika t\u00eb tjera. Ato i drejtohen re, vet\u00ebm kur v\u00ebrtet kan\u00eb nevoj\u00eb. <\/p>\n

Pra, p\u00ebrs\u00ebri decentralizimi, autonomi, dhe sigurisht, shum\u00eb nga ju tashm\u00eb e kuptoni se n\u00eb \u00e7far\u00eb po shkon kjo, sepse nuk mund t\u00eb flas\u00ebsh p\u00ebr decentralizim dhe t\u00eb mos p\u00ebrmend\u00ebsh bllokad\u00ebn. <\/p>\n

\"DevOps
\n
\nKa ata q\u00eb besojn\u00eb, ata q\u00eb kan\u00eb investuar n\u00eb kriptovaluta. Ka ata q\u00eb besojn\u00eb, por kan\u00eb frik\u00eb, si p.sh. un\u00eb. Dhe ka ata q\u00eb nuk besojn\u00eb. Mund t\u00eb merremi me t\u00eb n\u00eb m\u00ebnyra t\u00eb ndryshme. Ka teknologji, nj\u00eb gj\u00eb t\u00eb re t\u00eb paqart\u00eb, dhe ka probleme. Si \u00e7do teknologji e re, ajo ngrit m\u00eb shum\u00eb pyetje sesa jep p\u00ebrgjigje. <\/p>\n

Haji rreth bllokad\u00ebs \u00ebsht\u00eb i kuptuesh\u00ebm. Edhe n\u00ebse e l\u00eb jasht\u00eb ethet e arit, vet\u00eb teknologjia ofron premtime t\u00eb shk\u00eblqyera p\u00ebr nj\u00eb t\u00eb ardhme t\u00eb ndritshme: m\u00eb shum\u00eb liri, m\u00eb shum\u00eb autonomi, besim global t\u00eb shp\u00ebrndar\u00eb. \u00c7far\u00eb nuk do t\u00eb d\u00ebshiroje? <\/p>\n

Si pasoj\u00eb, gjithnj\u00eb e m\u00eb shum\u00eb inxhinier\u00eb n\u00eb t\u00eb gjith\u00eb bot\u00ebn fillojn\u00eb t\u00eb zhvillojn\u00eb aplikacione t\u00eb decentralizuara. Dhe kjo \u00ebsht\u00eb nj\u00eb forc\u00eb nga e cila nuk mund t\u00eb ik\u00ebsh, thjesht duke th\u00ebn\u00eb: \"Eh, bllokada \u00ebsht\u00eb thjesht nj\u00eb baz\u00eb t\u00eb shp\u00ebrndar\u00eb e zbatuar keq.\" Ose si\u00e7 thon\u00eb skeptik\u00ebt: \"Nuk ka aplikacione reale p\u00ebr bllokad\u00ebn.\" N\u00ebse e mendoni, 150 vjet m\u00eb par\u00eb ata than\u00eb t\u00eb nj\u00ebjt\u00ebn gj\u00eb p\u00ebr elektricitetin. Dhe madje n\u00eb disa aspekte ishin t\u00eb drejta, sepse ajo q\u00eb elektriciteti b\u00ebn sot t\u00eb mundshme, n\u00eb shekullin e 19-t\u00eb ishte krejt\u00ebsisht e pamundur.<\/p>\n

A, kush e di se \u00e7far\u00eb logoje \u00ebsht\u00eb n\u00eb ekran? Kjo \u00ebsht\u00eb Hyperledger. Ky \u00ebsht\u00eb nj\u00eb projekt q\u00eb zhvillohet n\u00ebn mbik\u00ebqyrjen e The Linux Foundation, ai p\u00ebrfshin nj\u00eb grup teknologjish bllokade. Kjo \u00ebsht\u00eb n\u00eb t\u00eb v\u00ebrtet\u00eb nj\u00eb forc\u00eb 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 kompleks, gjithnj\u00eb e m\u00eb kaotik, gjithnj\u00eb e m\u00eb adaptiv. Netflix \u2013 pionier\u00ebt e sistemeve mikros\u00ebrvikuese. Ata ishin nga t\u00eb par\u00ebt q\u00eb e kuptuan k\u00ebt\u00eb, ata zhvilluan nj\u00eb grup mjetesh q\u00eb e quajt\u00ebn Simian Army, mjeti m\u00eb i njohur prej t\u00eb cil\u00ebve u b\u00eb Chaos Monkey<\/a><\/noindex>. Ai p\u00ebrcaktoi at\u00eb q\u00eb u b\u00eb e njohur si \u00abparimet e inxhinieris\u00eb s\u00eb kaosit\u00bb<\/a><\/noindex>.<\/p>\n

N\u00eb fakt, gjat\u00eb pun\u00ebs mbi raportin, ne madje p\u00ebrkthyem k\u00ebt\u00eb tekst n\u00eb gjuh\u00ebn ruse, k\u00ebshtu q\u00eb vizitoni lidhjen<\/a><\/noindex>, lexoni, komentoni, kritikoni.<\/p>\n

N\u00eb p\u00ebrmbledhje, parimet e inxhinieris\u00eb s\u00eb kaosit flasin p\u00ebr k\u00ebt\u00eb. Sistemet e ndara t\u00eb shp\u00ebrndara jan\u00eb natyrsh\u00ebm t\u00eb paparashikueshme dhe n\u00eb thelb p\u00ebrmbajn\u00eb gabime. Gabimet jan\u00eb t\u00eb pashmangshme, q\u00eb 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 ndryshe. <\/p>\n

Ne duhet t\u00eb p\u00ebrpiqemi t\u00eb krijojm\u00eb vet\u00eb k\u00ebto gabime n\u00eb sistemet tona t\u00eb prodhimit, p\u00ebr t'i testuar ato p\u00ebr adaptivitetin e tyre, aft\u00ebsin\u00eb p\u00ebr vet\u00eb-organizim, p\u00ebr mbijetes\u00eb. <\/p>\n

Dhe kjo ndryshon gjith\u00e7ka. Jo vet\u00ebm si i nxjerrim sistemet n\u00eb prodhim, por edhe si i zhvillojm\u00eb, si i testojm\u00eb ato. Nuk ka asnj\u00eb proces stabilizimi, as kod t\u00eb ngrir\u00eb, p\u00ebrkundrazi, ka nj\u00eb proces t\u00eb vazhduesh\u00ebm t\u00eb destabilizimit. Ne p\u00ebrpiqemi t\u00eb vrasim sistemin dhe t\u00eb shohim se si ai vazhdon t\u00eb mbijetoj\u00eb.<\/p>\n

Protokollet e Integrimit t\u00eb Sistemeve t\u00eb Shp\u00ebrndara<\/b><\/h3>\n

\n\"DevOps
\n
\nPrandaj, kjo k\u00ebrkon nga sistemet tona q\u00eb ato t\u00eb ndryshohen gjithashtu. Q\u00eb t\u00eb b\u00ebhen m\u00eb t\u00eb q\u00ebndrueshme, ata kan\u00eb nevoj\u00eb p\u00ebr disa protokolle t\u00eb reja bashk\u00ebpunimi midis 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 t\u00eb caktuar. Dhe lindin lloje t\u00eb ndryshme t\u00eb reja t\u00eb mjeteve, protokolleve t\u00eb reja, t\u00eb cilat un\u00eb i quaj protokolle t\u00eb bashk\u00ebpunimit t\u00eb sistemeve t\u00eb shp\u00ebrndara.<\/p>\n

\"DevOps
\n
\n\u00c7far\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 p\u00ebr ndjekjen e shp\u00ebrndar\u00eb, i cili \u00ebsht\u00eb nj\u00eb mjet krejt i domosdosh\u00ebm p\u00ebr debimin e sistemeve t\u00eb ndara t\u00eb komplikuara.<\/p>\n

\"DevOps
\n
\nTjet\u00ebr \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, prandaj \u00ebsht\u00eb e nevojshme t\u00eb rrisim observabilitetin e tij. Opentracing i p\u00ebrket grupit t\u00eb mjeteve q\u00eb ofrojn\u00eb observabilitetin e sistemeve tona. Por observabiliteti na nevojitet p\u00ebr t\u00eb p\u00ebrcaktuar n\u00ebse sistemi sillet ashtu si\u00e7 e presim ne apo jo. Si mund ta p\u00ebrcaktojm\u00eb sjelljen e pritur? Duke p\u00ebrcaktuar nj\u00eb politik\u00eb t\u00eb till\u00eb, nj\u00eb grup rregullash. Projekti Open Policy Agent merret me p\u00ebrcaktimin e k\u00ebtij grupi rregullash n\u00eb nj\u00eb gam\u00eb t\u00eb gjer\u00eb: nga qasja deri te shp\u00ebrndarja e burimeve.<\/p>\n

\"DevOps
\n
\nSi\u00e7 e tham\u00eb, sistemet tona jan\u00eb gjithnj\u00eb e m\u00eb t\u00eb menaxhuara nga ngjarjet. Serverless \u00ebsht\u00eb nj\u00eb shembull i shk\u00eblqyer i sistemeve t\u00eb menaxhuara nga ngjarjet. Q\u00eb t\u00eb mund t\u00eb transferojm\u00eb ngjarje midis sistemeve dhe t'i ndjekim ato, na nevojitet nj\u00eb gjuh\u00eb e p\u00ebrbashk\u00ebt, nj\u00eb protokoll i p\u00ebrbashk\u00ebt p\u00ebr at\u00eb se si flasim p\u00ebr ngjarjet, si i komunikojm\u00eb ato midis nesh. K\u00ebtu merret me k\u00ebt\u00eb projekti i quajtur Cloudevents<\/a><\/noindex>.<\/p>\n

\"DevOps
\n
\nNj\u00eb rrjedh\u00eb e vazhdueshme ndryshimesh, e cila p\u00ebrshkon sistemet tona duke i destabilizuar vazhdimisht, \u00ebsht\u00eb nj\u00eb rrjedh\u00eb e vazhdueshme e artefakteve software. Q\u00eb t\u00eb mund t\u00eb mbajm\u00eb k\u00ebt\u00eb rrjedh\u00eb t\u00eb vazhdueshme ndryshimesh, na nevojitet nj\u00eb protokoll i p\u00ebrbashk\u00ebt, me an\u00eb t\u00eb t\u00eb cilit do t\u00eb mund t\u00eb flasim p\u00ebr at\u00eb se \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb artefakt software, si \u00ebsht\u00eb verifikuar, \u00e7far\u00eb verifikimi ka kaluar. K\u00ebtu merret me k\u00ebt\u00eb projekti i quajtur Grafeas<\/a><\/noindex>. Pra, nj\u00eb protokoll i p\u00ebrbashk\u00ebt p\u00ebr metadata t\u00eb artefakteve software.<\/p>\n

\"DevOps
\n
\nDhe, p\u00ebrfundimisht, n\u00ebse duam q\u00eb sistemet tona t\u00eb jen\u00eb plot\u00ebsisht autonome, adaptuese, t\u00eb organizohen vet\u00eb, ne duhet t'u japim atyre t\u00eb drejt\u00ebn p\u00ebr autoidentifikim. Projekti i quajtur spiffe<\/a><\/noindex> pik\u00ebrisht me k\u00ebt\u00eb merret. Ky \u00ebsht\u00eb gjithashtu nj\u00eb projekt n\u00ebn ombrell\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, provimin ton\u00eb. T\u00eb gjitha jan\u00eb kod i hapur, testimi yn\u00eb, zbatimi yn\u00eb. Ato na tregojn\u00eb se n\u00eb \u00e7far\u00eb drejtimi po shkon teknologjia. <\/p>\n

Por DevOps kurr\u00eb nuk ka qen\u00eb fillimisht p\u00ebr teknologjin\u00eb, gjithnj\u00eb ka qen\u00eb p\u00ebr bashk\u00ebpunimin mes njer\u00ebzve. Prandaj, n\u00ebse duam q\u00eb sistemet q\u00eb po zhvillojm\u00eb t\u00eb ndryshojn\u00eb, at\u00ebher\u00eb ne duhet t\u00eb ndryshojm\u00eb. N\u00eb t\u00eb v\u00ebrtet\u00eb, ne po ndryshojm\u00eb, nuk kemi zgjidhje t\u00eb ve\u00e7ant\u00eb. <\/p>\n

\"DevOps
\n
\nKa nj\u00eb lib\u00ebr t\u00eb mrekulluesh\u00ebm lib\u00ebr<\/a><\/noindex> nga shkrimtarja britanike Rachael Botsman, n\u00eb t\u00eb cilin ajo shkruan p\u00ebr evolucionin e besimit n\u00ebp\u00ebr histori. Ajo thot\u00eb se fillimisht, n\u00eb shoq\u00ebrit\u00eb primitive, besimi ishte lokal, dometh\u00ebn\u00eb ne besonim vet\u00ebm te ata q\u00eb i njehja personalisht. <\/p>\n

M\u00eb pas kishte nj\u00eb periudh\u00eb t\u00eb gjat\u00eb - nj\u00eb koh\u00eb t\u00eb err\u00ebt, kur besimi ishte centralizuar, kur filluam t\u00eb besojm\u00eb te njer\u00ebz t\u00eb cil\u00ebt nuk i njihnim n\u00eb baz\u00eb t\u00eb p\u00ebrkat\u00ebsis\u00eb son\u00eb ndaj nj\u00eb institucioni shoq\u00ebror ose 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 i shp\u00ebrndar\u00eb dhe i decentralizuar, dhe mb\u00ebshtetet n\u00eb lirin\u00eb e rrjedhave t\u00eb informacionit, n\u00eb aksesin e informacionit. <\/p>\n

N\u00ebse mendoni thell\u00eb, ky akses i nj\u00ebjt\u00eb, i cili e b\u00ebn t\u00eb mundur k\u00ebt\u00eb besim, ne e realizojm\u00eb vet\u00eb. Kjo do t\u00eb thot\u00eb se m\u00ebnyra se si bashk\u00ebpunojm\u00eb dhe se si e b\u00ebjm\u00eb k\u00ebt\u00eb duhet t\u00eb ndryshoj\u00eb, sepse organizatat IT centralizuese dhe hierarkike t\u00eb vjetra nuk funksionojn\u00eb m\u00eb. Ato fillojn\u00eb t\u00eb zhduken. <\/p>\n

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

\nOrganizata ideale DevOps e s\u00eb ardhmes \u00ebsht\u00eb nj\u00eb sistem decentralizuar, adaptiv, i p\u00ebrb\u00ebr\u00eb nga ekipe autonome, secila e p\u00ebrb\u00ebr\u00eb nga individ\u00eb autonom\u00eb. K\u00ebto ekipe jan\u00eb t\u00eb shp\u00ebrndara n\u00eb gjith\u00eb bot\u00ebn, ato bashk\u00ebpunojn\u00eb efektivisht me nj\u00ebra-tjetr\u00ebn p\u00ebrmes komunikimit asinkron, p\u00ebrmes protokolleve t\u00eb informacionit shum\u00eb t\u00eb qarta. Shum\u00eb bukur, apo jo? Nj\u00eb t\u00eb ardhme shum\u00eb e bukur.<\/p>\n

Sigurisht, kjo \u00ebsht\u00eb e pamundur pa ndryshime kulturore. Duhet t\u00eb kemi udh\u00ebheqje transformative, p\u00ebrgjegj\u00ebsi personale, motivim t\u00eb brendsh\u00ebm.<\/p>\n

\"DevOps
\n
\nKjo \u00ebsht\u00eb baza e organizatave DevOps: transparenca e informacionit, komunikimi asinkron, udh\u00ebheqja transformative, decentralizimi. <\/p>\n

Shterimi<\/b><\/h3>\n

\nSistemet e cilave jemi pjes\u00eb, dhe ato q\u00eb nd\u00ebrtuam, jan\u00eb gjithnj\u00eb e m\u00eb kaotike, dhe ne, njer\u00ebzit, e kemi t\u00eb v\u00ebshtir\u00eb t\u00eb p\u00ebrballojm\u00eb k\u00ebt\u00eb mendim, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb heqim dor\u00eb nga iluzioni i kontrollit. P\u00ebrpiqemi t\u00eb vazhdojm\u00eb t'i kontrollojm\u00eb ato, dhe kjo shpesh \u00e7on n\u00eb shterim. Po e them k\u00ebt\u00eb nga p\u00ebrvoja ime, gjithashtu kam p\u00ebsuar, gjithashtu jam invalid i defekteve t\u00eb papritura n\u00eb prodhim.<\/p>\n

\"DevOps
\n
\nShterimi ndodh kur p\u00ebrpiqemi t\u00eb kontrollojm\u00eb at\u00eb q\u00eb n\u00eb thelb nuk mund t\u00eb kontrollohet. Kur \u2018shterim\u2019, gjith\u00e7ka humbet kuptimin, sepse humbasim d\u00ebshir\u00ebn p\u00ebr t\u00eb b\u00ebr\u00eb di\u00e7ka t\u00eb re, ne kalojm\u00eb n\u00eb nj\u00eb pozita mbrojt\u00ebse dhe fillojm\u00eb t\u00eb mbrojm\u00eb at\u00eb q\u00eb kemi. <\/p>\n

Profesioni i inxhinieris\u00eb, si\u00e7 m\u00eb p\u00eblqen t\u00eb kujtoj shpesh, \u00ebsht\u00eb kryesisht nj\u00eb profesion krijues. N\u00ebse humbasim d\u00ebshir\u00ebn p\u00ebr t\u00eb krijuar di\u00e7ka, ne kthehemi n\u00eb hir, kthehemi n\u00eb hiri. Njer\u00ebzit shterin, organizatat shterin.<\/p>\n

Mendoj se vet\u00ebm pranuar fuqin\u00eb krijuese t\u00eb kaosit, vet\u00ebm nd\u00ebrtimi i bashk\u00ebpunimit sipas parimeve t\u00eb tij \u2013 \u00ebsht\u00eb ajo q\u00eb do t\u00eb na ndihmoj\u00eb t\u00eb mos humbasim at\u00eb t\u00eb mir\u00eb q\u00eb kemi n\u00eb profesionin ton\u00eb. <\/p>\n

K\u00ebshtu q\u00eb ju uroj: t\u00eb doni pun\u00ebn tuaj, t\u00eb doni at\u00eb q\u00eb b\u00ebjm\u00eb. Ky bot\u00eb ushqehet me informacione, na u dha nderi ta ushqejm\u00eb at\u00eb. Pra, le t\u00eb studiojm\u00eb kaosin, t\u00eb b\u00ebhemi kaolog\u00eb, t\u00eb sjellim vler\u00eb, t\u00eb krijojm\u00eb di\u00e7ka t\u00eb re, nd\u00ebrkoh\u00eb q\u00eb problemet, si\u00e7 e kemi kuptuar, jan\u00eb t\u00eb pashmangshme dhe kur t\u00eb shfaqen, ne do t\u00eb themi thjesht \"Ops!\", dhe problemi do t\u00eb zgjidhet. <\/p>\n

\u00c7far\u00eb tjet\u00ebr p\u00ebrve\u00e7 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 k\u00ebto parime, dhe mos u p\u00ebrpiqni t\u00eb k\u00ebrkoni mjete t\u00eb tjera q\u00eb dikush tjet\u00ebr i nd construit. <\/p>\n

Provo t\u00eb kuptosh se si sistemet tua thyejn\u00eb dhe fillo t'i thyesh dhe shiko se si duruan goditjet. Kjo \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja. Mjetet mund t\u00eb k\u00ebrkohen. Ka projekte t\u00eb ndryshme. <\/p>\n

Nuk e kuptova plot\u00ebsisht momentin kur po flisnit p\u00ebr at\u00eb q\u00eb sistemi nuk mund t\u00eb thjeshtohet duke e thjeshtuar komponent\u00ebt e tij, dhe menj\u00ebher\u00eb kaluat n\u00eb mikrosh\u00ebrbime, t\u00eb cilat pik\u00ebrisht thjeshtojn\u00eb sistemin duke e thjeshtuar vet\u00eb komponent\u00ebt dhe duke e komplikuar nd\u00ebrveprimin. Kjo n\u00eb thelb jan\u00eb dy pjes\u00eb q\u00eb bien ndesh me nj\u00ebra-tjetr\u00ebn. <\/b><\/p>\n

Plot\u00ebsisht e sakt\u00eb, mikrosh\u00ebrbimet jan\u00eb nj\u00eb tem\u00eb shum\u00eb e diskutueshme. 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 sigurisht q\u00eb nuk na japin thjesht\u00ebsi. Rrisin kompleksitetin.<\/p>\n

Pra, n\u00eb filozofin\u00eb DevOps, mikrosh\u00ebrbimet nuk jan\u00eb nj\u00eb bekim kaq t\u00eb madh?<\/b><\/p>\n

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

Megjithat\u00eb, \u00e7far\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishme: thjeshtimi i nd\u00ebrveprimit apo thjeshtimi i pjes\u00ebve?<\/b> <\/p>\n

Fokusimi \u00ebsht\u00eb padyshim n\u00eb thjeshtimin e interaksioneve, sepse n\u00ebse e shohim k\u00ebt\u00eb nga k\u00ebndv\u00ebshtrimi i m\u00ebnyr\u00ebs si ne punojm\u00eb, n\u00eb radh\u00eb t\u00eb par\u00eb duhet t\u00eb p\u00ebrqendrohemi n\u00eb thjeshtimin e interaksioneve, dhe jo n\u00eb thjeshtimin e pun\u00ebs s\u00eb secilit prej nesh ve\u00e7 e ve\u00e7. Sepse thjeshtimi i pun\u00ebs do t\u00eb thot\u00eb t\u00eb kthehemi n\u00eb robot\u00eb. Kjo funksionon mir\u00eb n\u00eb McDonald's, kur t\u00eb \u00ebsht\u00eb caktuar: vendos hamburgerin k\u00ebtu, derdh sosin mbi t\u00eb k\u00ebtu. Kjo nuk funksionon aspak n\u00eb pun\u00ebn ton\u00eb kreative.<\/p>\n

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

Kjo varet nga cili lloj konkurence po flasim. A \u00ebsht\u00eb konkurenca n\u00eb vendin e pun\u00ebs apo konkurrenca midis kompanive? <\/p>\n

Mbi konkurrenc\u00ebn e sh\u00ebrbimeve q\u00eb ekzistojn\u00eb, sepse sh\u00ebrbimet nuk jan\u00eb disa kompani. Ne po krijojm\u00eb nj\u00eb tip t\u00eb ri t\u00eb ambientit informativ, dhe \u00e7do ambient nuk mund t\u00eb jetoj\u00eb pa konkurrenc\u00eb. Ka konkurrenc\u00eb kudo.<\/b><\/p>\n

T\u00eb nj\u00ebjt\u00ebt Netflix, i marrim ata si nj\u00eb model rol. Pse e shpiku kjo? Sepse ata kishin nevoj\u00eb t\u00eb ishin konkurrues. Kjo fleksibilitet dhe shpejt\u00ebsi n\u00eb veprim jan\u00eb k\u00ebrkesa t\u00eb v\u00ebrteta konkurruese, ato sjellin 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 di\u00e7ka q\u00eb lind nga k\u00ebrkesat e bot\u00ebs. Ne thjesht duam t\u00eb p\u00ebrshtatemi. Dhe kaosi \u00ebsht\u00eb nga ana tjet\u00ebr, rezultati i konkurrenc\u00ebs.<\/p>\n

Kjo do t\u00eb thot\u00eb, a \u00ebsht\u00eb kaosi munges\u00eb q\u00ebllimesh ndoshta? Ose ato q\u00ebllime q\u00eb nuk duam t'i shohim? Ne jemi n\u00eb nj\u00eb kuti dhe nuk e kuptojm\u00eb q\u00ebllimet e t\u00eb tjer\u00ebve. Konkurrenca, n\u00eb t\u00eb v\u00ebrtet\u00eb, \u00ebsht\u00eb p\u00ebr shkak se kemi q\u00ebllime t\u00eb qarta dhe e dim\u00eb se ku do t\u00eb shkojm\u00eb n\u00eb \u00e7do moment tjet\u00ebr. N\u00eb k\u00ebt\u00eb pik\u00ebpamje, kjo \u00ebsht\u00eb thelbi i DevOps.<\/b><\/p>\n

Nj\u00eb tjet\u00ebr k\u00ebndv\u00ebshtrim mbi k\u00ebt\u00eb \u00e7\u00ebshtje. Mendoj se q\u00ebllimi yn\u00eb \u00ebsht\u00eb nj\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 ashtu. Mbijetesa ndodhi shpesh n\u00eb nj\u00eb gar\u00eb konkurruese, k\u00ebtu nuk mund t\u00eb b\u00ebjm\u00eb gj\u00eb tjet\u00ebr.<\/p>\n

T\u00eb k\u00ebtij viti konferenca DevOpsDays Moscow<\/a><\/noindex> do t\u00eb mbahet m\u00eb 7 dhjetor n\u00eb \"Teknopolis\". 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: shp\u00ebrndarja e softuerit n\u00eb nj\u00eb bot\u00eb t\u00eb decentralizuar | ProHoster","description":"Krijuesi dhe drejtor i \u00abOtomato Software\u00bb, nj\u00eb nga iniciator\u00ebt dhe instruktor\u00ebt e certifikimit t\u00eb par\u00eb DevOps n\u00eb Izrael, Anton Vajs tregoi n\u00eb 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}]}}