I-Cloud computing ichaziwe: imiqondo engu-11 yokwakhiwa okufanele uyazi (4K Masterclass).

Lokho okuhlanganiswa yile vidiyo

• - I-Architecture Wall & Master Blueprint
• - 01. I-Vertical vs. Horizontal Scaling
• - 02. I-Load Balancing Architecture (L4 vs. L7 & Health Checks)
• - 03. I-Autoscaling & Elasticity
• - 04. I-Serverless (FaaS & Firecracker MicroVMs)

Umbhalo obhaliwe ohunyushwe

Kuhunyushwe kusuka ekulandiseni kokuqala kwesiNgisi. Umsindo namazwibela atholakalayo alawulwa yi-YouTube.

- I-Architecture Wall & Master Blueprint

0:00 Wonke unjiniyela wesofthiwe ekugcineni ubhekana nodonga lwe-cloud architecture. Uyakha uhlelo kukhompyutha yakho ephathekayo, uyidlulisele ekukhiqizeni, futhi ngesikhathi kufika abasebenzisi bangempela, amaseva ayawa, uxhumano lwedatha luyaphela, futhi isikweletu sakho se-AWS sibukeka njengenombolo yocingo. Onjiniyela abaningi bazama ukuxazulula ubunjiniyela befu ngokubamba ngekhanda izifinyezo zemikhiqizo eyahlukene engamakhulu amathathu ye-AWS. Kodwa i-cloud computing yangempela ayigcini nje ngokubamba ngekhanda izincwadi zombhali: yakhelwe phezu kwemigomo eyishumi nanye eyisisekelo yokwakha.

0:34 Kule masterclass, sizodlula kuhlelo lonke lwebhizinisi: kusukela ekulinganiseni nasekulinganiseni umthwalo kuya ku-serverless, ukwehlisa okuqhutshwa imicimbi, izinhlelo zokugcina, kanye nokuxhumana kwefu. Kahle le migomo eyishumi nanye, futhi ungaklama noma yimuphi umgogodla ku-AWS, I-GCP, noma i-Azure. Lena i-The Daily Diff, ngaphansi kwendawo.

- 01. I-Vertical vs. Horizontal Scaling

0:57 Umcabango wokuqala: I-Scaling. Lapho uhlelo lwakho lubona ukukhula kwethrafikhi, unezindlela ezimbili ezihluke ngokuyisisekelo zokusingatha umthwalo: ukulinganisa okuqondile, noma ukulinganisa okuphambene. Ukulinganisa okuqondile, noma ukukhulisa, kusho ukuthatha umshini wakho okhona bese wengeza izinsiza eziningi: ukuthuthukisa kusuka kumacores amane e-CPU kuya kwamashumi amathathu nambili, noma ukushintshanisa ama-gigabytes angamashumi amathathu nambili e-RAM ngo- ikhulu namashumi amabili nesishiyagalombili. Ukulinganisa okuqondile akudingi izinguquko ekwakhiweni: ikhodi yakho

1:28 nedatha ihlala ifana ncamashi. Kodwa ishaya isilinganiso esinzima sezingxenyekazi zekhompuyutha. Awukho umshini owodwa emhlabeni onamacores ayishumi ezinkulungwane e-CPU, futhi izibonelo ezisezingeni eliphezulu zineprimiyamu yentengo ephindaphindwayo. Ukulinganisa okuphambene, noma ukukhulisa, kusho ukugcina amaseva akho emancane futhi anentengo ephansi, kodwa usebenzisa izibonelo eziningi ngokuhambisana ngemuva kwerouter. Uma isibonelo esisodwa siwa, amanodi asele amunca ithrafikhi ngesikhathi sokusebenza esingalingani. Umthetho wegolide wokulinganisa okuphambene

2:01 ukungenasimo: amaseva ohlelo lwakho awafanele agcine izikhathi zabasebenzisi, amafayela alayishiwe, noma isimo kuma-disks abo asendaweni. Isimo kufanele sibe kusizindalwazi sangaphandle noma i-cache, okuphonsa noma iyiphi inodi ukusingatha noma isiphi isicelo somsebenzisi.

