{"id":38233,"date":"2019-10-31T22:22:28","date_gmt":"2019-10-31T19:22:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/gcp-razbor-vychislitelnogo-steka-google-cloud-platform\/"},"modified":"2019-10-31T22:22:28","modified_gmt":"2019-10-31T19:22:28","slug":"gcp-razbor-vychislitelnogo-steka-google-cloud-platform","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/gcp-razbor-vychislitelnogo-steka-google-cloud-platform","title":{"rendered":"GCP: Anal\u00fdza v\u00fdpo\u010detn\u00ed platformy Google Cloud Platform","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u0159eklad \u010dl\u00e1nku byl p\u0159ipraven speci\u00e1ln\u011b pro studenty kurzu \u201eCloudov\u00e9 slu\u017eby\u201c<\/a><\/noindex>.<\/em> <\/p>\n

<\/p>\n

Zaj\u00edm\u00e1 v\u00e1s rozvoj v tomto sm\u011bru?<\/strong> Pod\u00edvejte se na z\u00e1znam profesion\u00e1ln\u00edho workshopu \u201eAWS EC2 slu\u017eba\u201c<\/a><\/noindex>, kter\u00fd vedl Egor Zuyev \u2014 TeamLead ve spole\u010dnosti InBit a autor vzd\u011bl\u00e1vac\u00edho programu v OTUS.<\/em><\/p>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

Google Cloud Platform (GCP) nab\u00edz\u00ed \u0159adu slu\u017eeb, a to zejm\u00e9na v\u00fdpo\u010detn\u00ed stack, kter\u00fd zahrnuje Google Compute Engine (GCE), Google Kubernetes Engine (d\u0159\u00edve \u2013 Container Engine) (GKE), Google App Engine (GAE) a Google Cloud Functions (GCF). V\u0161echny tyto slu\u017eby maj\u00ed zaj\u00edmav\u00e9 n\u00e1zvy, ale nemus\u00ed b\u00fdt zcela jasn\u00e9, jak\u00e9 maj\u00ed funkce a co je \u010din\u00ed jedine\u010dn\u00fdmi navz\u00e1jem. Tento \u010dl\u00e1nek je ur\u010den pro ty, kte\u0159\u00ed se teprve seznamuj\u00ed s koncepty cloudu, zejm\u00e9na s cloudov\u00fdmi slu\u017ebami a GCP. <\/a><\/noindex><\/p>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

1. V\u00fdpo\u010detn\u00ed stack<\/h2>\n

<\/p>\n

V\u00fdpo\u010detn\u00ed stack lze pova\u017eovat za v\u00edce\u00farov\u0148ovou abstrakci nad t\u00edm, co m\u016f\u017ee po\u010d\u00edta\u010dov\u00fd syst\u00e9m poskytnout. Tento stack stoup\u00e1 (moves up<\/em>) od \u201ehol\u00e9ho \u017eeleza\u201c (bare metal<\/em>), vztahuj\u00edc\u00edho se k skute\u010dn\u00fdm hardwarov\u00fdm komponent\u016fm po\u010d\u00edta\u010de, a\u017e po funkce (functions<\/em>), kter\u00e9 p\u0159edstavuj\u00ed nejmen\u0161\u00ed jednotku v\u00fdpo\u010dtu. D\u016fle\u017eit\u00e9 je poznamenat, \u017ee ve vztahu ke stacku se slu\u017eby agreguj\u00ed p\u0159i pohybu vzh\u016fru, nap\u0159\u00edklad sekce \u201eaplikace\u201c (apps<\/em>), zn\u00e1zorn\u011bn\u00e1 na obr\u00e1zku 1 n\u00ed\u017ee, by m\u011bla obsahovat v\u0161echny z\u00e1kladn\u00ed komponenty kontejner\u016f (kontejnery<\/em>), virtu\u00e1ln\u00edch stroj\u016f (virtual machines<\/em>) a hardwaru. Stejn\u00fdm zp\u016fsobem mus\u00ed komponent virtu\u00e1ln\u00edch stroj\u016f obsahovat hardware uvnit\u0159 pro fungov\u00e1n\u00ed.<\/p>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

Obr\u00e1zek 1: V\u00fdpo\u010detn\u00ed stack | Obr\u00e1zek byl p\u0159evzat z Google Cloud<\/a><\/noindex><\/em><\/p>\n

<\/p>\n

Tento model, zn\u00e1zorn\u011bn\u00fd na obr\u00e1zku 1, je z\u00e1kladem pro popis nab\u00eddek od cloudov\u00fdch poskytovatel\u016f. N\u011bkte\u0159\u00ed poskytovatel\u00e9 mohou nab\u00edzet pouze, nap\u0159\u00edklad, kontejnery a slu\u017eby ni\u017e\u0161\u00ed kvality v r\u00e1mci stacku, jin\u00ed pak v\u0161e, co je zn\u00e1zorn\u011bno na obr\u00e1zku 1.<\/p>\n

<\/p>\n

\u2014 Pokud jste obezn\u00e1meni s cloudov\u00fdmi slu\u017ebami, p\u0159ejd\u011bte na \u010d\u00e1st 3<\/strong>, abyste se sezn\u00e1mili s ekvivalentem GCP
\n\u2014 Pokud pot\u0159ebujete pouze shrnut\u00ed o cloudov\u00fdch slu\u017eb\u00e1ch, p\u0159ejd\u011bte na \u010d\u00e1st 2.4<\/strong><\/p><\/blockquote>\n

<\/p>\n

2. Cloudov\u00e9 slu\u017eby<\/h2>\n

<\/p>\n

Sv\u011bt cloudov\u00e9ho v\u00fdpo\u010detnictv\u00ed je velmi rozmanit\u00fd. Cloudov\u00ed poskytovatel\u00e9 nab\u00edzej\u00ed \u0159adu slu\u017eeb, kter\u00e9 jsou p\u0159izp\u016fsobeny r\u016fzn\u00fdm po\u017eadavk\u016fm klient\u016f. Mo\u017en\u00e1 jste sly\u0161eli o takov\u00fdch term\u00ednech jako IaaS, PaaS, SaaS, FaaS, KaaS atd. se v\u0161emi p\u00edsmeny abecedy, za kter\u00fdmi n\u00e1sleduje \u201eaaS\u201c. Navzdory zvl\u00e1\u0161tn\u00edmu pojmenov\u00e1n\u00ed tvo\u0159\u00ed tyto term\u00edny sadu slu\u017eeb cloudov\u00fdch poskytovatel\u016f. Uv\u00e1d\u00edm, \u017ee existuj\u00ed 3 hlavn\u00ed nab\u00eddky \u201ejako slu\u017eba\u201c (as a Service), kter\u00e9 cloudov\u00ed poskytovatel\u00e9 t\u00e9m\u011b\u0159 v\u017edy poskytuj\u00ed. <\/p>\n

<\/p>\n

Jsou to IaaS, PaaS a SaaS, kter\u00e9 znamenaj\u00ed respektive infrastrukturu jako slu\u017ebu (Infrastructure as a Service), platformu jako slu\u017ebu (Platform as a Service) a software jako slu\u017ebu (Software as a Service). Je d\u016fle\u017eit\u00e9 vizualizovat cloudov\u00e9 slu\u017eby jako \u00farovn\u011b nab\u00edzen\u00fdch slu\u017eeb. To znamen\u00e1, \u017ee kdy\u017e se dost\u00e1v\u00e1te nahoru nebo dol\u016f na \u00farovni, jako klient p\u0159ekon\u00e1v\u00e1te r\u016fzn\u00e9 varianty slu\u017eeb, kter\u00e9 jsou bu\u010f p\u0159id\u00e1v\u00e1ny, nebo odebr\u00e1ny z hlavn\u00ed nab\u00eddky. Nejl\u00e9pe to lze pova\u017eovat za pyramidu, jak je zn\u00e1zorn\u011bno na obr\u00e1zku 2.
\n\"GCP:<\/p>\n

<\/p>\n

Obr\u00e1zek 2: Pyramida \u201eaaS\u201c | Obr\u00e1zek p\u0159evzat\u00fd z Ruby Garage<\/a><\/noindex><\/em><\/p>\n

<\/p>\n

2.1 Infrastruktura jako slu\u017eba (IaaS)<\/h4>\n

<\/p>\n

To je nejni\u017e\u0161\u00ed \u00farove\u0148, kterou m\u016f\u017ee poskytovatel cloudov\u00fdch slu\u017eeb nab\u00eddnout, a zahrnuje poskytovatele cloudov\u00e9ho v\u00fdpo\u010detnictv\u00ed, kter\u00fd dod\u00e1v\u00e1 \u201eholou\u201c infrastrukturu, v\u010detn\u011b middleware, s\u00ed\u0165ov\u00fdch kabel\u016f, procesor\u016f, grafick\u00fdch procesor\u016f, pam\u011bti RAM, extern\u00edho \u00falo\u017ei\u0161t\u011b, server\u016f a obraz\u016f z\u00e1kladn\u00edch opera\u010dn\u00edch syst\u00e9m\u016f, jako jsou Debian Linux, CentOS, Windows atd. <\/p>\n

<\/p>\n

Pokud si objedn\u00e1te nab\u00eddku IaaS od poskytovatele cloudov\u00fdch slu\u017eeb, to je to, co byste m\u011bli o\u010dek\u00e1vat. Na v\u00e1s, jako klientovi, z\u016fst\u00e1v\u00e1 sestaven\u00ed t\u011bchto \u010d\u00e1st\u00ed pro provozov\u00e1n\u00ed va\u0161eho podnik\u00e1n\u00ed. \u00darove\u0148 toho, s \u010d\u00edm budete muset pracovat, se m\u016f\u017ee li\u0161it od poskytovatele k poskytovateli, ale obecn\u011b dost\u00e1v\u00e1te hardware a OS, zat\u00edmco ostatn\u00ed je zcela na v\u00e1s. P\u0159\u00edklady IaaS zahrnuj\u00ed AWS Elastic Compute, Microsoft Azure a GCE.<\/p>\n

<\/p>\n

N\u011bkter\u00fdm lidem se nemus\u00ed l\u00edbit, \u017ee mus\u00ed instalovat obrazy OS a zab\u00fdvat se s\u00edt\u00ed, vyva\u017eov\u00e1n\u00edm z\u00e1t\u011b\u017ee nebo se starat o to, jak\u00fd typ procesoru je pro jejich pracovn\u00ed z\u00e1t\u011b\u017e ide\u00e1ln\u00ed. Tady se posouv\u00e1me nahoru po pyramid\u011b k PaaS.<\/p>\n

<\/p>\n

2.2 Platforma jako slu\u017eba (PaaS)<\/h4>\n

<\/p>\n

PaaS zahrnuje pouze poskytovatele cloudov\u00fdch slu\u017eeb, kter\u00fd nab\u00edz\u00ed ur\u010ditou platformu, na kter\u00e9 mohou u\u017eivatel\u00e9 vytv\u00e1\u0159et aplikace. Je to abstrakce nad IaaS, co\u017e znamen\u00e1, \u017ee poskytovatel cloudu se star\u00e1 o v\u0161echny detaily typ\u016f CPU, pam\u011bti, RAM, \u00falo\u017ei\u0161t\u011b, s\u00edt\u00ed atd. Jak je zn\u00e1zorn\u011bno na obr\u00e1zku 2, vy, jako klient, m\u00e1te malou kontrolu nad skute\u010dnou platformou, proto\u017ee poskytovatel cloudu se star\u00e1 o v\u0161echny detaily infrastruktury za v\u00e1s. Po\u017eadujete vybranou platformu a stav\u00edte na n\u00ed projekt. P\u0159\u00edkladem PaaS je Heroku.<\/p>\n

<\/p>\n

Pro n\u011bkoho m\u016f\u017ee b\u00fdt tato \u00farove\u0148 p\u0159\u00edli\u0161 vysok\u00e1, proto\u017ee nemus\u00ed m\u00edt z\u00e1jem o vytv\u00e1\u0159en\u00ed projektu na uveden\u00e9 platform\u011b, ale sp\u00ed\u0161e pot\u0159ebuje sadu slu\u017eeb p\u0159\u00edmo od poskytovatele cloudov\u00fdch slu\u017eeb. Zde p\u0159ich\u00e1z\u00ed na sc\u00e9nu SaaS.<\/p>\n

<\/p>\n

2.3 Software jako slu\u017eba (SaaS)<\/h4>\n

<\/p>\n

SaaS p\u0159edstavuje nejroz\u0161\u00ed\u0159en\u011bj\u0161\u00ed slu\u017eby nab\u00edzen\u00e9 poskytovateli cloudov\u00fdch slu\u017eeb. Jsou ur\u010deny pro koncov\u00e9 u\u017eivatele a jsou dostupn\u00e9 p\u0159edev\u0161\u00edm prost\u0159ednictv\u00edm webov\u00fdch str\u00e1nek, jako nap\u0159\u00edklad Gmail, Google Docs, Dropbox atd. Co se t\u00fd\u010de Google Cloud, existuje n\u011bkolik nab\u00eddek mimo jejich v\u00fdpo\u010detn\u00ed stack, kter\u00e9 jsou SaaS. Pat\u0159\u00ed sem Data Studio, Big Query atd.<\/p>\n

<\/p>\n

2.4 Shrnut\u00ed cloudov\u00fdch slu\u017eeb<\/h4>\n

<\/p>\n

Slo\u017eky
\nIaaS
\nPaaS
\nSaaS<\/p>\n

Co z\u00edsk\u00e1te
\nZ\u00edsk\u00e1te infrastrukturu a plat\u00edte podle toho. Svobodu pou\u017e\u00edvat nebo instalovat jak\u00fdkoli software, OS nebo jejich kombinaci.
\nZde z\u00edsk\u00e1te to, co po\u017eadujete. Software, hardware, OS, webov\u00e9 prost\u0159ed\u00ed. Z\u00edsk\u00e1te p\u0159ipravenou platformu k pou\u017eit\u00ed a plat\u00edte podle toho.
\nZde se nemus\u00edte o nic starat. Je v\u00e1m poskytnut p\u0159edinstalovan\u00fd bal\u00ed\u010dek p\u0159izp\u016fsoben\u00fd va\u0161im po\u017eadavk\u016fm, a vy u\u017e jen plat\u00edte podle toho.<\/p>\n

Hodnota
\nZ\u00e1kladn\u00ed \u00farove\u0148 v\u00fdpo\u010dt\u016f
\n\u0160pi\u010dka IaaS
\nTo je v podstat\u011b kompletn\u00ed bal\u00ed\u010dek slu\u017eeb<\/p>\n

Technick\u00e9 slo\u017eitosti
\nJsou pot\u0159ebn\u00e9 technick\u00e9 znalosti
\nM\u00e1te z\u00e1kladn\u00ed konfiguraci, ale st\u00e1le jsou nutn\u00e9 znalosti oboru.
\nNemus\u00edte se starat o technick\u00e9 detaily. Poskytovatel SaaS poskytuje v\u0161e.<\/p>\n

S \u010d\u00edm pracuje
\nVirtu\u00e1ln\u00ed stroje, \u00falo\u017ei\u0161t\u011b, servery, s\u00ed\u0165, vyva\u017eova\u010de z\u00e1t\u011b\u017ee atd.
\nProst\u0159ed\u00ed b\u011bhu (jako java runtime), datab\u00e1ze (jako mySQL, Oracle), webov\u00e9 servery (jako tomcat atd.)
\nAplikace jako po\u0161tovn\u00ed slu\u017eby (Gmail, Yahoo Mail atd.), webov\u00e9 str\u00e1nky pro soci\u00e1ln\u00ed interakci (Facebook atd.)<\/p>\n

Graf popularity
\nPopul\u00e1rn\u00ed mezi vysoce kvalifikovan\u00fdmi v\u00fdvoj\u00e1\u0159i, v\u00fdzkumn\u00edky, kte\u0159\u00ed pot\u0159ebuj\u00ed p\u0159izp\u016fsoben\u00ed podle sv\u00fdch po\u017eadavk\u016f nebo oblasti v\u00fdzkumu
\nNejpopul\u00e1rn\u011bj\u0161\u00ed mezi v\u00fdvoj\u00e1\u0159i, proto\u017ee se mohou soust\u0159edit na v\u00fdvoj sv\u00fdch aplikac\u00ed nebo skript\u016f. Nemus\u00ed se starat o z\u00e1t\u011b\u017eov\u00fd provoz nebo spr\u00e1vu serveru atd.
\nNejpopul\u00e1rn\u011bj\u0161\u00ed mezi b\u011b\u017en\u00fdmi spot\u0159ebiteli nebo firmami, kter\u00e9 pou\u017e\u00edvaj\u00ed software jako e-mail, sd\u00edlen\u00ed soubor\u016f, soci\u00e1ln\u00ed s\u00edt\u011b, proto\u017ee se nemus\u00ed starat o technick\u00e9 detaily<\/p>\n

<\/p>\n

Obr\u00e1zek 3: P\u0159ehled hlavn\u00edch cloudov\u00fdch nab\u00eddek | Obr\u00e1zek poskytnut Amir na Blog Specia<\/a><\/noindex><\/em><\/p>\n

<\/p>\n

3. V\u00fdpo\u010detn\u00ed bal\u00ed\u010dek Google Cloud Platform<\/h2>\n

<\/p>\n

Po zv\u00e1\u017een\u00ed typick\u00fdch nab\u00eddek cloudov\u00fdch poskytovatel\u016f v sekci 2 m\u016f\u017eeme je porovnat s nab\u00eddkami Google Cloud.<\/p>\n

<\/p>\n

3.1 Google Compute Engine (GCE) \u2014 IaaS<\/h4>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

Obr\u00e1zek 4: Ikona Google Compute Engine (GCE)<\/em><\/p>\n

<\/p>\n

GCE je IaaS nab\u00eddka od Google. S GCE m\u016f\u017eete voln\u011b vytv\u00e1\u0159et virtu\u00e1ln\u00ed stroje, distribuovat procesorov\u00e9 a pam\u011b\u0165ov\u00e9 zdroje, vyb\u00edrat typ \u00falo\u017ei\u0161t\u011b, nap\u0159\u00edklad SSD nebo HDD, a tak\u00e9 objem pam\u011bti. Je to t\u00e9m\u011b\u0159 jako byste si vytvo\u0159ili sv\u016fj vlastn\u00ed po\u010d\u00edta\u010d\/pracovn\u00ed stanici a zab\u00fdvali se v\u0161emi detaily jeho provozu.<\/p>\n

<\/p>\n

V GCE si m\u016f\u017eete vybrat od mikro instanc\u00ed s 0,3 j\u00e1drov\u00fdmi procesory a 1 GB RAM po 96-j\u00e1drov\u00e9 monstra s v\u00edce ne\u017e 300 GB RAM. M\u016f\u017eete tak\u00e9 vytv\u00e1\u0159et virtu\u00e1ln\u00ed stroje na m\u00edru pro sv\u00e9 pracovn\u00ed z\u00e1t\u011b\u017ee. Pro ty, kter\u00e9 to zaj\u00edm\u00e1 \u2014 jsou to virtu\u00e1ln\u00ed stroje, kter\u00e9 si m\u016f\u017eete sestavit.<\/p>\n

<\/p>\n

Typy stroj\u016f | Dokumentace Compute Engine | Google Cloud<\/a><\/noindex><\/p>\n

<\/p>\n

3.2. Google Kubernetes Engine (GKE) \u2014 (CaaS \/ KaaS)<\/h4>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

Obr\u00e1zek 5: Ikona Google Kubernetes Engine (GKE)<\/em><\/p>\n

<\/p>\n

GKE je jedine\u010dn\u00e1 v\u00fdpo\u010detn\u00ed nab\u00eddka od GCP, kter\u00e1 p\u0159edstavuje abstrakci nad Compute Engine. Obecn\u011bji lze GKE za\u0159adit do kategorie \"Kontejner jako slu\u017eba\" (CaaS), n\u011bkdy naz\u00fdvan\u00e9 \"Kubernetes jako slu\u017eba\" (KaaS), co\u017e umo\u017e\u0148uje z\u00e1kazn\u00edk\u016fm snadno spou\u0161t\u011bt sv\u00e9 Docker kontejnery v pln\u011b spravovan\u00e9m prost\u0159ed\u00ed Kubernetes. Pro ty, kte\u0159\u00ed nejsou obezn\u00e1meni s kontejnery, kontejnery pom\u00e1haj\u00ed modul\u00e1rn\u011b tvo\u0159it slu\u017eby\/aplikace, tak\u017ee r\u016fzn\u00e9 kontejnery mohou obsahovat r\u016fzn\u00e9 slu\u017eby, nap\u0159\u00edklad jeden kontejner m\u016f\u017ee hostit u\u017eivatelsk\u00e9 rozhran\u00ed va\u0161\u00ed webov\u00e9 aplikace a jin\u00fd m\u016f\u017ee obsahovat jej\u00ed serverovou \u010d\u00e1st. Kubernetes prov\u00e1d\u00ed automatizaci, koordinaci, spr\u00e1vu a nasazen\u00ed va\u0161ich kontejner\u016f. V\u00edce informac\u00ed zde.<\/p>\n

<\/p>\n

Google Kubernetes Engine | Google Cloud<\/a><\/noindex><\/p>\n

<\/p>\n

3.3 Google App Engine (GAE) \u2014 (PaaS)<\/h4>\n

<\/p>\n

\"GCP:<\/p>\n

<\/p>\n

Obr\u00e1zek 6: Ikona Google App Engine (GAE)<\/em><\/p>\n

<\/p>\n

Jak bylo zm\u00edn\u011bno v \u010d\u00e1sti 2.2, PaaS je nad IaaS, a v p\u0159\u00edpad\u011b GCP lze tuto nab\u00eddku tak\u00e9 pova\u017eovat za nad GKE. GAE je specializovan\u00fd Google PaaS a jak se sami nejl\u00e9pe popisuj\u00ed \u2014 \"p\u0159ineste sv\u016fj k\u00f3d a my se postar\u00e1me o zbytek\". <\/p>\n

<\/p>\n

To zaji\u0161\u0165uje, \u017ee z\u00e1kazn\u00edci pou\u017e\u00edvaj\u00edc\u00ed GAE se nemus\u00ed zab\u00fdvat z\u00e1kladn\u00edm hardwarem\/softwarovou architekturou a mohou m\u00edt p\u0159edem nastavenou platformu p\u0159ipravenou k pou\u017eit\u00ed; v\u0161e, co mus\u00ed ud\u011blat, je poskytnout k\u00f3d, kter\u00fd pot\u0159ebuj\u00ed k jej\u00edmu spu\u0161t\u011bn\u00ed. <\/p>\n

<\/p>\n

GAE automaticky zpracov\u00e1v\u00e1 \u0161k\u00e1lov\u00e1n\u00ed, aby vyhov\u011blo z\u00e1t\u011b\u017ei a popt\u00e1vce ze strany u\u017eivatel\u016f, co\u017e znamen\u00e1, \u017ee pokud v\u00e1\u0161 web prod\u00e1vaj\u00edc\u00ed kv\u011btiny n\u00e1hle dos\u00e1hne vrcholu, proto\u017ee se bl\u00ed\u017e\u00ed Valent\u00fdn, GAE se postar\u00e1 o \u0161k\u00e1lov\u00e1n\u00ed z\u00e1kladn\u00ed infrastruktury, aby splnilo popt\u00e1vku a zajistilo, \u017ee va\u0161e webov\u00e1 str\u00e1nka nespadne kv\u016fli zv\u00fd\u0161en\u00e9 popt\u00e1vce. To znamen\u00e1, \u017ee plat\u00edte pouze za ty zdroje, kter\u00e9 va\u0161e aplikace v danou chv\u00edli pot\u0159ebuje.<\/p>\n

<\/p>\n

GAE pou\u017e\u00edv\u00e1 Kubernetes nebo jeho integrovanou verzi, aby se s t\u00edmto v\u0161\u00edm vyrovnalo, abyste se o to nemuseli starat. GAE je nejvhodn\u011bj\u0161\u00ed pro firmy, kter\u00e9 nemaj\u00ed z\u00e1jem o z\u00e1kladn\u00ed infrastrukturu a zaj\u00edmaj\u00ed se pouze o to, aby byla jejich aplikace co nejl\u00e9pe dostupn\u00e1.<\/p>\n

<\/p>\n

Podle m\u00e9ho n\u00e1zoru je GAE nejlep\u0161\u00ed m\u00edsto pro start, pokud jste v\u00fdvoj\u00e1\u0159 s skv\u011bl\u00fdm n\u00e1padem, ale nechcete se zab\u00fdvat rutinn\u00edmi \u00fakoly jako je nastaven\u00ed server\u016f, vyva\u017eov\u00e1n\u00ed z\u00e1t\u011b\u017ee a dal\u0161\u00edmi pracemi spojen\u00fdmi s devops\/SRE. \u010casem byste mohli vyzkou\u0161et GKE a GCE, ale to je jen m\u016fj n\u00e1zor.<\/p>\n

<\/p>\n

Vylou\u010den\u00ed odpov\u011bdnosti<\/em><\/strong>: AppEngine se pou\u017e\u00edv\u00e1 pro webov\u00e9 aplikace, nikoli pro mobiln\u00ed aplikace.<\/p>\n

<\/p>\n

Pro sezn\u00e1men\u00ed<\/em><\/strong>: App Engine \u2013 Vytv\u00e1\u0159ejte \u0161k\u00e1lovateln\u00e9 webov\u00e9 a mobiln\u00ed backendy v jak\u00e9mkoli jazyce | Google Cloud<\/a><\/noindex><\/p>\n

<\/p>\n

3.4 Google Cloud Functions \u2013 (FaaS)<\/h4>\n

<\/p>\n

\"GCP: <\/p>\n

<\/p>\n

Obr\u00e1zek 7: Ikona Google Cloud Functions (GCF)<\/em><\/p>\n

<\/p>\n

Douf\u00e1m, \u017ee jste si v\u0161imli trendu p\u0159i anal\u00fdze p\u0159edchoz\u00edch n\u00e1vrh\u016f. \u010c\u00edm v\u00fd\u0161e stoup\u00e1te po \u017eeb\u0159\u00ed\u010dku v\u00fdpo\u010detn\u00edch \u0159e\u0161en\u00ed GCP, t\u00edm m\u00e9n\u011b se mus\u00edte ob\u00e1vat z\u00e1kladn\u00edch technologi\u00ed. Tato pyramida kon\u010d\u00ed nejmen\u0161\u00ed mo\u017enou jednotkou v\u00fdpo\u010dtu, funkc\u00ed, jak je uvedeno v odd\u00edle 1.<\/p>\n

<\/p>\n

GCF je relativn\u011b novou nab\u00eddkou GCP, kter\u00e1 je st\u00e1le v beta testov\u00e1n\u00ed (v dob\u011b psan\u00ed tohoto \u010dl\u00e1nku). Cloudov\u00e9 funkce umo\u017e\u0148uj\u00ed ur\u010dit\u00fdm funkc\u00edm napsan\u00fdm v\u00fdvoj\u00e1\u0159em spou\u0161t\u011bt se na z\u00e1klad\u011b ur\u010dit\u00e9 ud\u00e1losti. <\/p>\n

<\/p>\n

Jsou \u0159\u00edzeny ud\u00e1lostmi a le\u017e\u00ed v z\u00e1kladu m\u00f3dn\u00edho slova \u201ebezserverov\u00fd\u201c, co\u017e znamen\u00e1, \u017ee neznaj\u00ed servery. Cloudov\u00e9 funkce jsou velmi jednoduch\u00e9 a maj\u00ed mnoho r\u016fzn\u00fdch vyu\u017eit\u00ed, kter\u00e9 vy\u017eaduj\u00ed my\u0161len\u00ed zam\u011b\u0159en\u00e9 na ud\u00e1losti. Nap\u0159\u00edklad poka\u017ed\u00e9, kdy\u017e se zaregistruje nov\u00fd u\u017eivatel, m\u016f\u017ee se spustit cloudov\u00e1 funkce, aby upozornila v\u00fdvoj\u00e1\u0159e. <\/p>\n

<\/p>\n

Na v\u00fdrobn\u011b, kdy\u017e ur\u010dit\u00fd senzor dos\u00e1hne ur\u010dit\u00e9 hodnoty, m\u016f\u017ee spustit cloudovou funkci, kter\u00e1 prov\u00e1d\u00ed ur\u010dit\u00e9 zpracov\u00e1n\u00ed informac\u00ed nebo informuje n\u011bjak\u00fd obslu\u017en\u00fd person\u00e1l atd.<\/p>\n

<\/p>\n

Cloudov\u00e9 funkce \u2013 \u0159\u00edzen\u00e9 ud\u00e1lostmi serverov\u00e9 v\u00fdpo\u010dty | Google Cloud<\/a><\/noindex><\/p>\n

<\/p>\n

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

<\/p>\n

V tomto \u010dl\u00e1nku jsme hovo\u0159ili o r\u016fzn\u00fdch cloudov\u00fdch nab\u00eddk\u00e1ch, jako je IaaS, PaaS atd., a o tom, jak googleov\u00e1 v\u00fdpo\u010detn\u00ed architektura implementuje tyto r\u016fzn\u00e9 \u00farovn\u011b. Vid\u011bli jsme, \u017ee \u00farovn\u011b abstrakce p\u0159i p\u0159echodu z jedn\u00e9 kategorie slu\u017eeb do druh\u00e9, nap\u0159\u00edklad z IaaS na PaaS, vy\u017eaduj\u00ed m\u00e9n\u011b znalost\u00ed o z\u00e1kladn\u00ed technologii.<\/p>\n

<\/p>\n

Pro podnik\u00e1n\u00ed to poskytuje kritickou flexibilitu, kter\u00e1 nejen odpov\u00edd\u00e1 jeho operativn\u00edm c\u00edl\u016fm, ale tak\u00e9 uspokojuje dal\u0161\u00ed kl\u00ed\u010dov\u00e9 oblasti, jako je bezpe\u010dnost a n\u00e1klady. Obecn\u011b \u0159e\u010deno:<\/p>\n

<\/p>\n

Compute Engine<\/em><\/strong> \u2014 umo\u017e\u0148uje v\u00e1m vytvo\u0159it si vlastn\u00ed virtu\u00e1ln\u00ed stroj, kter\u00fd vy\u010dle\u0148uje ur\u010dit\u00e9 hardwarov\u00e9 zdroje, nap\u0159\u00edklad RAM, procesor a \u00falo\u017ei\u0161t\u011b. Je tak\u00e9 dost praktick\u00fd a n\u00edzko\u00farov\u0148ov\u00fd.<\/p>\n

<\/p>\n

Kubernetes Engine<\/em><\/strong> \u2014 to je krok d\u00e1l oproti Compute Engine, kter\u00fd v\u00e1m umo\u017e\u0148uje pou\u017e\u00edvat Kubernetes a kontejnery pro spr\u00e1vu va\u0161\u00ed aplikace, co\u017e umo\u017e\u0148uje jej\u00ed \u0161k\u00e1lov\u00e1n\u00ed, pokud je to pot\u0159eba.<\/p>\n

<\/p>\n

App Engine<\/em><\/strong> \u2014 to je krok d\u00e1l oproti Kubernetes Engine, kter\u00fd v\u00e1m umo\u017e\u0148uje soust\u0159edit se pouze na v\u00e1\u0161 k\u00f3d, zat\u00edmco Google zaji\u0161\u0165uje v\u0161echny po\u017eadavky z\u00e1kladn\u00ed platformy.<\/p>\n

<\/p>\n

Cloud-Functions<\/em><\/strong> \u2014 to je vrchol v\u00fdpo\u010detn\u00ed pyramidy, kter\u00fd umo\u017e\u0148uje napsat jednoduchou funkci, kter\u00e1 p\u0159i spu\u0161t\u011bn\u00ed vyu\u017e\u00edv\u00e1 celou z\u00e1kladn\u00ed infrastrukturu pro v\u00fdpo\u010dty a vrac\u00ed v\u00fdsledek.<\/p>\n

<\/p>\n

D\u011bkujeme za pozornost!<\/h1>\n

<\/p>\n

Twitter: @martinomburajr<\/a><\/noindex><\/p>\n

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

\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u044c\u043d\u043e \u0434\u043b\u044f \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043a\u0443\u0440\u0441\u0430 \u00ab\u041e\u0431\u043b\u0430\u0447\u043d\u044b\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u044b\u00bb. \u0418\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u0442\u044c\u0441\u044f \u0432 \u0434\u0430\u043d\u043d\u043e\u043c \u043d\u0430\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0438? \u0421\u043c\u043e\u0442\u0440\u0438\u0442\u0435 \u0437\u0430\u043f\u0438\u0441\u044c \u043f\u0440\u043e\u0444\u0435\u0441\u0441\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043c\u0430\u0441\u0442\u0435\u0440-\u043a\u043b\u0430\u0441\u0441\u0430 \u00abAWS EC2 \u0441\u0435\u0440\u0432\u0438\u0441\u00bb, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u0440\u043e\u0432\u0451\u043b \u0415\u0433\u043e\u0440 \u0417\u0443\u0435\u0432 \u2014 TeamLead \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 InBit \u0438 \u0430\u0432\u0442\u043e\u0440 \u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0439 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u044b \u0432 OTUS. Google Cloud Platform (GCP) \u043f\u0440\u0435\u0434\u043b\u0430\u0433\u0430\u0435\u0442 \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, \u0438 \u0432 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u0432\u044b\u0447\u0438\u0441\u043b\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0439 \u0441\u0442\u0435\u043a, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442 Google Compute Engine (GCE), Google […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28699,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38233","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\udd47GCP: Rozbor v\u00fdpo\u010detn\u00edho stacku Google Cloud Platform | ProHoster","description":"P\u0159eklad \u010dl\u00e1nku byl p\u0159ipraven speci\u00e1ln\u011b pro studenty kurzu \u201eCloudov\u00e9 slu\u017eby\u201c. Zaj\u00edm\u00e1 v\u00e1s rozv\u00edjet se v t\u00e9to oblasti.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/gcp-razbor-vychislitelnogo-steka-google-cloud-platform","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\udd47GCP: \u0420\u0430\u0437\u0431\u043e\u0440 \u0432\u044b\u0447\u0438\u0441\u043b\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 Google Cloud Platform | ProHoster","og:description":"\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u044c\u043d\u043e \u0434\u043b\u044f \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043a\u0443\u0440\u0441\u0430 \u00ab\u041e\u0431\u043b\u0430\u0447\u043d\u044b\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u044b\u00bb. \u0418\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u0442\u044c\u0441\u044f \u0432 \u0434\u0430\u043d\u043d\u043e\u043c.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/gcp-razbor-vychislitelnogo-steka-google-cloud-platform","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:22:28+00:00","article:modified_time":"2019-10-31T19:22:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38233","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-23 21:03:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:13:22","updated":"2026-01-23 21:03:19","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\/38233","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=38233"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/38233\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28699"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=38233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=38233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=38233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}