{"id":28018,"date":"2020-04-21T08:25:24","date_gmt":"2020-04-21T06:25:24","guid":{"rendered":"https:\/\/blog.wedos.cz\/?p=28018"},"modified":"2020-04-22T17:49:47","modified_gmt":"2020-04-22T15:49:47","slug":"jak-rychle-jsou-weby-u-wedos-anebo-kolik-zobrazeni-ma-nejnavstevovanejsi-web-na-nolimit","status":"publish","type":"post","link":"https:\/\/blog.wedos.com\/cs\/jak-rychle-jsou-weby-u-wedos-anebo-kolik-zobrazeni-ma-nejnavstevovanejsi-web-na-nolimit","title":{"rendered":"Jak rychl\u00e9 jsou weby u WEDOS anebo kolik zobrazen\u00ed m\u00e1 nejnav\u0161t\u011bvovan\u011bj\u0161\u00ed web na NoLimit?"},"content":{"rendered":"

N\u00e1\u0161 syst\u00e9m CML (Centr\u00e1ln\u00ed Monitoring Log\u016f) shroma\u017e\u010fuje nep\u0159etr\u017eit\u011b data ze v\u0161ech server\u016f a dal\u0161\u00edch za\u0159\u00edzen\u00ed v na\u0161\u00ed s\u00edti a v re\u00e1ln\u00e9m \u010dase je vyhodnocuje. Denn\u011b se jedn\u00e1 o 600 – 700 GB dat. Slou\u017e\u00ed prim\u00e1rn\u011b pro \u00fa\u010dely dohled\u00e1n\u00ed chyb a probl\u00e9m\u016f. Ov\u0161em vyu\u017e\u00edv\u00e1me je nap\u0159\u00edklad i pro na\u0161e ochrany. Co kdybychom z nich ale ud\u011blali t\u0159eba infografiku?<\/p>\n

<\/p>\n

Jak\u00e1 data jsou pou\u017eita<\/h3>\n

N\u00e1sleduj\u00edc\u00ed data jsou sestavena z 521.314.847 <\/strong>vygenerovan\u00fdch str\u00e1nk\u00e1ch v obdob\u00ed za 1 t\u00fdden od ned\u011ble 12.04.2020 do soboty 18.04.2020 na slu\u017eb\u00e1ch NoLimit<\/a> (star\u00e9 i nov\u00e9 servery) a WMS<\/a>. Jen pro zaj\u00edmavost celkov\u00fd provoz byl za tuto dobu 2.001.258.362<\/strong> request\u016f.<\/p>\n

Je to tedy pr\u016fm\u011brn\u011b cca 862 vygenerovan\u00fdch str\u00e1nek za sekundu. V noci v\u00fdrazn\u011b m\u00e9n\u011b, p\u0159es den v\u00fdrazn\u011b v\u00edce. Ale to nen\u00ed v\u0161e. Dnes se n\u00ed\u017ee dozv\u00edte n\u011bkolik dal\u0161\u00edch zaj\u00edmavost\u00ed…<\/p>\n

P\u0159es polovinu po\u017eadavk\u016f nap\u0159\u00edklad blokujeme, tak\u017ee se nezobraz\u00ed koncov\u00e9mu robotovi (nebo \u00fato\u010dn\u00edkovi) a nejsou v n\u00ed\u017ee uveden\u00fdch statistik\u00e1ch zahrnuty. Ka\u017ed\u00e1 str\u00e1nka se skl\u00e1d\u00e1 z r\u016fzn\u00fdch \u010d\u00e1st\u00ed a ty tak\u00e9 logujeme. Logujeme tak pr\u016fm\u011brn\u011b des\u00edtky tis\u00edc z\u00e1znam\u016f ka\u017edou sekundu. Ve \u0161pi\u010dce je to mnohem v\u00edce a v noci naopak m\u00e9n\u011b.\u00a0<\/p>\n

Jak rychl\u00e9 jsou str\u00e1nky na WEDOS?<\/h3>\n

Ob\u010das n\u011bkde zazn\u00ed, \u017ee jsou weby u n\u00e1s pomal\u00e9. Kdy\u017e to s n\u00e1mi n\u011bkdo \u0159e\u0161\u00ed, tak v\u011bt\u0161inou zjist\u00edme, \u017ee nem\u00e1 spr\u00e1vn\u011b nastaven\u00e9 cachov\u00e1n\u00ed, str\u00e1nce br\u00e1n\u00ed ve vykreslen\u00ed n\u011bjak\u00fd prvek t\u0159et\u00ed strany anebo pou\u017e\u00edv\u00e1 n\u011bjak\u00e9 roz\u0161\u00ed\u0159en\u00ed, co komunikuje s t\u0159et\u00ed stranou a ta je pomal\u00e1.<\/p>\n

Jak\u00fd je tedy u WEDOS pr\u016fm\u011br pro v\u0161echny str\u00e1nky a\u0165 u\u017e se jedn\u00e1 o cachovanou php str\u00e1nku, skript co parsuje data anebo vyhled\u00e1v\u00e1n\u00ed v eshopu?<\/p>\n

\u010cas v grafice je v ms a ud\u00e1v\u00e1 za jak dlouhou server poskytl obsah n\u00e1v\u0161t\u011bvn\u00edkovi. V re\u00e1lu je tak je\u0161t\u011b t\u0159eba p\u0159i\u010d\u00edst p\u00e1r ms pro komunikaci v r\u00e1mci \u010cR a SR anebo p\u00e1r des\u00edtek ms pro komunikaci v r\u00e1mci Evropy.<\/p>\n

Pr\u016fm\u011br vygenerov\u00e1n\u00ed str\u00e1nky serverem<\/strong><\/h4>\n

\"\"<\/a><\/p>\n

Jak je vid\u011bt, tak str\u00e1nky na star\u0161\u00edch serverech NoLimit jsou v pr\u016fm\u011bru pomalej\u0161\u00ed 759 ms<\/strong>, proto\u017ee zde jsou vyu\u017e\u00edv\u00e1ny slab\u0161\u00ed procesory pro webserver i datab\u00e1zi a serverov\u00e9 SSD.<\/p>\n

Nov\u00e9 NoLimit, kter\u00e9 u\u017e jedou v cloudu na HPE Moonshot jsou rychlej\u0161\u00ed o zhruba 11,3%. 7 denn\u00ed pr\u016fm\u011br je 673 ms<\/strong>. Va\u0161e skripty maj\u00ed k dispozici 3,8 GHz procesory a velmi rychl\u00e9 NVMe SSD disky.<\/p>\n

Z\u00e1kazn\u00edk\u016f na WMS jsou zat\u00edm jen des\u00edtky, proto jsou data hodn\u011b zkreslen\u00e1. WMS m\u00e1 v\u017edy vyhrazen\u00fd v\u00fdkon hardwaru a tak tam nedoch\u00e1z\u00ed tolik k ovlivn\u011bn\u00ed jin\u00fdmi u\u017eivateli. I tak vych\u00e1z\u00ed pr\u016fm\u011br 403 ms<\/strong>.<\/p>\n

Median vygenerov\u00e1n\u00ed str\u00e1nky serverem<\/strong><\/h4>\n

\"\"<\/a><\/p>\n

S pr\u016fm\u011brem rychlosti str\u00e1nky na webhostingu je to v\u0161ak jak s pr\u016fm\u011brn\u00fdm platem. P\u00e1r lid\u00ed m\u00e1 o hodn\u011b v\u00edce ne\u017e ostatn\u00ed a pak to vypad\u00e1, \u017ee v\u0161ichni maj\u00ed v pr\u016fm\u011bru hodn\u011b \ud83d\ude42<\/p>\n

Daleko v\u00edce prozrad\u00ed median, tedy skute\u010dn\u00e1 prost\u0159edn\u00ed hodnota.<\/p>\n

Median u\u017e vypad\u00e1 jinak. Sta\u010d\u00ed aby byl neoptimalizovan\u00fd redak\u010dn\u00ed syst\u00e9m a u\u017e jde pr\u016fm\u011br rychle nahoru. Des\u00edtky vte\u0159in spot\u0159ebuj\u00ed i skripty, kter\u00e9 volaj\u00ed z\u00e1kazn\u00edci pravideln\u011b p\u0159es CRONy, nap\u0159\u00edklad automatick\u00e9 z\u00e1lohov\u00e1n\u00ed, import\/export dat anebo \u00fadr\u017eba mohou trvat i minuty.<\/p>\n

To je vid\u011bt i na t\u00e9to grafice. P\u0159ekvapiv\u011b medi\u00e1n web\u016f je rychlej\u0161\u00ed na star\u00fdch NoLimit (107 ms<\/strong>) ne\u017e na nov\u00fdch NoLimit (208 ms<\/strong>). Jak je to mo\u017en\u00e9? Na star\u0161\u00edch NoLimit jsou p\u0159ev\u00e1\u017en\u011b zku\u0161en\u011bj\u0161\u00ed z\u00e1kazn\u00edci, kte\u0159\u00ed bu\u010f nepou\u017e\u00edvaj\u00ed redak\u010dn\u00ed syst\u00e9my, maj\u00ed sv\u00e9 \u0159e\u0161en\u00ed na m\u00edru, anebo si je redak\u010dn\u00ed syst\u00e9my je\u0161t\u011b instalovali ru\u010dn\u011b sami. Um\u00ed si je optimalizovat a ve v\u00fdsledku i s pomalej\u0161\u00edmi procesory dok\u00e1\u017eou dos\u00e1hnout vy\u0161\u0161\u00edch rychlost\u00ed.<\/p>\n

Kdy\u017e se pod\u00edv\u00e1me na 7 denn\u00ed graf s medianem u nov\u00fdch Nolimit, tak vid\u00edme \u0161pi\u010dky, kdy\u017e je n\u00e1razov\u00fd provoz. Celkov\u011b je v\u0161ak graf sp\u00ed\u0161e vyrovnan\u00fd. Nov\u00e9 NoLimit jsou hodn\u011b naddimenzovan\u00e9 a nav\u00edc jim pom\u00e1haj\u00ed proxy servery (viz. d\u00e1le).<\/p>\n

\"\"<\/a><\/p>\n

Naopak na star\u0161\u00edch serverech vid\u00edme vesm\u011bs podobn\u00fd provoz ka\u017ed\u00fd den. Zku\u0161en\u011bj\u0161\u00ed u\u017eivatel\u00e9 prov\u00e1d\u00ed v noci \u00fadr\u017eby, z\u00e1lohuj\u00ed, importuj\u00ed data a dal\u0161\u00ed n\u00e1ro\u010dn\u011b procedury. P\u0159es den pak provoz kop\u00edruje b\u011b\u017en\u00fd z\u00e1jem lid\u00ed o str\u00e1nky. Na star\u0161\u00edm NoLimit u\u017e nav\u00edc nep\u0159ib\u00fdvaj\u00ed nov\u00ed z\u00e1kazn\u00edci.\u00a0<\/p>\n

\"\"<\/a><\/p>\n

Proxy servery<\/strong><\/h4>\n

Nov\u00e9 NoLimit a WMS maj\u00ed k dispozici proxy servery, kter\u00e9 mohou vyu\u017e\u00edt. Tyto proxy servery dok\u00e1\u017e\u00ed odbavovat velice rychle po\u017eadavky, proto\u017ee si ulo\u017e\u00ed vygenerovanou str\u00e1nku a pak j\u00ed z\u00e1kazn\u00edk\u016fm serv\u00edruj\u00ed p\u0159\u00edmo. Nen\u00ed nutn\u00e9 je tedy znovu generovat na serveru. Proxy servery v\u0161ak v\u011bt\u0161inou z\u00e1kazn\u00edci vyu\u017e\u00edvaj\u00ed nep\u0159\u00edmo prost\u0159ednictv\u00edm roz\u0161\u00ed\u0159en\u00ed pro sv\u00e9 redak\u010dn\u00ed syst\u00e9my.<\/p>\n

Na n\u00e1sleduj\u00edc\u00edm grafu vid\u00edte, za jak dlouho v pr\u016fm\u011bru odbav\u00ed proxy server po\u017eadavek na str\u00e1nku. Do pr\u016fm\u011bru je zapo\u010dtena jak doba \u010dek\u00e1n\u00ed na prvn\u00ed vygenerov\u00e1n\u00ed, tak i ulo\u017een\u00e1 str\u00e1nka.<\/p>\n

\"\"<\/a><\/p>\n

Sp\u00ed\u0161e median tak prozrad\u00ed, jak velkou rychlost m\u016f\u017ee proxy server poskytnout. 208 ms<\/strong> sever vs 148 ms<\/strong> proxy, to je t\u00e9m\u011b\u0159 29 % rychlej\u0161\u00ed.<\/p>\n

\"\"<\/a>Z\u00e1kazn\u00edci, kte\u0159\u00ed n\u00e1\u0161 proxy server um\u00ed vyu\u017e\u00edvat maj\u00ed str\u00e1nky vygenerovan\u00e9 opravdu rychle, ale popravd\u011b n\u011bco tomu je\u0161t\u011b chyb\u00ed…<\/p>\n

Pracujeme te\u010f na Proxy v2.0, kter\u00e1 bude postaven\u00e1 na NGINX a hlavn\u011b bude anycast s body po cel\u00e9m sv\u011bt\u011b. Tam je c\u00edlem vracet str\u00e1nky rychlost\u00ed mrknut\u00edm oka (pod 100 ms) a to kdekoliv na sv\u011bt\u011b \ud83d\ude09<\/p>\n

Nejv\u011bt\u0161\u00ed weby na NoLimit a WMS<\/h3>\n

NoLimit byl u\u017e v dob\u011b spu\u0161t\u011bn\u00ed nadstandardn\u011b naddimenzovan\u00fd webhosting. Zat\u00edmco u v\u011bt\u0161iny konkuren\u010dn\u00edch nab\u00eddek jste v roce 2011 nedok\u00e1zali kv\u016fli parametr\u016fm po\u0159\u00e1dn\u011b rozjet WordPress, tak NoLimit pro n\u011bj nab\u00edzel ide\u00e1ln\u00ed parametry za 15 K\u010d\/m\u011bs\u00edc (m\u011bli jsme p\u0159i rozjedu WEDOS zav\u00e1d\u011bc\u00ed ceny).<\/p>\n

D\u00edky redak\u010dn\u00edm syst\u00e9m\u016fm jako je WordPress jsem vyrostli, a proto jsou pro n\u00e1s prioritou te\u010f i do budoucna. Hl\u00edd\u00e1me si jak u n\u00e1s funguj\u00ed a jestli zvl\u00e1dnou ut\u00e1hnout \u010dasto ob\u0159\u00ed n\u00e1v\u0161t\u011bvnost. M\u00e1me pro pomoc s redak\u010dn\u00edmi syst\u00e9my vy\u0161kolen\u00e9 CMS specialisty s roky praxe, optimalizujeme na\u0161e slu\u017eby a\u00a0 upravujeme nastaven\u00ed na\u0161ich ochran na m\u00edru CMS. Neboj\u00edme se ani po\u0159\u00e1dn\u011b s\u00e1hnout do nastaven\u00ed a nav\u00fd\u0161it parametry<\/a>, aby NoLimit byl pro obl\u00edben\u00e9 redak\u010dn\u00ed syst\u00e9my st\u00e1le nejlep\u0161\u00ed volbou.<\/p>\n

Kolik ale ve skute\u010dnosti ut\u00e1hne NoLimit, pokud se o weby staraj\u00ed profesion\u00e1lov\u00e9, kte\u0159\u00ed UM\u00cd \ud83d\ude09<\/p>\n

Na n\u00e1sleduj\u00edc\u00edm grafu vid\u00edte TOP 20 web\u016f na NoLimit podle po\u010dtu zobrazen\u00ed za 7 dn\u00ed.<\/p>\n

\"\"<\/a><\/p>\n

Ano, rekordman m\u00e1 30.887.648<\/strong> zobrazen\u00ed za t\u00fdden, tj. 4.412.521<\/strong> za den anebo 183.855<\/strong> za hodinu, celkem tak ze v\u0161ech t\u00fddenn\u00edch zobrazen\u00ed v\u0161ech web\u016f d\u011bl\u00e1 5,93 %. A ano jede na NoLimit, jen m\u00e1 p\u0159\u00edplatkovou slu\u017ebu Extra \ud83d\ude42<\/p>\n

Dal\u0161\u00ed n\u00e1m z\u016fstali trochu pozadu, tak se pod\u00edv\u00e1me na ten sam\u00fd graf s logaritmickou stupnic\u00ed.<\/p>\n

\"\"<\/a><\/p>\n

Jak vid\u00edte, tak abyste se dostali do TOP 20 na WEDOS NoLimit anebo WMS, tak mus\u00edte p\u0159ekro\u010dit hranici 700 tis\u00edc impres\u00ed za t\u00fdden<\/strong>. Ale pozor .html str\u00e1nky, dokumenty a multim\u00e9dia do toho nepo\u010d\u00edt\u00e1me \ud83d\ude09<\/p>\n

S v\u00fdjimkou jednoho webu, kter\u00fd je na WMS, jsou v\u0161echny na NoLimit. Dokonce n\u011bkter\u00e9 nemaj\u00ed ani extra. Asi nep\u0159ekvap\u00ed, \u017ee v\u011bt\u0161ina je na WordPress. Tak\u017ee nev\u011b\u0159te tomu, \u017ee WordPress je jen na mal\u00e9 osobn\u00ed str\u00e1nky \ud83d\ude42<\/p>\n

Mimochodem v\u0161echny na\u0161e firemn\u00ed WEDOS weby jedou na WordPress. Dokonce u n\u00e1s je na NoLimit jeden z p\u0159edn\u00edch \u010desk\u00fdch eshop\u016f s cca miliardov\u00fdm obratem a jede tak\u00e9 na WordPress.<\/p>\n

Tak\u017ee a\u017e se v\u00e1s n\u011bkdo p\u0159\u00ed\u0161t\u011b zept\u00e1, jestli NoLimit ut\u00e1hne 10 tis\u00edc n\u00e1v\u0161t\u011bv, tak mu m\u016f\u017eete \u0159\u00edct: „Pokud um\u00ed\u0161 optimalizovat weby, tak za hodinu n\u011bkolikr\u00e1t“ \ud83d\ude09<\/p>\n

Na co se tento t\u00fdden \u00fato\u010dilo<\/h3>\n

Samoz\u0159ejm\u011b na na\u0161ich NoLimit by nikdy ne\u0161lo provozovat takto velk\u00e9 weby, pokud bychom v\u0161echny nechr\u00e1nili p\u0159ed \u00fatoky. \u00dato\u010dn\u00edci, roboti co sb\u00edraj\u00ed marketingov\u00e1 data a spousta dal\u0161\u00edch ne\u0159\u00e1d\u016f vytv\u00e1\u0159\u00ed neskute\u010dn\u00e9 mno\u017estv\u00ed z\u00e1t\u011b\u017ee. V\u00edce jak polovina v\u0161eho provozu u\u017e dnes tvo\u0159\u00ed „bordel“, kter\u00fd kdy\u017e odfiltrujeme tak nikomu nechyb\u00ed.<\/p>\n

Bez ochran by ka\u017ed\u00fd web nav\u0161t\u00edvilo za den stovky a\u017e tis\u00edce robot\u016f a automatick\u00fdch skript\u016f. To je neskute\u010dn\u00e1 z\u00e1t\u011b\u017e.<\/p>\n

Postupem \u010dasu jsem postavili robustn\u00ed s\u00e9rii ochran, kter\u00e9 r\u016fzn\u00fdmi zp\u016fsoby chr\u00e1n\u00ed weby na\u0161ich z\u00e1kazn\u00edk\u016f. Nejv\u011bt\u0161\u00ed a nejn\u00e1kladn\u011bj\u0161\u00ed je DDoS ochrana. Za ty roky jsme j\u00ed zdokonalili a vylep\u0161ili natolik, \u017ee ob\u010das zapom\u00edn\u00e1me, \u017ee j\u00ed m\u00e1me, i kdy\u017e na n\u00e1s sm\u011b\u0159uje \u00fatok o s\u00edle 44,5 Gbps<\/a>.<\/p>\n

Za n\u00ed je velmi rychl\u00e1 filtrace na b\u00e1z\u00ed blacklist\u016f, greylist\u016f a whitelist\u016f. Ta \u010derp\u00e1 data z CML. Pokud se n\u011bjak\u00e1 IP adresa chov\u00e1 podez\u0159ele, tak dostane ban. Tato ochrana je neust\u00e1le roz\u0161i\u0159ov\u00e1na a jej\u00ed pod\u00edl na blokov\u00e1n\u00ed z\u00e1vadn\u00e9ho provozu roste.<\/p>\n

Toto filtrov\u00e1n\u00ed se m\u011bn\u00ed naprosto dynamicky a reaguje na aktu\u00e1ln\u00ed hrozby. N\u011bkoho jen p\u0159ibrzd\u00edme, jin\u00e9ho zablokujeme. N\u011bkoho na p\u00e1r sekund, jin\u00e9ho na minuty a jin\u00e9ho na hodiny a n\u011bkter\u00e9 „loupe\u017en\u00edky“ trvale.\u00a0 V\u0161e jede automaticky a nep\u0159etr\u017eit\u011b a ka\u017edou minutu to vyhodnocuje data a podle toho m\u011bn\u00ed pravidla.<\/p>\n

A pak tu je IPS\/IDS ochrana. Ta u\u017e p\u0159\u00edmo filtruje ne\u0161ifrovan\u00fd (HTTP) provoz. Skl\u00e1d\u00e1 se z v\u00edce jak 20 tis\u00edc pravidel a slou\u017e\u00ed jako posledn\u00ed barik\u00e1da. Um\u00ed rozeznat obecn\u00fd i konkr\u00e9tn\u00ed \u00fatok a zastavit jej. Vyu\u017e\u00edv\u00e1me tak\u00e9 data z ve\u0159ejn\u00fdch i soukrom\u00fdch datab\u00e1z\u00ed zn\u00e1m\u00fdch zranitelnost\u00ed. Bohu\u017eel nechr\u00e1n\u00ed HTTPS provoz, co\u017e bude \u0159e\u0161it Proxy v2.0.<\/p>\n

A na co se tento t\u00fdden nejv\u00edce \u00fato\u010dilo? Podle dat z p\u0159edsunut\u00e9 filtrace a IPS\/IDS to byla hlavn\u00ed str\u00e1nka. Tam toho blokujeme nejv\u00edce.<\/p>\n

\"\"<\/a><\/p>\n

Pro p\u0159ehlednost se pod\u00edv\u00e1me je\u0161t\u011b na graf s logaritmickou stupnic\u00ed.<\/p>\n

\"\"<\/a><\/p>\n

Jak vid\u00edte na grafu, tak v\u011bt\u0161ina \u00fatok\u016f sm\u011b\u0159uje na WordPress. Jedn\u00e1 se o hodn\u011b zn\u00e1m\u00e9 bezpe\u010dnostn\u00ed d\u00edry, kterou jsou velmi masivn\u011b zneu\u017e\u00edvan\u00e9. Nejnebezpe\u010dn\u011bj\u0161\u00ed \u00fatoky v\u0161ak nenajdete v \u017e\u00e1dn\u00fdch grafech naho\u0159e. \u00dato\u010dn\u00edci si hl\u00eddaj\u00ed, aby nebyli moc vid\u011bt. Um\u00ed rozlo\u017eit \u00fatok nap\u0159\u00ed\u010d \u010dasem i servery. \u00dato\u010d\u00ed t\u0159eba 1x za 7 minut na 1 web na 1 IP adrese. My to vid\u00edme, proto\u017ee stahujeme v\u0161echna data na jedno m\u00edsto ze v\u0161ech server\u016f.<\/p>\n

Z\u00e1v\u011br<\/h3>\n

Z obrovsk\u00e9ho mno\u017estv\u00ed dat vid\u00edme hodn\u011b zaj\u00edmav\u00e9 informace.\u00a0 A takto postupn\u011b analyzujeme a vyu\u017e\u00edv\u00e1me nejen k ochran\u011b p\u0159ed \u00fato\u010dn\u00edky, ale chceme t\u0159eba brzo pomoci\u00a0 klient\u016fm s t\u00edm, aby se nenechali \u0161idit od reklamn\u00edch s\u00edt\u00ed… Nebudete toti\u017e v\u011b\u0159it, \u017ee a\u017e p\u0159es 90 % v\u0161ech online reklam jsou vlastn\u011b naprosto ne\u00fa\u010dinn\u00e9 odliky a prokliky robot\u016f nebo omyl\u016f. A pokud za online reklamu plat\u00edte, tak t\u00edm v mnoha p\u0159\u00edpadech jen vyhazujete pen\u00edze oknem – na\u0161e vlastn\u00ed zku\u0161enost. Ale o tom a\u017e zase p\u0159\u00ed\u0161t\u011b.\u00a0<\/p>\n

Tak co \u0159\u00edk\u00e1te na na\u0161\u00ed prvn\u00ed komentovanou infografiku? Pokud se v\u00e1m l\u00edb\u00ed, m\u016f\u017eeme p\u0159ipravit dal\u0161\u00ed, detailn\u011bj\u0161\u00ed a nejen o webech u WEDOS. M\u00e1me t\u0159eba dost velk\u00fd vzorek (t\u00e9m\u011b\u0159 20 % .cz dom\u00e9n), abychom v\u00e1m dok\u00e1zali uk\u00e1zat, jak je na tom \u010desk\u00fd Internet \ud83d\ude42<\/p>\n

V infografice jsou jen webhostingy a WMS. Nejsou tam \u017e\u00e1dn\u00e9 dedikovan\u00e9 nebo virtu\u00e1ln\u00ed servery nebo jin\u00e9 slu\u017eby.\u00a0<\/p>\n

Anebo rad\u0161i n\u011bco temn\u011bj\u0161\u00edho? Backdoory, DDoS \u00fatoky, 0-day exploity \ud83d\ude09<\/p>\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

N\u00e1\u0161 syst\u00e9m CML (Centr\u00e1ln\u00ed Monitoring Log\u016f) shroma\u017e\u010fuje nep\u0159etr\u017eit\u011b data ze v\u0161ech server\u016f a dal\u0161\u00edch za\u0159\u00edzen\u00ed v na\u0161\u00ed s\u00edti a v re\u00e1ln\u00e9m \u010dase je vyhodnocuje. Denn\u011b se jedn\u00e1 o 600 – 700 GB dat. Slou\u017e\u00ed prim\u00e1rn\u011b pro \u00fa\u010dely dohled\u00e1n\u00ed chyb a probl\u00e9m\u016f. Ov\u0161em vyu\u017e\u00edv\u00e1me je nap\u0159\u00edklad i pro na\u0161e ochrany. Co kdybychom z nich ale ud\u011blali … <\/p>\n

Pokra\u010dovat ve \u010dten\u00ed „Jak rychl\u00e9 jsou weby u WEDOS anebo kolik zobrazen\u00ed m\u00e1 nejnav\u0161t\u011bvovan\u011bj\u0161\u00ed web na NoLimit?“<\/span><\/a><\/p>\n","protected":false},"author":9,"featured_media":28072,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[117,41,83,27,37],"class_list":["post-28018","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technologie","tag-ips-ids","tag-nolimit","tag-ochrana","tag-wms","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/28018","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/comments?post=28018"}],"version-history":[{"count":38,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/28018\/revisions"}],"predecessor-version":[{"id":28468,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/28018\/revisions\/28468"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/media\/28072"}],"wp:attachment":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/media?parent=28018"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/categories?post=28018"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/tags?post=28018"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}