{"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\/cs\/blog\/administrirovanie\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire","title":{"rendered":"DevOps a Chaos: doru\u010dov\u00e1n\u00ed softwaru ve decentralizovan\u00e9m sv\u011bt\u011b.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Zakladatel a \u0159editel \u201eOtomato Software\u201c, jeden z inici\u00e1tor\u016f a instrukt\u016fr\u016f prvn\u00ed DevOps certifikace v Izraeli, Anton Weiss, hovo\u0159il na lo\u0148sk\u00e9m DevOpsDays Moskva<\/a><\/noindex> o teorii chaosu a hlavn\u00edch principech chaosov\u00e9 in\u017een\u00fdrstv\u00ed a tak\u00e9 vysv\u011btlil, jak by m\u011bla vypadat ide\u00e1ln\u00ed DevOps organizace budoucnosti.<\/p>\n

P\u0159ipravili jsme textovou verzi prezentace. <\/p>\n

\r\n \"P\u0159ehr\u00e1t\r\n
<\/div>\r\n <\/div><\/center>
\n<\/a><\/noindex>
\nDobr\u00e9 r\u00e1no! <\/p>\n

DevOpsDays v Moskv\u011b podruh\u00e9 v \u0159ad\u011b, j\u00e1 podruh\u00e9 na tomto p\u00f3diu, mnoz\u00ed z v\u00e1s podruh\u00e9 v t\u00e9to m\u00edstnosti. Co to znamen\u00e1? To znamen\u00e1, \u017ee DevOps hnut\u00ed v Rusku roste, mno\u017e\u00ed se a hlavn\u011b, to znamen\u00e1, \u017ee p\u0159i\u0161el \u010das hovo\u0159it o tom, co vlastn\u011b znamen\u00e1 DevOps v roce 2018. <\/p>\n

Zvedn\u011bte ruku ti, kte\u0159\u00ed si mysl\u00ed, \u017ee v roce 2018 je DevOps u\u017e profes\u00ed? Jsou tu takov\u00ed. Jsou v m\u00edstnosti DevOps in\u017een\u00fd\u0159i, kte\u0159\u00ed maj\u00ed v popisu pracovn\u00ed pozice naps\u00e1no \u201eDevOps in\u017een\u00fdr\u201c? Jsou v m\u00edstnosti DevOps mana\u017ee\u0159i? Takov\u00ed nejsou. DevOps architekti? Taky ne. M\u00e1lo. Co, opravdu nikdo nem\u00e1 naps\u00e1no, \u017ee je DevOps in\u017een\u00fdr?<\/p>\n

To znamen\u00e1, \u017ee v\u011bt\u0161ina z v\u00e1s si mysl\u00ed, \u017ee je to antipattern? \u017de takov\u00e1 profese by nem\u011bla existovat? M\u016f\u017eeme si myslet, co chceme, a zat\u00edmco p\u0159em\u00fd\u0161l\u00edme, pr\u016fmysl slavnostn\u011b postupuje vp\u0159ed za zvuk\u016f DevOps trumpety.<\/p>\n

Kdo sly\u0161el o nov\u00e9m t\u00e9matu, kter\u00e9 se naz\u00fdv\u00e1 DevDevOps? Je to takov\u00e1 nov\u00e1 metodika, kter\u00e1 umo\u017e\u0148uje efektivn\u00ed spolupr\u00e1ci mezi v\u00fdvoj\u00e1\u0159i a DevOps t\u00fdmy. P\u0159itom to nen\u00ed n\u011bco \u00fapln\u011b nov\u00e9ho. Sud\u011b podle Twitteru, o tom u\u017e za\u010dali mluvit p\u0159ed 4 lety. A z\u00e1jem o to st\u00e1le roste, co\u017e znamen\u00e1, \u017ee probl\u00e9m existuje. Tento probl\u00e9m je t\u0159eba vy\u0159e\u0161it.<\/p>\n

\"DevOps
\n
\nJsme kreativn\u00ed lid\u00e9, tak snadno se neuklidn\u00edme. \u0158\u00edk\u00e1me, \u017ee DevOps je p\u0159\u00edli\u0161 obecn\u00e9 slovo, chyb\u00ed v n\u011bm r\u016fzn\u00e9 zaj\u00edmav\u00e9 prvky. A jdeme do na\u0161ich tajn\u00fdch laborato\u0159\u00ed a za\u010d\u00edn\u00e1me plodit zv\u011bdav\u00e9 mutace: DevTestOps, GitOps, DevSecOps, BizDevOps, ProdOps.<\/p>\n

\"DevOps
\n
\nLogika je jasn\u00e1, \u017ee? Na\u0161e dodac\u00ed syst\u00e9m nen\u00ed funk\u010dn\u00ed, na\u0161e syst\u00e9my jsou nestabiln\u00ed a u\u017eivatel\u00e9 nespokojen\u00ed, nest\u00edh\u00e1me vyd\u00e1vat software v\u010das, nepohybujeme se v rozpo\u010dtu. Jak to v\u0161echno vy\u0159e\u0161\u00edme? Vymysl\u00edme nov\u00e9 slovo! Bude kon\u010dit na \u201eOps\u201c, a probl\u00e9m je vy\u0159e\u0161en.<\/p>\n

Tak tento p\u0159\u00edstup naz\u00fdv\u00e1m \u2014 \u201eOps, a probl\u00e9m je vy\u0159e\u0161en\u201c.<\/p>\n

Tohle v\u0161echno ustupuje do pozad\u00ed, pokud si p\u0159ipom\u00edn\u00e1me, pro\u010d jsme to v\u0161echno vymysleli. Vymysleli jsme cel\u00fd tento DevOps, abychom u\u010dinili doru\u010dov\u00e1n\u00ed software a na\u0161i pr\u00e1ci v tomto procesu co nejv\u00edce bezprobl\u00e9movou, bezbolestnou, efektivn\u00ed a, hlavn\u011b, p\u0159\u00edjemnou. <\/p>\n

DevOps vyrostl z bolesti. A m\u00e1me dost utrpen\u00ed. Abychom to v\u0161echno zvl\u00e1dli, zakl\u00e1d\u00e1me se na udr\u017eiteln\u00fdch praktik\u00e1ch: efektivn\u00ed spolupr\u00e1ce, praktiky toku a p\u0159edev\u0161\u00edm syst\u00e9mov\u00e9 my\u0161len\u00ed, proto\u017ee bez n\u011bj \u017e\u00e1dn\u00fd DevOps nefunguje.<\/p>\n

Co je to syst\u00e9m?<\/b><\/h3>\n

\nA pokud u\u017e mluv\u00edme o syst\u00e9mov\u00e9m my\u0161len\u00ed, p\u0159ipome\u0148me si, co je to syst\u00e9m.<\/p>\n

\"DevOps
\n
\nPokud jste hacker-revolucion\u00e1\u0159, pak je pro v\u00e1s syst\u00e9m jednozna\u010dn\u00e9 zlo. Je to mrak, kter\u00fd se nad v\u00e1mi vzn\u00e1\u0161\u00ed a nut\u00ed v\u00e1s d\u011blat v\u011bci, kter\u00e9 d\u011blat nechcete. <\/p>\n

\"DevOps
\n
\nZ pohledu syst\u00e9mov\u00e9ho my\u0161len\u00ed je syst\u00e9m celkem, kter\u00fd se skl\u00e1d\u00e1 z \u010d\u00e1st\u00ed. V tomto smyslu jsme ka\u017ed\u00fd z n\u00e1s syst\u00e9m. Organizace, ve kter\u00fdch pracujeme, jsou syst\u00e9my. A to, co budujeme, se naz\u00fdv\u00e1 syst\u00e9m.<\/p>\n

To v\u0161echno je sou\u010d\u00e1st\u00ed jedn\u00e9 velk\u00e9 sociotechnologick\u00e9 soustavy. A pouze pokud pochop\u00edme, jak tato sociotechnologick\u00e1 soustava spolupracuje, budeme schopni skute\u010dn\u011b n\u011bco optimalizovat. <\/p>\n

Z pohledu syst\u00e9mov\u00e9ho my\u0161len\u00ed m\u00e1 syst\u00e9m r\u016fzn\u00e1 zaj\u00edmav\u00e1 vlastnosti. Za prv\u00e9, skl\u00e1d\u00e1 se z \u010d\u00e1st\u00ed, co\u017e znamen\u00e1, \u017ee jeho chov\u00e1n\u00ed z\u00e1vis\u00ed na chov\u00e1n\u00ed jednotliv\u00fdch \u010d\u00e1st\u00ed. A v\u0161echny jeho \u010d\u00e1sti jsou tak\u00e9 vz\u00e1jemn\u011b z\u00e1visl\u00e9. To znamen\u00e1, \u017ee \u010d\u00edm v\u00edce \u010d\u00e1st\u00ed syst\u00e9m m\u00e1, t\u00edm slo\u017eit\u011bj\u0161\u00ed je pochopit nebo p\u0159edpov\u011bd\u011bt jeho chov\u00e1n\u00ed. <\/p>\n

Z hlediska chov\u00e1n\u00ed existuje je\u0161t\u011b jeden zaj\u00edmav\u00fd fakt. Syst\u00e9m m\u016f\u017ee d\u011blat n\u011bco, co \u017e\u00e1dn\u00e1 z jeho jednotliv\u00fdch \u010d\u00e1st\u00ed nem\u016f\u017ee ud\u011blat. <\/p>\n

Jak \u0159\u00edkal doktor Russell Ackoff (jeden z zakladatel\u016f syst\u00e9mov\u00e9ho my\u0161len\u00ed), je to dost snadn\u00e9 dok\u00e1zat pomoc\u00ed my\u0161lenkov\u00e9ho experimentu. Nap\u0159\u00edklad, kdo v s\u00e1le um\u00ed ps\u00e1t k\u00f3d? Mnoho rukou, a to je norm\u00e1ln\u00ed, proto\u017ee je to jedna z hlavn\u00edch po\u017eadavk\u016f na na\u0161i profesi. Um\u00edte ps\u00e1t, a va\u0161e ruce odd\u011blen\u011b od v\u00e1s mohou ps\u00e1t k\u00f3d? Jsou lid\u00e9, kte\u0159\u00ed \u0159eknou: \u201eMoje ruce nep\u00ed\u0161\u00ed k\u00f3d, m\u016fj mozek p\u00ed\u0161e k\u00f3d\u201c. A m\u016f\u017ee mozek ps\u00e1t k\u00f3d odd\u011blen\u011b od v\u00e1s? No, pravd\u011bpodobn\u011b ne. <\/p>\n

Mozek je \u00fa\u017easn\u00fd stroj, o jeho\u017e fungov\u00e1n\u00ed nev\u00edme ani 10 %, ale nem\u016f\u017ee pracovat odd\u011blen\u011b od syst\u00e9mu, kter\u00fdm je n\u00e1\u0161 organismus. A to lze snadno dok\u00e1zat: otev\u0159ete si lebku, vyjm\u011bte z n\u00ed mozek, polo\u017ete ho p\u0159ed po\u010d\u00edta\u010d a a\u0165 se pokus\u00ed napsat n\u011bco jednoduch\u00e9ho. Nap\u0159\u00edklad \"Ahoj, sv\u011bte\" v Pythonu.<\/p>\n

Pokud syst\u00e9m dok\u00e1\u017ee vykonat n\u011bco, co \u017e\u00e1dn\u00e1 z jeho \u010d\u00e1st\u00ed samostatn\u011b ud\u011blat nem\u016f\u017ee, znamen\u00e1 to, \u017ee jeho chov\u00e1n\u00ed nen\u00ed ur\u010dov\u00e1no chov\u00e1n\u00edm jeho \u010d\u00e1st\u00ed. \u010c\u00edm je tedy ur\u010dov\u00e1no? Ur\u010duje ho interakce mezi t\u011bmito \u010d\u00e1stmi. A podle toho, \u010d\u00edm v\u00edce \u010d\u00e1st\u00ed, t\u00edm slo\u017eit\u011bj\u0161\u00ed interakce, t\u00edm slo\u017eit\u011bj\u0161\u00ed je pochopit a p\u0159edpov\u011bd\u011bt chov\u00e1n\u00ed syst\u00e9mu. A to d\u011bl\u00e1 takov\u00fd syst\u00e9m chaotick\u00fdm, proto\u017ee jak\u00e1koliv, i ta nejmen\u0161\u00ed, oku neviditeln\u00e1 zm\u011bna v jak\u00e9koliv \u010d\u00e1sti syst\u00e9mu m\u016f\u017ee v\u00e9st k naprosto nep\u0159edv\u00eddateln\u00fdm v\u00fdsledk\u016fm. <\/p>\n

Tato citlivost na po\u010d\u00e1te\u010dn\u00ed podm\u00ednky byla poprv\u00e9 objevena a zkoum\u00e1na americk\u00fdm meteorologem Edem Lorenzem. Pozd\u011bji byla nazv\u00e1na \"efekt mot\u00fdla\" a vedla k rozvoji takov\u00e9ho sm\u011bru v\u011bdeck\u00e9ho my\u0161len\u00ed, kter\u00fd se naz\u00fdv\u00e1 \"teorie chaosu\". Tato teorie se stala jedn\u00edm z hlavn\u00edch paradigmatick\u00fdch posun\u016f ve v\u011bd\u011b 20. stolet\u00ed.<\/p>\n

Teorie chaosu<\/b><\/h3>\n

\nLid\u00e9, kte\u0159\u00ed se zab\u00fdvaj\u00ed studiem chaosu, se naz\u00fdvaj\u00ed chaotologov\u00e9.<\/p>\n

\"DevOps
\n
\nSkute\u010dn\u00fdm d\u016fvodem t\u00e9to p\u0159edn\u00e1\u0161ky bylo to, \u017ee p\u0159i pr\u00e1ci se slo\u017eit\u00fdmi distribuovan\u00fdmi syst\u00e9my a velk\u00fdmi mezin\u00e1rodn\u00edmi organizacemi jsem si v ur\u010dit\u00e9m okam\u017eiku uv\u011bdomil, \u017ee to je to, \u010d\u00edm se c\u00edt\u00edm. Jsem chaotolog. To je v z\u00e1sad\u011b takov\u00fd d\u016fmysln\u00fd zp\u016fsob, jak \u0159\u00edct: \"Nerozum\u00edm tomu, co se zde d\u011bje, a nev\u00edm, co s t\u00edm d\u011blat.\" <\/p>\n

Mysl\u00edm, \u017ee se mnoz\u00ed z v\u00e1s \u010dasto c\u00edt\u00ed podobn\u011b, tak\u017ee tak\u00e9 jste chaotologov\u00e9. Zveme v\u00e1s do gildy chaotolog\u016f. Syst\u00e9my, kter\u00e9 budeme studovat, mil\u00ed kolegov\u00e9 chaotologov\u00e9, se naz\u00fdvaj\u00ed \"slo\u017een\u00e9 adaptivn\u00ed syst\u00e9my\". <\/p>\n

Co je to adaptabilita? Adaptabilita znamen\u00e1, \u017ee individu\u00e1ln\u00ed a kolektivn\u00ed chov\u00e1n\u00ed \u010d\u00e1st\u00ed v takov\u00e9m adaptivn\u00edm syst\u00e9mu se m\u011bn\u00ed a samoorganizuje jako reakce na ud\u00e1losti nebo \u0159et\u011bzce mikroevekt\u016f v syst\u00e9mu. To znamen\u00e1, \u017ee se syst\u00e9m p\u0159izp\u016fsobuje zm\u011bn\u00e1m prost\u0159ednictv\u00edm samoorganizace. A tato schopnost samoorganizace je zalo\u017eena na dobrovoln\u00e9, zcela decentralizovan\u00e9 spolupr\u00e1ci svobodn\u00fdch autonomn\u00edch agent\u016f.<\/p>\n

Dal\u0161\u00ed zaj\u00edmavou vlastnost\u00ed takov\u00fdch syst\u00e9m\u016f je, \u017ee jsou voln\u011b \u0161k\u00e1lovateln\u00e9. Co\u017e by n\u00e1s, jako in\u017een\u00fdry chaologie, m\u011blo ur\u010dit\u011b zaj\u00edmat. Tak\u017ee pokud jsme \u0159ekli, \u017ee chov\u00e1n\u00ed slo\u017eit\u00e9ho syst\u00e9mu je ur\u010dov\u00e1no interakc\u00ed jeho \u010d\u00e1st\u00ed, co n\u00e1s m\u00e1 zaj\u00edmat? Interakce. <\/p>\n

Existuj\u00ed je\u0161t\u011b dv\u011b zaj\u00edmav\u00e9 z\u00e1v\u011bry.
\n \"DevOps
\n
\nZa prv\u00e9, ch\u00e1peme, \u017ee slo\u017eit\u00fd syst\u00e9m nelze zjednodu\u0161it prost\u00fdm zjednodu\u0161en\u00edm jeho \u010d\u00e1st\u00ed. Za druh\u00e9, jedin\u00fd zp\u016fsob, jak zjednodu\u0161it slo\u017eit\u00fd syst\u00e9m, je prost\u0159ednictv\u00edm zjednodu\u0161en\u00ed interakc\u00ed mezi jeho \u010d\u00e1stmi. <\/p>\n

Jak spolu komunikujeme? V\u0161ichni jsme sou\u010d\u00e1st\u00ed velk\u00e9ho informa\u010dn\u00edho syst\u00e9mu, kter\u00fd se naz\u00fdv\u00e1 lidsk\u00e1 spole\u010dnost. Komunikujeme prost\u0159ednictv\u00edm spole\u010dn\u00e9ho jazyka, pokud ho m\u00e1me, pokud ho nach\u00e1z\u00edme.<\/p>\n

\"DevOps
\n
\nAle jazyk s\u00e1m o sob\u011b je slo\u017eit\u00fd adaptivn\u00ed syst\u00e9m. Proto, abychom mohli interagovat efektivn\u011bji a snadn\u011bji, pot\u0159ebujeme vytvo\u0159en\u00ed n\u011bjak\u00fdch protokol\u016f. Tedy n\u011bjak\u00e9 sekvence symbol\u016f a akc\u00ed, kter\u00e9 u\u010din\u00ed v\u00fdm\u011bnu informac\u00ed mezi n\u00e1mi jednodu\u0161\u0161\u00ed, p\u0159edv\u00eddateln\u011bj\u0161\u00ed a srozumiteln\u011bj\u0161\u00ed.<\/p>\n

Chci \u0159\u00edct, \u017ee tendence ke komplikov\u00e1n\u00ed, adaptabilit\u011b, decentralizaci a chaoti\u010dnosti jsou patrn\u00e9 ve v\u0161em. A v t\u011bch syst\u00e9mech, kter\u00e9 stav\u00edme, a v t\u011bch syst\u00e9mech, jejich\u017e sou\u010d\u00e1st\u00ed jsme.<\/p>\n

A abychom nebyli bez d\u016fkaz\u016f, pod\u00edvejme se na to, jak se m\u011bn\u00ed ty syst\u00e9my, kter\u00e9 vytv\u00e1\u0159\u00edme.<\/p>\n

\"DevOps
\n
\n\u010cekali jste na toto slovo, ch\u00e1pu to. Jsme na DevOps konferenci, dnes toto slovo zazn\u00ed n\u011bjak\u00fdch sto tis\u00edckr\u00e1t a pak se n\u00e1m bude zd\u00e1t v noci.<\/p>\n

Mikroslu\u017eby jsou prvn\u00ed softwarov\u00e1 architektura, kter\u00e1 vznikla jako reakce na praktiky DevOps, a jej\u00edm c\u00edlem je u\u010dinit na\u0161e syst\u00e9my flexibiln\u011bj\u0161\u00edmi, \u0161k\u00e1lovateln\u011bj\u0161\u00edmi a zajistit nep\u0159etr\u017eitou dod\u00e1vku. Jak to d\u011bl\u00e1? Sn\u00ed\u017een\u00edm objemu slu\u017eeb, omezen\u00edm rozsahu probl\u00e9m\u016f, kter\u00e9 tyto slu\u017eby zpracov\u00e1vaj\u00ed, a zkr\u00e1cen\u00edm doby dod\u00e1n\u00ed. To znamen\u00e1, \u017ee zmen\u0161ujeme a zjednodu\u0161ujeme \u010d\u00e1sti syst\u00e9mu, zvy\u0161ujeme jejich po\u010det, co\u017e nevyhnuteln\u011b zvy\u0161uje slo\u017eitost interakc\u00ed mezi t\u011bmito \u010d\u00e1stmi, tedy vznikaj\u00ed nov\u00e9 probl\u00e9my, kter\u00e9 mus\u00edme \u0159e\u0161it.<\/p>\n

\"DevOps
\n
\nMikroslu\u017eby nejsou konec, mikroslu\u017eby jsou vlastn\u011b u\u017e v\u010derej\u0161ek, proto\u017ee p\u0159ich\u00e1z\u00ed Serverless. V\u0161echny servery sho\u0159ely, nejsou servery, nejsou opera\u010dn\u00ed syst\u00e9my, jen \u010dist\u011b vykon\u00e1van\u00fd k\u00f3d. Konfigurace odd\u011blen\u011b, stavy odd\u011blen\u011b, v\u0161echno je \u0159\u00edzeno ud\u00e1lostmi. Kr\u00e1sa, \u010distota, ticho, \u017e\u00e1dn\u00e9 ud\u00e1losti, nic se ned\u011bje, naprost\u00fd klid. <\/p>\n

Kde je slo\u017eitost? Slo\u017eitost je pochopiteln\u011b ve vz\u00e1jemn\u00fdch interakc\u00edch. Kolik toho m\u016f\u017ee jedna funkce ud\u011blat sama o sob\u011b? Jak interaguje s ostatn\u00edmi funkcemi? Zpr\u00e1vy v front\u00e1ch, datab\u00e1ze, vyva\u017eova\u010de. Jak rekonstruovat n\u011bjakou ud\u00e1lost, kdy\u017e dojde k selh\u00e1n\u00ed? Spousta ot\u00e1zek a m\u00e1lo odpov\u011bd\u00ed.<\/p>\n

Mikroslu\u017eby a Serverless jsou v\u0161e, co my, po\u010d\u00edta\u010dov\u00ed hipste\u0159i, naz\u00fdv\u00e1me Cloud Native. V\u0161echno je to o cloudu. Ale cloud je z podstaty tak\u00e9 omezen\u011b \u0161k\u00e1lovateln\u00fd. Jsme zvykl\u00ed p\u0159em\u00fd\u0161let o n\u011bm jako o distribuovan\u00e9m syst\u00e9mu. Ve skute\u010dnosti, kde \u017eij\u00ed servery cloudov\u00fdch poskytovatel\u016f? V datacentrech. To znamen\u00e1, \u017ee zde m\u00e1me n\u011bjak\u00fd centralizovan\u00fd, velmi omezen\u00fd, distribuovan\u00fd model.<\/p>\n

Dnes ji\u017e ch\u00e1peme, \u017ee internet v\u011bc\u00ed nejsou jen pr\u00e1zdn\u00e1 slova o tom, \u017ee n\u00e1s podle skromn\u00fdch p\u0159edpov\u011bd\u00ed v p\u0159\u00ed\u0161t\u00edch p\u011bti a\u017e deseti letech \u010dekaj\u00ed miliardy za\u0159\u00edzen\u00ed p\u0159ipojen\u00fdch k internetu. Obrovsk\u00e9 mno\u017estv\u00ed u\u017eite\u010dn\u00fdch a neu\u017eite\u010dn\u00fdch dat, kter\u00e1 budou stahov\u00e1na do cloudu a odes\u00edl\u00e1na z cloudu. <\/p>\n

Cloud to neut\u00e1hne, a proto \u010d\u00edm d\u00e1l v\u00edce mluv\u00edme o tom, co se naz\u00fdv\u00e1 \u201eokrajov\u00e9 v\u00fdpo\u010dty\u201c. Nebo se mi l\u00edb\u00ed kr\u00e1sn\u00e1 definice \u201efog computing\u201c. Ta je zast\u0159en\u00e1 mystikou romantismu a z\u00e1hadnosti.<\/p>\n

\"DevOps
\n
\nZaml\u017een\u00e9 v\u00fdpo\u010dty. Jde o to, \u017ee oblaka jsou centralizovan\u00e9 shluky vody, p\u00e1ry, ledu a kamen\u016f. A mlha jsou kapky vody, kter\u00e9 jsou rozpt\u00fdleny kolem n\u00e1s v atmosf\u00e9\u0159e. <\/p>\n

V zaml\u017een\u00e9 paradigmatice v\u011bt\u0161inu pr\u00e1ce vykon\u00e1vaj\u00ed tyto kapky zcela autonomn\u011b nebo ve spolupr\u00e1ci s jin\u00fdmi kapkami. A obracej\u00ed se na oblaka pouze tehdy, kdy\u017e nastane skute\u010dn\u00e1 pot\u0159eba. <\/p>\n

To znamen\u00e1 op\u011bt decentralizaci, autonomii, a samoz\u0159ejm\u011b mnoz\u00ed z v\u00e1s ji\u017e rozum\u00ed, kam to v\u0161e sm\u011b\u0159uje, proto\u017ee nelze mluvit o decentralizaci a nezm\u00ednit blockchain. <\/p>\n

\"DevOps
\n
\nJsou ti, kte\u0159\u00ed v\u011b\u0159\u00ed, to jsou ti, kte\u0159\u00ed investovali do kryptom\u011bny. Jsou ti, kte\u0159\u00ed v\u011b\u0159\u00ed, ale boj\u00ed se, jako t\u0159eba j\u00e1. A jsou ti, kte\u0159\u00ed nev\u011b\u0159\u00ed. K tomu se d\u00e1 p\u0159istupovat r\u016fzn\u011b. Existuje technologie, nov\u00e1 nepochopen\u00e1 z\u00e1le\u017eitost, existuj\u00ed probl\u00e9my. Jako ka\u017ed\u00e1 nov\u00e1 technologie vyvol\u00e1v\u00e1 v\u00edce ot\u00e1zek, ne\u017e poskytuje odpov\u011bd\u00ed. <\/p>\n

Hype kolem blockchainu je jasn\u00fd. I kdy\u017e odlo\u017e\u00edme stranou zlatou hore\u010dku, samotn\u00e1 technologie slibuje \u00fa\u017easnou budoucnost: v\u00edce svobody, v\u00edce autonomie, rozpt\u00fdlen\u00e9 glob\u00e1ln\u00ed d\u016fv\u011bry. Co tu nen\u00ed cht\u00edt? <\/p>\n

Proto \u010d\u00edm d\u00e1l t\u00edm v\u00edce in\u017een\u00fdr\u016f po cel\u00e9m sv\u011bt\u011b za\u010d\u00edn\u00e1 vyv\u00edjet decentralizovan\u00e9 aplikace. A to je s\u00edla, kterou nelze jednodu\u0161e ignorovat slovy: \u201eAaa, blockchain je jen \u0161patn\u011b implementovan\u00e1 distribuovan\u00e1 datab\u00e1ze.\u201c Nebo jak skeptici r\u00e1di \u0159\u00edkaj\u00ed: \u201ePro blockchain neexistuj\u00ed \u017e\u00e1dn\u00e9 skute\u010dn\u00e9 aplikace.\u201c Kdy\u017e si to promysl\u00edme, p\u0159ed 150 lety \u0159\u00edkali to sam\u00e9 o elekt\u0159in\u011b. A v n\u011b\u010dem m\u011bli pravdu, proto\u017ee to, co elekt\u0159ina dnes umo\u017e\u0148uje, bylo v 19. stolet\u00ed naprosto nere\u00e1ln\u00e9.<\/p>\n

Mimochodem, kdo v\u00ed, co je za logo na obrazovce? To je Hyperledger. To je projekt vyv\u00edjen\u00fd pod z\u00e1\u0161titou The Linux Foundation, zahrnuje soubor blockchainov\u00fdch technologi\u00ed. To je skute\u010dn\u00e1 s\u00edla na\u0161\u00ed komunity otev\u0159en\u00e9ho k\u00f3du.<\/p>\n

Chaosov\u00e9 in\u017een\u00fdrstv\u00ed<\/b><\/h3>\n

\n\"DevOps
\n
\nTak\u017ee syst\u00e9m, kter\u00fd vyv\u00edj\u00edme, se st\u00e1v\u00e1 \u010d\u00edm d\u00e1l slo\u017eit\u011bj\u0161\u00edm, chaoti\u010dt\u011bj\u0161\u00edm a adaptivn\u011bj\u0161\u00edm. Netflix je pr\u016fkopn\u00edkem mikroservisn\u00edch syst\u00e9m\u016f. Byli jedni z prvn\u00edch, kdo to pochopili, vyvinuli sadu n\u00e1stroj\u016f, kter\u00e9 nazvali Simian Army, z nich\u017e nejzn\u00e1m\u011bj\u0161\u00ed je Chaos Monkey<\/a><\/noindex>. Definoval to, co se stalo zn\u00e1m\u00fdm jako \u201eprincipy chaotick\u00e9ho in\u017een\u00fdrstv\u00ed\u201c<\/a><\/noindex>.<\/p>\n

Mimochodem, p\u0159i pr\u00e1ci na t\u00e9to prezentaci jsme tento text tak\u00e9 p\u0159elo\u017eili do ru\u0161tiny, tak se pod\u00edvejte na odkaz<\/a><\/noindex>, \u010dt\u011bte, komentujte, kritizujte.<\/p>\n

Stru\u010dn\u011b \u0159e\u010deno, principy chaotick\u00e9ho in\u017een\u00fdrstv\u00ed \u0159\u00edkaj\u00ed n\u00e1sleduj\u00edc\u00ed. Slo\u017eit\u00e9 distribuovan\u00e9 syst\u00e9my jsou v z\u00e1sad\u011b nep\u0159edv\u00eddateln\u00e9 a v nich jsou inherentn\u011b chyby. Chyby jsou nevyhnuteln\u00e9, co\u017e znamen\u00e1, \u017ee je mus\u00edme p\u0159ijmout a pracovat s t\u011bmito syst\u00e9my zcela jinak. <\/p>\n

Mus\u00edme se sami sna\u017eit vn\u00e1\u0161et tyto chyby do na\u0161ich produk\u010dn\u00edch syst\u00e9m\u016f, abychom testovali na\u0161e syst\u00e9my na tuto adaptabilitu, na tuto schopnost samoorganizace, na p\u0159e\u017eit\u00ed. <\/p>\n

A to m\u011bn\u00ed v\u0161echno. Nejen to, jak spou\u0161t\u00edme syst\u00e9m v produkci, ale tak\u00e9 jak je vyv\u00edj\u00edme, jak je testujeme. Neexistuje \u017e\u00e1dn\u00fd proces stabilizace, zamrznut\u00ed k\u00f3du, naopak, je tu trval\u00fd proces destabilizace. Sna\u017e\u00edme se zab\u00edt syst\u00e9m a vid\u011bt, zda p\u0159e\u017eije.<\/p>\n

Protokoly pro integraci distribuovan\u00fdch syst\u00e9m\u016f<\/b><\/h3>\n

\n\"DevOps
\n
\nTo vy\u017eaduje, aby se na\u0161e syst\u00e9my tak\u00e9 n\u011bjak zm\u011bnily. Aby se staly robustn\u011bj\u0161\u00edmi, pot\u0159ebuj\u00ed nov\u00e9 protokoly interakce mezi jejich \u010d\u00e1stmi. Aby si tyto \u010d\u00e1sti mohly vyjedn\u00e1vat a doch\u00e1zet k n\u011bjak\u00e9 samoorganizaci. A vznikaj\u00ed nov\u00e9 n\u00e1stroje, nov\u00e9 protokoly, kter\u00e9 naz\u00fdv\u00e1m \u201eprotokoly interakce distribuovan\u00fdch syst\u00e9m\u016f\u201c.<\/p>\n

\"DevOps
\n
\nO \u010dem mluv\u00edm? P\u0159edev\u0161\u00edm o projektu Opentracing<\/a><\/noindex>. Ur\u010dit\u00fd pokus vytvo\u0159it spole\u010dn\u00fd protokol pro distribuovan\u00e9 sledov\u00e1n\u00ed, kter\u00fd je zcela nezbytn\u00fdm n\u00e1strojem pro lad\u011bn\u00ed slo\u017eit\u00fdch distribuovan\u00fdch syst\u00e9m\u016f.<\/p>\n

\"DevOps
\n
\nD\u00e1le je zde Open Policy Agent<\/a><\/noindex>. \u0158\u00edk\u00e1me, \u017ee nem\u016f\u017eeme p\u0159edv\u00eddat, co se s syst\u00e9mem stane, tak\u017ee mus\u00edme zv\u00fd\u0161it jeho observabilitu. Opentracing pat\u0159\u00ed do rodiny n\u00e1stroj\u016f, kter\u00e9 poskytuj\u00ed observabilitu na\u0161ich syst\u00e9m\u016f. Ale observabilita je nezbytn\u00e1 k tomu, abychom ur\u010dili, zda se syst\u00e9m chov\u00e1 tak, jak o\u010dek\u00e1v\u00e1me, nebo ne. Jak ur\u010d\u00edme o\u010dek\u00e1van\u00e9 chov\u00e1n\u00ed? Ur\u010den\u00edm n\u011bjak\u00e9 politiky, n\u011bjak\u00e9ho souboru pravidel. Projekt Open Policy Agent se zab\u00fdv\u00e1 definov\u00e1n\u00edm tohoto souboru pravidel v \u0161irok\u00e9m spektru: od p\u0159\u00edstupu po um\u00edst\u011bn\u00ed zdroj\u016f.<\/p>\n

\"DevOps
\n
\nJak jsme \u0159ekli, na\u0161e syst\u00e9my jsou st\u00e1le v\u00edce \u0159\u00edzen\u00e9 ud\u00e1lostmi. Serverless je skv\u011bl\u00fdm p\u0159\u00edkladem syst\u00e9m\u016f \u0159\u00edzen\u00fdch ud\u00e1lostmi. Abychom mohli p\u0159ed\u00e1vat ud\u00e1losti mezi syst\u00e9my a sledovat je, pot\u0159ebujeme spole\u010dn\u00fd jazyk, spole\u010dn\u00fd protokol, jak hovo\u0159\u00edme o ud\u00e1lostech a jak si je p\u0159ed\u00e1v\u00e1me. T\u00edmto se zab\u00fdv\u00e1 projekt s n\u00e1zvem Cloudevents<\/a><\/noindex>.<\/p>\n

\"DevOps
\n
\nNep\u0159etr\u017eit\u00fd proud zm\u011bn, kter\u00fd om\u00fdv\u00e1 na\u0161e syst\u00e9my a neust\u00e1le je destabilizuje, je nep\u0159etr\u017eit\u00fd proud softwarov\u00fdch artefakt\u016f. Abychom mohli podporovat tento st\u00e1l\u00fd proud zm\u011bn, pot\u0159ebujeme n\u011bjak\u00fd spole\u010dn\u00fd protokol, pomoc\u00ed kter\u00e9ho m\u016f\u017eeme hovo\u0159it o tom, co je softwarov\u00fd artefakt, jak byl ov\u011b\u0159en a jakou verifikac\u00ed pro\u0161el. T\u00edmto se zab\u00fdv\u00e1 projekt s n\u00e1zvem Grafeas<\/a><\/noindex>. To znamen\u00e1 spole\u010dn\u00fd protokol metadat softwarov\u00fdch artefakt\u016f.<\/p>\n

\"DevOps
\n
\nA kone\u010dn\u011b, pokud chceme, aby na\u0161e syst\u00e9my byly zcela samostatn\u00e9, adaptivn\u00ed a autoreguluj\u00edc\u00ed, mus\u00edme jim umo\u017enit sebeidentifikaci. Projekt s n\u00e1zvem spiffe<\/a><\/noindex> se t\u00edmto p\u0159esn\u011b zab\u00fdv\u00e1. To je tak\u00e9 projekt pod z\u00e1\u0161titou Cloud Native Computing Foundation.<\/p>\n

V\u0161echny tyto projekty jsou mlad\u00e9, v\u0161echny pot\u0159ebuj\u00ed na\u0161i l\u00e1sku a na\u0161i kontrolu. V\u0161echny jsou open source, na\u0161e testov\u00e1n\u00ed, na\u0161\u00edm implementov\u00e1n\u00edm. Ukazuj\u00ed n\u00e1m, kter\u00fdm sm\u011brem se technologie ub\u00edr\u00e1. <\/p>\n

Ale DevOps nikdy nebyl p\u0159edev\u0161\u00edm o technologii, v\u017edy byl o spolupr\u00e1ci mezi lidmi. A pokud tedy chceme, aby se syst\u00e9my, kter\u00e9 vyv\u00edj\u00edme, zm\u011bnily, mus\u00edme se zm\u011bnit my sami. Ve skute\u010dnosti se ji\u017e m\u011bn\u00edme, nem\u00e1me mnoho na v\u00fdb\u011br. <\/p>\n

\"DevOps
\n
\nExistuje skv\u011bl\u00e1 kniha<\/a><\/noindex> britsk\u00e9 autorky Rachelle Botsman, ve kter\u00e9 p\u00ed\u0161e o evoluci d\u016fv\u011bry b\u011bhem lidsk\u00e9 historie. \u0158\u00edk\u00e1, \u017ee p\u016fvodn\u011b, v primitivn\u00edch spole\u010dnostech, byla d\u016fv\u011bra lok\u00e1ln\u00ed, tedy jsme d\u016fv\u011b\u0159ovali pouze t\u011bm, kter\u00e9 osobn\u011b zn\u00e1me. <\/p>\n

N\u00e1sledovalo velmi dlouh\u00e9 obdob\u00ed \u2014 temn\u00e1 doba, kdy byla d\u016fv\u011bra centralizov\u00e1na, kdy jsme za\u010dali d\u016fv\u011b\u0159ovat lidem, kter\u00e9 nezn\u00e1me na z\u00e1klad\u011b toho, \u017ee pat\u0159\u00edme ke stejn\u00e9mu spole\u010densk\u00e9mu nebo st\u00e1tn\u00edmu institutu.<\/p>\n

A to, co vid\u00edme v na\u0161em modern\u00edm sv\u011bt\u011b: d\u016fv\u011bra se st\u00e1v\u00e1 st\u00e1le v\u00edce rozpt\u00fdlenou a decentralizovanou, zalo\u017eenou na svobod\u011b informa\u010dn\u00edch tok\u016f a dostupnosti informac\u00ed. <\/p>\n

Pokud se zamysl\u00edme, tak tuto dostupnost, kter\u00e1 umo\u017e\u0148uje tuto d\u016fv\u011bru, vlastn\u011b realizujeme. To znamen\u00e1, \u017ee se mus\u00ed m\u011bnit nejen to, jak spolupracujeme, ale tak\u00e9 to, jak to d\u011bl\u00e1me, proto\u017ee centralizovan\u00e9 hierarchick\u00e9 IT organizace star\u00e9ho typu p\u0159est\u00e1vaj\u00ed fungovat. Za\u010d\u00ednaj\u00ed um\u00edrat. <\/p>\n

Z\u00e1klady DevOps organizace<\/b><\/h3>\n

\nIde\u00e1ln\u00ed DevOps organizace budoucnosti je decentralizovan\u00fd, adaptivn\u00ed syst\u00e9m slo\u017een\u00fd z autonomn\u00edch t\u00fdm\u016f, p\u0159i\u010dem\u017e ka\u017ed\u00fd z t\u011bchto t\u00fdm\u016f se skl\u00e1d\u00e1 z autonomn\u00edch jednotlivc\u016f. Tyto t\u00fdmy jsou rozpt\u00fdleny po cel\u00e9m sv\u011bt\u011b, efektivn\u011b spolupracuj\u00ed pomoc\u00ed asynchronn\u00ed komunikace a vysoce transparentn\u00edch protokol\u016f v\u00fdm\u011bny informac\u00ed. Velmi hezk\u00e9, \u017ee? Velmi kr\u00e1sn\u00e1 budoucnost.<\/p>\n

Samoz\u0159ejm\u011b, to v\u0161e je nemo\u017en\u00e9 bez kulturn\u00edch zm\u011bn. Mus\u00edme m\u00edt transforma\u010dn\u00ed veden\u00ed, osobn\u00ed odpov\u011bdnost a vnit\u0159n\u00ed motivaci.<\/p>\n

\"DevOps
\n
\nToto je z\u00e1klad DevOps organizac\u00ed: transparentnost informac\u00ed, asynchronn\u00ed komunikace, transforma\u010dn\u00ed veden\u00ed, decentralizace. <\/p>\n

Vyho\u0159en\u00ed<\/b><\/h3>\n

\nSyst\u00e9my, jejich\u017e sou\u010d\u00e1st\u00ed jsme, a ty, kter\u00e9 budujeme, jsou st\u00e1le v\u00edce chaotick\u00e9, a pro n\u00e1s, lidi, je t\u011b\u017ek\u00e9 se s touto my\u0161lenkou vypo\u0159\u00e1dat, je obt\u00ed\u017en\u00e9 se vzd\u00e1t iluze kontroly. Pokou\u0161\u00edme se je d\u00e1l kontrolovat, co\u017e \u010dasto vede k vyho\u0159en\u00ed. Hovo\u0159\u00edm z vlastn\u00ed zku\u0161enosti, tak\u00e9 jsem se sp\u00e1lil, jsem tak\u00e9 ob\u011bt\u00ed ne\u010dekan\u00fdch poruch v produkci.<\/p>\n

\"DevOps
\n
\nVyho\u0159en\u00ed nast\u00e1v\u00e1, kdy\u017e se sna\u017e\u00edme ovl\u00e1dat to, co se vlastn\u011b ovl\u00e1d\u00e1n\u00ed nepodl\u00e9h\u00e1. Kdy\u017e vyho\u0159\u00edme, v\u0161echno ztr\u00e1c\u00ed smysl, proto\u017ee ztr\u00e1c\u00edme touhu d\u011blat n\u011bco nov\u00e9ho, jsme v obrann\u00e9 pozici a za\u010d\u00edn\u00e1me chr\u00e1nit to, co m\u00e1me. <\/p>\n

In\u017een\u00fdrsk\u00e1 profese, jak si \u010dasto p\u0159ipom\u00edn\u00e1m, je p\u0159edev\u0161\u00edm kreativn\u00ed profese. Pokud ztr\u00e1c\u00edme touhu n\u011bco vytv\u00e1\u0159et, prom\u011b\u0148ujeme se v popel, st\u00e1v\u00e1me se popelem. Lid\u00e9 vyho\u0159\u00ed, vyho\u0159\u00ed cel\u00e9 organizace.<\/p>\n

Podle m\u00e9ho n\u00e1zoru, pouze p\u0159ijet\u00ed tvo\u0159iv\u00e9 s\u00edly chaosu, pouze budov\u00e1n\u00ed spolupr\u00e1ce podle jeho princip\u016f \u2014 to je to, co n\u00e1m pom\u016f\u017ee neztratit to dobr\u00e9, co m\u00e1me ve sv\u00e9m oboru. <\/p>\n

To v\u00e1m i p\u0159eji: milovat svou pr\u00e1ci, milovat to, co d\u011bl\u00e1me. Tento sv\u011bt se \u017eiv\u00ed informacemi, m\u00e1me tu \u010dest ho \u017eivit. Tak se poj\u010fme u\u010dit chaos, bu\u010fme chaosologov\u00e9, p\u0159in\u00e1\u0161ejme hodnotu, tvo\u0159me n\u011bco nov\u00e9ho, a probl\u00e9my, jak jsme ji\u017e zjistili, jsou nevyhnuteln\u00e9, a a\u017e se objev\u00ed, \u0159ekneme jednodu\u0161e \u201eOps!\u201c, a probl\u00e9m je vy\u0159e\u0161en. <\/p>\n

Co krom\u011b Chaos Monkey?<\/b><\/p>\n

Opravdu, v\u0161echny tyto n\u00e1stroje jsou velmi mlad\u00e9. Stejn\u011b tak Netflix budoval n\u00e1stroje pro sebe. Budujte n\u00e1stroje pro sebe. \u010ct\u011bte principy chaosov\u00e9ho in\u017een\u00fdrstv\u00ed a dodr\u017eujte tyto principy, a nehledejte jin\u00e9 n\u00e1stroje, kter\u00e9 n\u011bkdo jin\u00fd u\u017e postavil. <\/p>\n

Sna\u017ete se pochopit, jak se va\u0161e syst\u00e9my rozpadnou, a za\u010dn\u011bte je rozb\u00edjet a sledovat, jak odol\u00e1vaj\u00ed \u00fader\u016fm. To je na prvn\u00edm m\u00edst\u011b. N\u00e1stroje se daj\u00ed hledat. Existuje spousta projekt\u016f. <\/p>\n

Nepochopil jsem \u00fapln\u011b moment, kdy jste mluvili o tom, \u017ee syst\u00e9m nelze zjednodu\u0161ovat, zjednodu\u0161en\u00edm jeho komponent, a hned pot\u00e9 jste p\u0159e\u0161li k mikroslu\u017eb\u00e1m, kter\u00e9 pr\u00e1v\u011b zjednodu\u0161uj\u00ed syst\u00e9m zjednodu\u0161en\u00edm samotn\u00fdch komponent a komplikuj\u00ed interakce. To jsou v podstat\u011b dv\u011b \u010d\u00e1sti, kter\u00e9 si navz\u00e1jem odporuj\u00ed. <\/b><\/p>\n

Naprost\u00fd souhlas, mikroslu\u017eby jsou velmi kontroverzn\u00ed t\u00e9ma. Opravdu, zjednodu\u0161en\u00ed \u010d\u00e1st\u00ed zvy\u0161uje flexibilitu. Co n\u00e1m mikroslu\u017eby d\u00e1vaj\u00ed? D\u00e1vaj\u00ed n\u00e1m flexibilitu a rychlost, ale rozhodn\u011b n\u00e1m nep\u0159in\u00e1\u0161ej\u00ed jednoduchost. Zvy\u0161uj\u00ed slo\u017eitost.<\/p>\n

Tak\u017ee v filozofii DevOps, mikroslu\u017eby nejsou takov\u00fdm po\u017eehn\u00e1n\u00edm?<\/b><\/p>\n

Ka\u017ed\u00e9 po\u017eehn\u00e1n\u00ed m\u00e1 svou odvr\u00e1cenou stranu. Existuje po\u017eehn\u00e1n\u00ed: zvy\u0161uje to flexibilitu, d\u00e1v\u00e1 n\u00e1m mo\u017enost rychleji prov\u00e1d\u011bt zm\u011bny, ale zvy\u0161uje to slo\u017eitost a t\u00edm p\u00e1dem i k\u0159ehkost cel\u00e9ho syst\u00e9mu. <\/p>\n

Na co se tedy v\u00edce zam\u011b\u0159it: na zjednodu\u0161en\u00ed interakc\u00ed nebo na zjednodu\u0161en\u00ed \u010d\u00e1st\u00ed?<\/b> <\/p>\n

D\u016fraz je bezpochyby na zjednodu\u0161en\u00ed interakce, proto\u017ee pokud se na to pod\u00edv\u00e1me z pohledu toho, jak pracujeme, je prvo\u0159ad\u00e9 soust\u0159edit se na zjednodu\u0161en\u00ed interakc\u00ed, nikoli na zjednodu\u0161en\u00ed pr\u00e1ce ka\u017ed\u00e9ho z n\u00e1s jednotliv\u011b. Proto\u017ee zjednodu\u0161en\u00ed pr\u00e1ce znamen\u00e1 st\u00e1t se roboty. V McDonald's to funguje norm\u00e1ln\u011b, kdy\u017e m\u00e1\u0161 p\u0159edpis: tady dej burger, tady nalij om\u00e1\u010dku. To v na\u0161\u00ed kreativn\u00ed pr\u00e1ci naprosto nefunguje.<\/p>\n

Je pravda, \u017ee to, co jste \u0159ekli, \u017eije ve sv\u011bt\u011b bez konkurence, a chaos je tam tak laskav\u00fd, a v tomto chaosu nejsou \u017e\u00e1dn\u00e9 rozpory, nikdo nikomu nechce ubl\u00ed\u017eit? Jak by m\u011bla \u017e\u00edt konkurence a DevOps?<\/b><\/p>\n

No, z\u00e1le\u017e\u00ed na tom, o jak\u00e9 konkurenci mluv\u00edme. O konkurenci na pracovi\u0161ti nebo o konkurenci mezi firmami? <\/p>\n

O konkurenci slu\u017eeb, kter\u00e9 existuj\u00ed, proto\u017ee slu\u017eby nejsou jen n\u011bkolik firem. Vytv\u00e1\u0159\u00edme nov\u00fd typ informa\u010dn\u00edho prost\u0159ed\u00ed, a \u017e\u00e1dn\u00e9 prost\u0159ed\u00ed nem\u016f\u017ee \u017e\u00edt bez konkurence. Sout\u011b\u017e je v\u0161ude.<\/b><\/p>\n

Stejn\u00e9 Netflix vezm\u011bme jako vzor. Pro\u010d to vymysleli? Proto\u017ee pot\u0159ebovali b\u00fdt konkurenceschopn\u00ed. Tato flexibilita a rychlost pohybu jsou pr\u00e1v\u011b t\u011bmi konkurenceschopn\u00fdmi po\u017eadavky, kter\u00e9 p\u0159in\u00e1\u0161ej\u00ed chaos do na\u0161ich syst\u00e9m\u016f. Tedy chaos nen\u00ed n\u011bco, co v\u011bdom\u011b d\u011bl\u00e1me, proto\u017ee to chceme, ale to, co se d\u011bje, proto\u017ee to sv\u011bt \u017e\u00e1d\u00e1. Mus\u00edme se jen p\u0159izp\u016fsobit. A chaos je v\u00fdsledkem konkurence.<\/p>\n

To znamen\u00e1, \u017ee chaos je absence c\u00edl\u016f, \u017ee? Nebo c\u00edle, kter\u00e9 nechceme vid\u011bt? Jsme v dome\u010dku a nech\u00e1peme c\u00edle ostatn\u00edch. Konkurence vlastn\u011b existuje d\u00edky tomu, \u017ee m\u00e1me jasn\u00e9 c\u00edle, a v\u00edme, kam se dostaneme v ka\u017ed\u00e9m dal\u0161\u00edm okam\u017eiku. V tom je, z m\u00e9ho pohledu, podstata DevOps.<\/b><\/p>\n

Tak\u00e9 pohled na ot\u00e1zku. Mysl\u00edm, \u017ee c\u00edl m\u00e1me v\u0161ichni stejn\u00fd: p\u0159e\u017e\u00edt a d\u011blat to s
\nnejv\u011bt\u0161\u00ed radost\u00ed. A konkurenceschopn\u00fd c\u00edl ka\u017ed\u00e9 organizace je stejn\u00fd. P\u0159e\u017eit\u00ed se \u010dasto d\u011bje v konkuren\u010dn\u00edm boji, s t\u00edm se ned\u00e1 nic d\u011blat.<\/p>\n

Letos se konference DevOpsDays Moskva<\/a><\/noindex> uskute\u010dn\u00ed 7. prosince v \u201eTechnopolisu\u201c. Do 11. listopadu p\u0159ij\u00edm\u00e1me p\u0159ihl\u00e1\u0161ky na prezentace. Napi\u0161te<\/a><\/noindex> n\u00e1m, pokud chcete vystoupit.<\/p>\n

Registrace pro \u00fa\u010dastn\u00edky je otev\u0159en\u00e1, vstupenka stoj\u00ed 7000 rubl\u016f. P\u0159ipojte se! \n<\/p><\/blockquote>\n

Zdroj: 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\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 a Chaos: doru\u010dov\u00e1n\u00ed softwaru ve decentralizovan\u00e9m sv\u011bt\u011b | ProHoster","description":"Zakladatel a \u0159editel \u201eOtomato Software\u201c, jeden z inici\u00e1tor\u016f a instrukt\u016fr\u016f prvn\u00ed DevOps certifikace v Izraeli, Anton Weiss, hovo\u0159il na lo\u0148sk\u00e9m","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/devops-i-haos-dostavka-po-v-detsentralizovannom-mire","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/39219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=39219"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/39219\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/29435"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=39219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=39219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=39219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}