- 02. I-Load Balancing Architecture (L4 vs. L7 & Health Checks)

2:17 Umcabango wesibili: Ukulinganisa Umthwalo. Ukulinganisa okuphambene kuzwakala kukuhle ephepheni, kodwa kulethe inkinga esheshayo: lapho izinkulungwane eziyishumi zabasebenzisi zishaya igama lakho lesizinda, yiliphi iseva elithola ithrafikhi yabo? I-load balancer isebenza njenge-reverse proxy ehlezi phakathi kwe-inthanethi yomphakathi nebhakendi lakho eliyimfihlo. Iyamukela uxhumano olungenayo lwe-TCP noma i-HTTP futhi ihambisa izicelo kuzo zonke izibonelo zakho eziphilile.

2:47 Ama-load balancers asebenza ezingeni ezimbili eziyinhloko zenethiwekhi. I-Layer 4 Network Load Balancers isebenza ezingeni lokuhambisa, ihambisa amaphakethe e-TCP nawe-UDP aluhlaza ngokuya ngekheli le-IP kanye nembobo ngesikhathi sokulibaziseka kwemicrosecond nezicelo eziyizigidi ngomzuzwana. I-Layer 7 Application Load Balancers ihlola iprotocol ye-HTTP uquqobo: ifunda izindlela ze-URL, izihloko zesicelo, amakhukhi, nezindlela ze-HTTP. Lokhu kunika amandla ukuhambisa okusekelwe endleleni: ukuthumela izicelo ze-slash-api ku-backend yakho kanye nezicelo ze-slash-static esitolo sezinto.

3:25 Okubalulekile, ama-load balancers enza izindlela zokuhlola impilo ezisebenzayo. Njalo ngemizuzwana embalwa, i-balancer iyathumela i-ping ekugcineni kwezempilo kuzo zonke izibonelo. Uma isibonelo siphonsa amaphutha angamakhulu amahlanu alandelanayo kathathu noma sehluleka ukuphendula, sikhishwa ngokuzenzakalelayo eqenjini ngaphandle kwezicelo eziwisiwe.

- 03. I-Autoscaling & Elasticity

3:45 Umcabango wesithathu: I-Autoscaling. Uma uhlelo lwakho lwe-web ludinga amaseva amabili ngo-3 ekuseni, kodwa amaseva angamashumi amabili ngesikhathi sokwethula emini, ukuchofoza izinkinobho mathupha ku- console yefu kuyindlela eqinisekisiwe yokwehla nokubhujiswa. I-Autoscaling iletha ukuguquguquka okunamandla kuma-server pool amaphambili. I-Auto Scaling Group ihlola izilinganiso zokusebenza njengokusetshenziswa kwe-CPU okuphakathi, i-I-O yenethiwekhi, noma ukugcina okusalindile ubude. Lapho i-CPU emaphakathi idlula umkhawulo ochaziwe — isibonelo,

4:19 amaphesenti angamashumi ayisikhombisa imizuzu emithathu elandelanayo — i-autoscaler ngokuzenzakalelayo iqala imishini emisha ebonakalayo, iyabhalisa ne-load balancer yakho, futhi iqala ukuhambisa ithrafikhi. Okubaluleke ngokulinganayo ukukhulisa: lapho igagasi lethrafikhi lincipha, i-autoscaler iyawaphelisa amabala amaningi ukuze uyeke ukukhokhela ukubala okungasetshenziswa. Ukuvimbela ukuphaphama — lapho amaseva adalwa ngokushesha futhi abhujiswa kulungele okungapheli — abaklami befu balungiselela izikhathi zokuphumula. Umcabango wesine: I-Serverless.

- 04. I-Serverless (FaaS & Firecracker MicroVMs)

