Lesson 1Networking, CDN and edge considerations: VPC design, load balancing, CDN for storefront performanceThis part covers networking and edge setup, including VPC layout, subnets, routing, and load balancing. It also explains CDN and edge caching to boost performance, reliability, and security 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 deals with data and state design, covering RDBMS and cloud SQL/NoSQL options, schema and access patterns, caching, and replication and backup. It stresses consistency, performance, and recovery aims.
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 focuses on security and compliance from the start, covering IAM, secrets handling, and encryption moving and stored. It also brings in PCI scope cutting and audit prep for regulated 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 cost handling and oversight, including tagging rules, budgeting, and reserved versus on-demand capacity. It also covers cost watching tools, chargeback ways, and limits to stop overspending.
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 explains picking public cloud providers, comparing managed services and prices, and choosing between hybrid and cloud-native ways, matching deployment platforms with resilience, compliance, 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 designing monitoring for ICT systems, including central logging, metrics, traces, and alerting. It explains SLOs, dashboards, runbooks, and on-call flows for reliable running and quick incident handling.
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 looks at compute and runtime choices, including containers, Kubernetes handling, and serverless platforms. It explains scheduling, autoscaling, workload separation, and when each fits ICT rollout 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 pipeline design, from branching and versioning to automated testing, artifact handling, and deployment ways like blue/green and canary, ensuring safe, repeatable, and checkable software delivery.
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 architecture patterns, comparing microservices and modular monoliths, and explaining API gateway and service mesh roles. It focuses on scalability, coupling, monitoring, and running complexity balances.
Microservices vs modular monolithDomain boundaries and service sizingAPI gateway responsibilitiesService mesh capabilities and limitsInter-service communication patterns