Lesson 1Networking, CDN and edge considerations: VPC design, load balancing, CDN for storefront performanceThis part handles networking and edge planning, like VPC setup, subnets, routing, and load balancing. It also covers CDN and edge caching to boost speed, reliability, and safety for customer services.
VPC, subnet, and routing topologyNorth-south and east-west securityLayer 4 and 7 load balancingCDN caching and invalidation rulesEdge security and DDoS protectionsLesson 2Data and state management: database selection (RDBMS vs cloud-native SQL/NoSQL), caching, data replication and backup strategiesThis part tackles data and state handling, including RDBMS and cloud SQL/NoSQL options, schema and access ways, caching, replication, and backups. It stresses consistency, speed, and recovery goals.
Relational vs NoSQL data modelingManaged database service selectionCaching layers and invalidationReplication, RPO, and RTO planningBackup, restore, and DR testingLesson 3Security and compliance design: IAM, secrets management, encryption in transit and at rest, PCI scope reduction approachesThis part puts security and compliance first, covering IAM, secrets handling, and encryption moving and stored. It also brings in PCI scope cuts and audit prep for controlled ICT setups.
Identity and access management designSecrets storage and rotationTLS, certificates, and key handlingData encryption at rest strategiesPCI scope reduction and evidenceLesson 4Cost management and governance: tagging, budgeting, reserved vs on-demand usage, cost monitoring toolsThis part explains handling costs and oversight, with tagging rules, budgeting, reserved vs spot capacity. It covers monitoring tools, chargeback, and limits to avoid extra spending.
Tagging and cost allocation modelsBudgeting and forecast processesReserved, spot, and on-demand mixCost dashboards and alertingPolicies and guardrails for spendLesson 5Choosing deployment platform(s): public cloud selection criteria (availability zones, managed services, cost), hybrid vs cloud-native tradeoffsThis part shows picking public cloud options, matching managed services and prices, and choosing hybrid or full-cloud, fitting resilience, rules, and running needs.
Cloud provider comparison criteriaEvaluating managed service offeringsCost modeling and TCO estimationHybrid vs cloud-native decision factorsMulti-region and AZ deployment designLesson 6Observability and operability: centralized logging, metrics, distributed tracing, alerting and runbooksThis part covers building monitoring for ICT systems, with central logs, metrics, traces, and alerts. It explains SLOs, dashboards, runbooks, and on-call to keep things running smooth and fix issues quick.
Centralized logging architectureMetrics, KPIs, SLOs, and SLIsDistributed tracing implementationAlert design and noise reductionRunbooks and incident workflowsLesson 7Compute and runtime: containers, orchestration with Kubernetes, serverless options and when to use themThis part checks compute and runtime choices, like containers, Kubernetes handling, and serverless. It covers scheduling, auto-scaling, isolation, and best fits for ICT needs.
Containerization standards and imagesKubernetes cluster and node designAutoscaling and workload placementServerless functions and event modelsChoosing runtimes for each workloadLesson 8CI/CD and delivery pipelines: branching strategies, automated testing, artifact management, deployment patterns (blue/green, canary)This part details CI/CD flows, from branching and versions to auto-tests, artifact handling, and rollout ways like blue/green and canary, for safe, repeatable software drops.
Branching and release strategiesAutomated build and test stagesArtifact storage and provenanceBlue/green and canary rolloutsRollback and feature flag tacticsLesson 9Core architecture patterns: microservices vs modular monolith, API gateway, service mesh essentialsThis part explores main design patterns, pitting microservices against modular monoliths, and API gateways and service meshes. It weighs scaling, links, monitoring, and running complexity.
Microservices vs modular monolithDomain boundaries and service sizingAPI gateway responsibilitiesService mesh capabilities and limitsInter-service communication patterns