4:53 Sekuyiminyaka eminingi, amaqembu okumaketha ayephakamisa i-serverless njengekhodi yomlingo egijima esibhakabhakeni. Eqinisweni, i-serverless isasebenzisa amaseva — kodwa awuwona, awuwalungisi, noma awukhokhi ngawo uma kungekho khodi egijima. Nge-Function-as-a-Service njenge-AWS Lambda noma i-Google Cloud Functions, ubhalela umsebenzi wokuphatha ozimele. Lapho isicelo se-HTTP, ukulayishwa kwefayela le-S3, noma ushintsho kusizindalwazi kwenzeka, isikhathi sokugijima sefu siqala i-ephemeral

5:23 i-micro-virtual-machine njenge-Firecracker ngaphansi kwemizuzu emihlanu. Ikhodi yakho iyagijima, ibuyise impendulo, bese iyacima. Uma kungekho muntu ovakashela iwebhusayithi yakho izinyanga ezintathu, isikweletu sakho sokubala singu- amadola ayiziro namasenti ayiziro. Uma abasebenzisi abayisigidi beyishaya ngesikhathi esisodwa, umhlinzeki uqala isigidi sama-microVMs ahambisanayo. Ukushintshaniswa kobunjiniyela kuyiqiniso: ukulibaziseka kokuqala okubandayo lapho kuqala izikhathi zokugijima ezintsha, umkhawulo wokugijima wemizuzu eyishumi nanhlanu ku-Lambda, nokungabi nasimo okuqinile.

5:55 I-Serverless ayinqandeki emishinini yemicimbi nama-API ayindlala, kodwa imbi kuma-WebSockets aqhubekayo noma izikhathi zokuqeqesha zamahora amaningi.

- 05. I-Event-Driven Architecture (EDA & Decoupling)

6:05 Umcabango wesihlanu: I-Event-Driven Architecture, noma i-EDA. Ezinhlelweni zendabuko, izinsizakalo zixhumana ngesikhathi esifanayo. Isevisi yakho yokukhokha ibiza inkokhelo, inkokhelo ibiza isitolo, isitolo sibiza ukukhwabanisa, futhi ukukhwabanisa kubiza i-imeyili. Lokhu kudala ukuwa okufanayo kokufa. Uma umhlinzeki we-imeyili ovela eceleni ebona ukuphazamiseka kwenethiwekhi futhi kuthatha imizuzwana eyishumi ukuphendula, isicelo sokukhokha sonke sekhasimende sakho siphela isikhathi ngokuphutha. Ekwakhiweni okugunyazwa umcimbi, izinsizakalo azixhunyiwe ngokuphelele.

6:37 Lapho ikhasimende lichofoza ukuthenga, isevisi yokukhokha ayibizi izinsizakalo ezengezwayo. Kumane ishicilele umcimbi obizwa ngokuthi i-OrderPlaced kuyi-Event Bus emaphakathi njenge-Amazon EventBridge noma isihloko se-SNS. Ukukhokha kuqedwa ngemizuzu engamashumi amahlanu. Abasebenzi abezansi benkokhelo, ukunciphisa isitoko, kanye namarisidi e-imeyili badonsa imilayezo ngokuzimele kuma-SQS queues abo. Uma isevisi ye-imeyili ihluleka isikhathi esiyihola, imilayezo ilinda ngokuphepha ibhafiwe kulayini ngaphandle kokwehla kwe-oda elilodwa.

- 06. I-Container Orchestration (Docker & Kubernetes)

7:13 Umcabango wesithupha: I-Container Orchestration. I-Docker ixazulule ukupakisha: ihlanganisa ikhodi yohlelo lwakho, imithombo yolwazi yesistimu, ukucushwa, kanye nesikhathi sokugijima ibe yisithombe esingashintsheki esisebenza ngokufana ku-MacBook yakho nasefuyeni. Kodwa ukupakisha isitsha kulula. Ukusebenzisa iziqukathi ezingamakhulu amahlanu kumishini ebonakalayo engamashumi amahlanu yilapho ubunjiniyela buwohloka khona. Kungakho iziqondisi zeziqukathi njenge-Kubernetes ne-AWS ECS

