One search. Connected ideas.

Connect pipelines, cloud fundamentals, and deployment troubleshooting.

Cloud platforms provide managed building blocks for compute, storage, databases, networking and operations. AWS and Azure use different service names, but the underlying choices—virtual machine versus managed runtime, object storage versus database, public versus private network—are transferable. Understanding responsibilities is more useful than memorizing a long service list.

DNS resolves names to records, load balancers select healthy destinations, IAM controls identities and permissions, and secret managers store sensitive credentials. These components connect an application to users and dependencies without putting all configuration into code. A failure at any layer can look like “the API is down” from the outside.

Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.

A delivery pipeline turns source changes into a verified, versioned artifact and releases it through controlled environments. Each step should provide evidence that the next step is safe and reproducible. Promoting the same artifact avoids rebuilding slightly different software for each environment.

GitHub Actions defines automated workflows triggered by repository or scheduled events. Workflows contain jobs that run on runners, and jobs contain ordered steps using commands or reusable actions. Artifacts and outputs move results between steps or jobs, while permissions control what the workflow may access.

Cloud platforms provide managed building blocks for compute, storage, databases, networking and operations. AWS and Azure use different service names, but the underlying choices—virtual machine versus managed runtime, object storage versus database, public versus private network—are transferable. Understanding responsibilities is more useful than memorizing a long service list.

An unreachable cloud API may fail before the request reaches application code. DNS, TLS, routing, firewall rules, load-balancer health and listening ports are separate layers to verify. Checking them in order avoids opening broad access or restarting healthy services without evidence.

DNS resolves names to records, load balancers select healthy destinations, IAM controls identities and permissions, and secret managers store sensitive credentials. These components connect an application to users and dependencies without putting all configuration into code. A failure at any layer can look like “the API is down” from the outside.

Delivery & cloud learning module

Delivery & cloud learning module