7:41 zikhona. Umqondisi unikeza indawo yokulawula: iseva ye-API, isitolo sesimo se-etcd, kanye nomhleli ohlakaniphile. Uyamemezela isimo sakho osifunayo: Ngifuna ama-replicas ayishumi esevisi yami yokuqinisekisa ngamagigabyte amabili e-RAM ngalinye. Umhleli uhlola iqoqo, ubeka ama-pods kuma-nodes anomemori okhululekile, ulungiselela inethiwekhi yangaphakathi, futhi uqhubeka nokuvumelanisa iqiniso. Uma i-node ihlupheka ngenxa yokwehluleka kwezingxenyekazi zekhompuyutha, i-Kubernetes iyathola ukulahlekelwa futhi ngokushesha ihlela kabusha wonke ama-pods asusiwe kuma-

- 07. Izinsika ezi-4 ze-Cloud Storage (S3, EBS, DBs & Redis)

8:16 nodes aphilile. Umcabango wesikhombisa: I-Cloud Storage Hierarchy. Abasaqalayo bavame ukuthatha i-cloud storage njengebhakede elilodwa lapho ukhulula khona amafayela. Ekuklameni okukhiqizayo, ukugcina kuhlukaniswa kube izinsika ezine ezihlukene ngokusekelwe kumaphethini okufinyelela nesikhathi sokulibaziseka. Okokuqala yi-Object Storage, njenge-Amazon S3 noma i-Google Cloud Storage. Ufinyelela amafayela ngama-API e-HTTP REST usebenzisa izingcingo ezilula ze-PUT ne-GET. Inikeza umthamo ongapheli we-horizontal ngamasenti amabili igigabyte ngenyanga,

8:49 okwenza kube kuhle kumavidiyo, ukulayishwa kwabasebenzisi, amalogi, nezibackup. Okwesibili yi-Block Storage, njenge-Amazon EBS. Lawana ama-hard drive abonakalayo afakwe ngqo kumshini othize obonakalayo ngaphezulu kokuxhumana okusheshayo. Ayakhishwa abe amafayela ajwayelekile njenge-ext4, esekela ukufunda nokubhala okungahleliwe okusheshayo okudingwa yi-database izinjini. Okwesithathu ngama-Managed Databases: izinjini ezihlobene njenge-PostgreSQL ku-RDS enikeza ukuthengiselana kwe-ACID namajoyini ayinkimbinkimbi,

9:21 nezinsizakalo ze-NoSQL ezifana ne-DynamoDB eziletha izinombolo ezincane zesikhathi sokulibaziseka ngesikhathi esikhulu. Futhi okwesine ngama-In-Memory Caches njenge-Redis. Ukufunda idatha ku-RAM kuthatha imizuzwana emincane kunasemisebenzini. Ama-Caches ahlala phambi kwesizindalwazi sakho, esivikela ekuthambekeni kokuphindaphindeka kwethrafikhi futhi elawula amathokheni weseshini yomsebenzisi angashintshi.

- 08. I-High Availability & The Nines (Multi-AZ Failover)

9:44 Umcabango wesishiyagalombili: Ukutholakala Okuphezulu, noma i-HA. Ukutholakala kuphendula umbuzo owodwa: mangakanani amaphesenti esikhathi uhlelo lwakho lusebenza futhi lufinyeleleka kubasebenzisi? Ezinkontileka zebhizinisi, ukutholakala kukalwa ngamathathu. Amabili amathathu, noma amaphesenti angamashumi ayisishiyagalolunye nambili okutholakala, avumela izinsuku ezingaphezu kwezintathu nesigamu zokungasebenzi minyaka yonke. Amanye amathathu ehla isikhathi sokungasebenzi sibe imizuzu engamashumi amabili nambili, futhi amahlanu amathathu avumela imizuzu emihlanu yokungasebenzi isiyonke ngonyaka.

10:15 Ukufeza ukutholakala okuphezulu, kufanele uqede amaphuzu okwehluleka kuzo zonke izindawo zokwehluleka. Efuyeni, lokho kusho ukusakaza kuzindawo eziningi zokutholakala. Indawo Yokutholakala akulona ireki elilodwa: yizindawo eziningi ezihlukene zedatha eziphansi amakhilomitha ukude ngamandla namafutha azimele. Ngokusebenzisa izibonelo ezisebenzayo ku-Zone A naku-Zone B ngokulinganisa kwedatha okuvumelanayo, ukushaya kombani noma ukusikwa kwefiber okuthatha indawo yonke ephathekayo kuphumela ekwehlulekeni okuzenzakalelayo.

10:50 ngemizuzwana engamashumi amathathu ngaphandle kokungenelela komuntu.

- 09. I-Durability vs. Availability (Kungani Izikhathi Eziyi-11 Ezingapheli Kungesona Isikhathi Sokusebenza)

10:53 Umqondo wesishiyagalolunye: Ukuqina ngokuqhathaniswa Nokutholakala. Lena iyona caphuni eyodwa ejwayeleke kakhulu yokucabanga ekwakhiweni kwefu izingxoxo. Onjiniyela bavame ukusebenzisa amagama ngokushintshana, kodwa balinganisa izakhiwo ezihluke ngokuphelele. Ukutholakala kulinganisa isikhathi esisebenza: Ngingenza yini ikholi ye-API ukuze ngifunde noma ngibhale idatha yami khona manje? Ukuqina kulinganisa ukulondolozwa: Idatha yami izosinda yini ngaphandle kokulimala unomphela, ukubola kancane, ukoniwa, noma ukubhujiswa eminyakeni eyishumi?

11:24 Bheka i-Amazon S3 Standard. Isivumelwano Sokuvumelana Kwesevisi sinikeza amaphesenti angamashumi ayisishiyagalolunye nesishiyagalolunye namaphesenti ayisishiyagalolunye okutholakala, okuvumela cishe imizuzu engamashumi amane nantathu yokuphazamiseka inyanga ngayinye lapho isicelo se-API singase sibuyisele iphutha elingamakhulu amahlanu. Kodwa i-S3 ithembisa ukugcinwa kweziyisi-11: amaphesenti angamashumi ayisishiyagalolunye nesishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye namaphesenti ayisishiyagalolunye. Uma ugcina amafayela ayizigidi eziyishumi ku-S3, ungalindela ukuthi ulahlekelwe ngokwezibalo

11:56 isilinganiso sefayela elilodwa njalo eminyakeni eyizinkulungwane eziyishumi. I-S3 ikwenza lokhu ngokubhala izinto ngokususa futhi iphinde ikopishe izingxenye phakathi kwezindawo ezingaphansi kwezintathu zezindawo zedatha ezihlukaniswe ngokwendawo. Ngesikhathi sokuphazamiseka okukhulu kwenethiwekhi yesifunda, i-S3 ingase iphele isikhashana ingatholakali, kodwa idatha yakho ayilokothi ibhujiswe.

- 10. I-Infrastructure as Code (Terraform vs. Console Drift)

12:14 Umqondo weshumi: I-Infrastructure as Code, noma i-IaC. Ezinsukwini zokuqala zokubalwa kwamafu, onjiniyela bangena ku-AWS ikhonsoli yokuphatha iwebhu futhi bachofoza mathupha ukuze bakhe i-virtual omishini, baqedele ama-subnet, futhi banamathisele amaqembu okuphepha. Imboni ikubiza lokhu nge-ClickOps, futhi ekukhiqizeni, kuyinto enkulu kakhulu inhlekelele. Izinguquko zekhonsoli ezenziwa mathupha azinayo imininingwane yokucwaninga, akukho ukubuyiselwa emuva indlela, futhi ngokungenakugwenywa kubangela ukuhlukana kokumiswa phakathi kokuhlelwa nezindawo zokukhiqiza. Ngengqalasizinda

12:48 njengamathuluzi ekhodi afana ne-Terraform, I-OpenTofu, i-Pulumi, noma i-AWS CDK, uchaza yonke i-architecture yakho yefu kumafayela okumisa adeklaratha agcinwe ku-Git. Yonke inguquko ekuphathweni okuvulekile noma ikhophi yedatha idlula ku-pull request nokubuyekezwa kontanga. Ukuqalisa uhlelo lwe-terraform kubuka kuqala i-API diff ngaphambi kokuba kuthintwe noma yini, futhi ukuqalisa ikhophi efanayo yokukhiqiza kwakho kuthatha imizuzu emine esikhundleni samaviki amane.

- 11. I-Cloud Networking (VPC, Subnets, NAT & Security Groups)

13:20 Umqondo weshumi nanye: Inethiwekhi Yefu kanye Namafu Abangasese Agunyaziwe. Uma uhambisa amaseva efwini, awahlali eveziwe ku-raw inethiwekhi yomphakathi. Ahlala ngaphakathi komngcele ohlukile ochazwe yisoftware obizwa nge-VPC. Ngaphakathi kwe-VPC yakho, unikeza indawo yekheli le-IP yangasese efana neshumi-dot-zero-dot-zero-dot-zero slash ishumi nesithupha, futhi uyihlukanise ibe ama-subnet omphakathi nawangasese. I-subnet yomphakathi inendawo eqondile eya ku-Internet Gateway.

13:51 Iqukethe izimpahla ezibhekana nomphakathi njenge-Application Load Balancers yakho kanye ne-NAT Ama-Gateways. Iyona kuphela ingxenye yenethiwekhi yakho enama-IP omphakathi amakheli. Amaseva akho ohlelo lokusebenza namadathabase okukhiqiza ahlala ngokuqinile kuma-subnet angasese angenama-IP omphakathi kanye nama-zero inbound routes avela ku- inethiwekhi. Lapho amaseva akho angemuva edinga ukulanda izibuyekezo zokuphepha, ithrafikhi yawo ephumayo idlula ku-NAT Gateway kumphakathi subnet. Ezungeze yonke i-instance kukhona ama-Security Groups: ama-stateful ama-firewall ababonakalayo aphoqa isimiso samalungelo amancane.

- 12. I-Complete Enterprise Blueprint & Verdict

14:28 Iqembu lakho lokuphepha ledathabase lamukela kuphela ukuxhumana ku-port 5432 ngokuqinile kusuka eqenjini lokuphepha lamaseva akho ohlelo lokusebenza, okwenza ukungena kwangaphandle kungenzeki ngokwezibalo. Uma uhlehlisa, lezi zimiso eziyishumi nanye zixhuma zibe uhlelo olulodwa oluhlangene. I-DNS yakho ihamba iye ku-Load Balancer ku-subnet yomphakathi, amaqembu e-autoscaling aphatha ukwanda kwethrafikhi kuma-Availability Zones amaningi, ama-event bus ahlukanisa abasebenzi bangemuva, futhi lonke i-stack yakho ihambiswa kusuka ku-Git kusetshenziswa i-Infrastructure as Code.

15:02 Isinqumo se-masterclass yanamuhla: SHIP IT. Yeka ukubamba ngekhanda amakhulu ama-acronyms okumaketha ifu. Yazi kahle lezi zindlela zokwakha eziyishumi nanye, hlukanisa isimo sakho, futhi wakhe izinhlelo ezingeke zehluleke. Ngitshele ukuthi yimuphi umqondo wefu owakunikeza ikhanda elikhulu kakhulu lapho uqala ukwakha kumazwana. Futhi ukuze uthole iphepha lokukopela eliphelele le-architecture, bhalisela i-newsletter ku-thedailydiff.dev,

15:28 isixhumanisi ngezansi. Futhi lokho kuwumehluko wanamuhla. Ngingu-Niko ovela ku-Axrisi. Hlanganisa ngokuzibophezela.

Imithombo

1. AWS Well-Architected Framework (Reliability & Performance Pillars)aws.amazon.com
2. Kubernetes Architecture & Control Plane Conceptskubernetes.io
3. Martin Fowler: What is Event-Driven Architecture?martinfowler.com
4. Amazon S3 Data Durability & Availability Technical Whitepaperaws.amazon.com
5. HashiCorp: Declarative Infrastructure as Code with Terraformwww.terraform.io