mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-10-24 01:08:07 +08:00
docs(cloud-computing): add resources from matching nodes in other roadmaps (#10481)
* docs(cloud-computing): add resources from matching nodes in other roadmaps Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * Update azure@54FZABfiiluudsw8dU2qj.md --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
Javier Canales
co-authored by
Claude Sonnet 5.5
Claude Sonnet 5.5
parent
d94eec0abf
commit
404cef3155
@@ -1,3 +1,7 @@
|
||||
# Auto Scaling
|
||||
|
||||
Auto scaling automatically adjusts the number of running instances based on demand. A scaling policy monitors a metric (CPU utilization, request rate, queue depth) and triggers the addition or removal of instances to match load. Auto scaling groups in AWS, managed instance groups in GCP, and scale sets in Azure implement this pattern. It is the primary mechanism for achieving elasticity in cloud architectures and directly reduces costs by terminating unused capacity during low-traffic periods.
|
||||
Auto scaling automatically adjusts the number of running instances based on demand. A scaling policy monitors a metric (CPU utilization, request rate, queue depth) and triggers the addition or removal of instances to match load. Auto scaling groups in AWS, managed instance groups in GCP, and scale sets in Azure implement this pattern. It is the primary mechanism for achieving elasticity in cloud architectures and directly reduces costs by terminating unused capacity during low-traffic periods.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS Autoscaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html)
|
||||
|
||||
@@ -5,3 +5,7 @@ AWS (Amazon Web Services) is the largest cloud provider by market share, launche
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated AWS Roadmap](https://roadmap.sh/aws)
|
||||
- [@official@AWS Cloud Essentials](https://aws.amazon.com/getting-started/cloud-essentials/)
|
||||
- [@official@Overview of Amazon Web Services](https://docs.aws.amazon.com/whitepapers/latest/aws-overview/introduction.html)
|
||||
- [@course@AWS Complete Tutorial](https://www.youtube.com/watch?v=B8i49C8fC3E)
|
||||
- [@video@100 hour AWS Complete Course](https://www.youtube.com/watch?v=zA8guDqfv40)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Azure
|
||||
|
||||
Microsoft Azure is the second-largest cloud provider, with particular strength in enterprise environments due to its deep integration with Microsoft products such as Active Directory, Office 365, and Windows Server. Azure is the preferred choice for organizations already running Microsoft workloads and has strong hybrid cloud capabilities through services like Azure Arc.
|
||||
Microsoft Azure is the second-largest cloud provider, with particular strength in enterprise environments due to its deep integration with Microsoft products such as Active Directory, Office 365, and Windows Server. Azure is the preferred choice for organizations already running Microsoft workloads and has strong hybrid cloud capabilities through services like Azure Arc.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@What is Azure?](https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-azure)
|
||||
- [@official@Azure Docs](https://learn.microsoft.com/en-us/azure/?product=popular)
|
||||
- [@video@Microsoft Azure](https://www.youtube.com/playlist?list=PLEiEAq2VkUUKihhGvJw05bU8DhoQMn_ni)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Block Storage
|
||||
|
||||
Block storage provides raw storage volumes that attach to instances and behave like physical disks. The operating system formats them with a filesystem and reads and writes to them at the block level. Block storage offers low latency and high IOPS, making it the right choice for database volumes, operating system disks, and any workload that requires fast random read/write access. AWS EBS, Google Persistent Disk, and Azure Managed Disks are the standard managed block storage options.
|
||||
Block storage provides raw storage volumes that attach to instances and behave like physical disks. The operating system formats them with a filesystem and reads and writes to them at the block level. Block storage offers low latency and high IOPS, making it the right choice for database volumes, operating system disks, and any workload that requires fast random read/write access. AWS EBS, Google Persistent Disk, and Azure Managed Disks are the standard managed block storage options.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Elastic Block Store](https://docs.aws.amazon.com/ebs/latest/userguide/what-is-ebs.html)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# CDN & Edge Caching
|
||||
|
||||
A CDN (Content Delivery Network) distributes static and cacheable content (images, scripts, video, API responses) to servers located geographically close to end users, reducing latency and offloading traffic from the origin server. Edge caching stores responses at the CDN layer so repeated requests are served without reaching the origin. CloudFront, Cloud CDN, and Azure CDN are the major managed options. CDNs are also used as a first line of defense against DDoS attacks by absorbing traffic at the edge before it reaches origin infrastructure.
|
||||
A CDN (Content Delivery Network) distributes static and cacheable content (images, scripts, video, API responses) to servers located geographically close to end users, reducing latency and offloading traffic from the origin server. Edge caching stores responses at the CDN layer so repeated requests are served without reaching the origin. CloudFront, Cloud CDN, and Azure CDN are the major managed options. CDNs are also used as a first line of defense against DDoS attacks by absorbing traffic at the edge before it reaches origin infrastructure.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Amazon Cloudfront](https://aws.amazon.com/cloudfront/)
|
||||
- [@article@What is a CDN?](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/)
|
||||
- [@article@Content Delivery Network (CDN) - System Design](https://dev.to/karanpratapsingh/system-design-the-complete-course-10fo#content-delivery-network-cdn)
|
||||
- [@video@Content Delivery Networks](https://www.youtube.com/watch?v=6DXEPcXKQNY)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# CI/CD Pipelines
|
||||
|
||||
A CI/CD pipeline is an automated workflow that runs whenever code changes are committed. Continuous Integration (CI) builds and tests the change to verify it does not break existing functionality. Continuous Delivery (CD) packages the artifact and ensures it is always in a deployable state. Continuous Deployment goes one step further and pushes to production automatically when all checks pass. Cloud providers offer managed pipeline services (AWS CodePipeline, Google Cloud Build, Azure DevOps) that integrate with source control, artifact registries, and deployment targets.
|
||||
A CI/CD pipeline is an automated workflow that runs whenever code changes are committed. Continuous Integration (CI) builds and tests the change to verify it does not break existing functionality. Continuous Delivery (CD) packages the artifact and ensures it is always in a deployable state. Continuous Deployment goes one step further and pushes to production automatically when all checks pass. Cloud providers offer managed pipeline services (AWS CodePipeline, Google Cloud Build, Azure DevOps) that integrate with source control, artifact registries, and deployment targets.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Automate your workflow - Github Actions](https://github.com/features/actions)
|
||||
- [@official@CI/CD Pipelines - GitLab](https://docs.gitlab.com/ee/ci/pipelines/)
|
||||
- [@official@Continuous Integration and Delivery - CircleCI](https://circleci.com/)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# CI/CD
|
||||
|
||||
CI/CD (Continuous Integration and Continuous Delivery) is the practice of automating the build, test, and deployment of software so that changes can be released reliably and frequently. In cloud environments, CI/CD pipelines integrate with container registries, IaC tools, and orchestration platforms to take code from a developer's commit to a running production workload with minimal manual steps.
|
||||
CI/CD (Continuous Integration and Continuous Delivery) is the practice of automating the build, test, and deployment of software so that changes can be released reliably and frequently. In cloud environments, CI/CD pipelines integrate with container registries, IaC tools, and orchestration platforms to take code from a developer's commit to a running production workload with minimal manual steps.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is CI/CD? Continuous Integration and Continuous Delivery](https://www.guru99.com/continuous-integration.html)
|
||||
- [@article@Continuous Integration vs Delivery vs Deployment](https://www.guru99.com/continuous-integration-vs-delivery-vs-deployment.html)
|
||||
- [@article@CI/CD Pipeline: Learn with Example](https://www.guru99.com/ci-cd-pipeline.html)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Cloud Deployment Models
|
||||
|
||||
Cloud deployment models represent the specific environment where cloud resources, such as servers, storage, and networking, are hosted and made accessible to users. These models define who owns the infrastructure, how it is managed, and the level of control and security available to the organization. The primary categories include public clouds, which are managed by third-party providers over the internet; private clouds, which are dedicated to a single organization; and hybrid clouds, which combine both environments to allow data and applications to be shared between them.
|
||||
Cloud deployment models represent the specific environment where cloud resources, such as servers, storage, and networking, are hosted and made accessible to users. These models define who owns the infrastructure, how it is managed, and the level of control and security available to the organization. The primary categories include public clouds, which are managed by third-party providers over the internet; private clouds, which are dedicated to a single organization; and hybrid clouds, which combine both environments to allow data and applications to be shared between them.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Types of Cloud Computing](https://www.redhat.com/en/topics/cloud-computing/public-cloud-vs-private-cloud-and-hybrid-cloud)
|
||||
- [@article@Selecting the right cloud for workloads](https://docs.aws.amazon.com/whitepapers/latest/public-sector-cloud-transformation/selecting-the-right-cloud-for-workloads-differences-between-public-private-and-hybrid.html)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Cloud Service Models
|
||||
|
||||
Cloud service models are standardized frameworks that define the different ways computing resources, applications, and infrastructure are delivered to users over the internet. These models—primarily Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS)—categorize services based on how much control the provider manages versus the user. By selecting a specific model, organizations can choose the appropriate level of abstraction, ranging from full control over virtual hardware to simply consuming a finished software product.
|
||||
Cloud service models are standardized frameworks that define the different ways computing resources, applications, and infrastructure are delivered to users over the internet. These models—primarily Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS)—categorize services based on how much control the provider manages versus the user. By selecting a specific model, organizations can choose the appropriate level of abstraction, ranging from full control over virtual hardware to simply consuming a finished software product.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Types of Cloud Computing](https://aws.amazon.com/types-of-cloud-computing/?nc1=h_ls)
|
||||
- [@video@IaaS vs PaaS vs SaaS cloud service models](https://youtu.be/9CVBohl6w0Q?si=cEDnXpd1sGkpf0K2)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Cloud vs On-Premises
|
||||
|
||||
On-premises infrastructure means owning and operating physical servers in your own data center or server room. Cloud infrastructure means renting virtualized resources from a provider who manages the physical layer. The trade-off is control versus convenience: on-premises gives full hardware control and predictable costs at scale, while cloud offers speed, elasticity, and lower upfront investment.
|
||||
On-premises infrastructure means owning and operating physical servers in your own data center or server room. Cloud infrastructure means renting virtualized resources from a provider who manages the physical layer. The trade-off is control versus convenience: on-premises gives full hardware control and predictable costs at scale, while cloud offers speed, elasticity, and lower upfront investment.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is On-Premises Data Centers vs. Cloud Computing?](https://www.hpe.com/uk/en/what-is/on-premises-vs-cloud.html)
|
||||
- [@video@On Premise vs Cloud : Is Cloud Computing the future?](https://www.youtube.com/watch?v=FuPh2o-GMDA)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Configuration Management
|
||||
|
||||
Configuration management tools manage the state of software and settings on existing servers. Ansible, Chef, and Puppet are the main tools. Where IaC provisions infrastructure, configuration management configures what runs on it: installing packages, writing config files, managing services, and enforcing a desired system state. In cloud environments, configuration management is most relevant for managing fleets of VMs; container-based workloads largely replace it with immutable images built at CI time.
|
||||
Configuration management tools manage the state of software and settings on existing servers. Ansible, Chef, and Puppet are the main tools. Where IaC provisions infrastructure, configuration management configures what runs on it: installing packages, writing config files, managing services, and enforcing a desired system state. In cloud environments, configuration management is most relevant for managing fleets of VMs; container-based workloads largely replace it with immutable images built at CI time.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Configuration Management?](https://www.atlassian.com/microservices/microservices-architecture/configuration-management)
|
||||
- [@article@What is configuration management? - RedHat](https://www.redhat.com/en/topics/automation/what-is-configuration-management)
|
||||
- [@video@Why You Need to Learn Configuration Management](https://www.youtube.com/watch?v=9In7ysQJGBs)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Container Orchestration
|
||||
|
||||
Container orchestration automates the deployment, scaling, networking, and lifecycle management of containers across a cluster of machines. Running containers in production at scale requires scheduling containers onto nodes with available resources, restarting failed containers, routing traffic to healthy instances, rolling out updates without downtime, and scaling based on load. Orchestration platforms handle all of this through declarative configuration, letting teams focus on application logic rather than operational mechanics.
|
||||
Container orchestration automates the deployment, scaling, networking, and lifecycle management of containers across a cluster of machines. Running containers in production at scale requires scheduling containers onto nodes with available resources, restarting failed containers, routing traffic to healthy instances, rolling out updates without downtime, and scaling based on load. Orchestration platforms handle all of this through declarative configuration, letting teams focus on application logic rather than operational mechanics.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Container Orchestration?](https://www.redhat.com/en/topics/containers/what-is-container-orchestration)
|
||||
- [@article@What is Kubernetes?](https://kubernetes.io/docs/tutorials/kubernetes-basics/)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Containers
|
||||
|
||||
Containers are lightweight, standalone, and executable software packages that include everything needed to run an application, such as code, runtime, system tools, libraries, and settings. They ensure that software runs reliably and consistently regardless of the computing environment. This approach isolates applications from the underlying infrastructure, allowing them to start quickly, share the host system's kernel, and move seamlessly between different development, testing, and production environments.
|
||||
Containers are lightweight, standalone, and executable software packages that include everything needed to run an application, such as code, runtime, system tools, libraries, and settings. They ensure that software runs reliably and consistently regardless of the computing environment. This approach isolates applications from the underlying infrastructure, allowing them to start quickly, share the host system's kernel, and move seamlessly between different development, testing, and production environments.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What are Containers?](https://cloud.google.com/learn/what-are-containers)
|
||||
- [@article@What is a Container?](https://www.docker.com/resources/what-container/)
|
||||
- [@video@What are Containers?](https://www.youtube.com/playlist?list=PLawsLZMfND4nz-WDBZIj8-nbzGFD4S9oz)
|
||||
|
||||
@@ -5,3 +5,6 @@ Cybersecurity basics covers the core concepts a cloud practitioner needs before
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated Cyber Security Roadmap](https://roadmap.sh/cyber-security)
|
||||
- [@article@What Is Cloud Security? - Google Cloud](https://cloud.google.com/learn/what-is-cloud-security)
|
||||
- [@article@Cloud Security](https://www.checkpoint.com/cyber-hub/cloud-security/what-is-cloud-security/)
|
||||
- [@video@What is cloud security](https://www.youtube.com/watch?v=jI8IKpjiCSM)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Data Archiving
|
||||
|
||||
Data archiving is the long-term retention of data that is rarely accessed but must be preserved for compliance, legal, or historical purposes. Archive storage classes are designed for this use case, offering very low storage costs in exchange for slow retrieval. Archiving strategies include setting lifecycle rules to move aging data to archive tiers, enabling retention locks to prevent deletion before a defined period, and maintaining audit trails for regulatory compliance.
|
||||
Data archiving is the long-term retention of data that is rarely accessed but must be preserved for compliance, legal, or historical purposes. Archive storage classes are designed for this use case, offering very low storage costs in exchange for slow retrieval. Archiving strategies include setting lifecycle rules to move aging data to archive tiers, enabling retention locks to prevent deletion before a defined period, and maintaining audit trails for regulatory compliance.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS Glacier](https://aws.amazon.com/s3/storage-classes/glacier/)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Data Lifecycle
|
||||
|
||||
Data lifecycle management controls how stored data moves, ages, and is eventually retired or preserved. Cloud providers offer tiered storage classes that automatically shift data to cheaper storage as it ages, along with tools to enforce retention periods, prevent premature deletion, and meet regulatory requirements for long-term data preservation.
|
||||
Data lifecycle management controls how stored data moves, ages, and is eventually retired or preserved. Cloud providers offer tiered storage classes that automatically shift data to cheaper storage as it ages, along with tools to enforce retention periods, prevent premature deletion, and meet regulatory requirements for long-term data preservation.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Bucket / Object Lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Data Protection
|
||||
|
||||
Data protection covers the controls that keep sensitive data secure at rest, in transit, and throughout its lifecycle. In cloud environments, this includes encryption, secrets management, and compliance with privacy regulations. These controls apply across storage, databases, APIs, and any service that handles customer or business data.
|
||||
Data protection covers the controls that keep sensitive data secure at rest, in transit, and throughout its lifecycle. In cloud environments, this includes encryption, secrets management, and compliance with privacy regulations. These controls apply across storage, databases, APIs, and any service that handles customer or business data.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Backup & Restore](https://aws.amazon.com/solutions/resilience/backup-restore/)
|
||||
- [@video@Why backup should be a part of your cyber resilience plan?](https://www.youtube.com/watch?v=S8BIkoHlU_0)
|
||||
|
||||
@@ -5,3 +5,7 @@ Docker is the most widely used container platform. It provides a CLI and daemon
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated Docker Roadmap](https://roadmap.sh/docker)
|
||||
- [@official@Docker Docs](https://docs.docker.com/)
|
||||
- [@official@Docker Getting Started Guide](https://docs.docker.com/get-started/)
|
||||
- [@course@DevOps with Docker](https://courses.mooc.fi/org/uh-cs/courses/devops-with-docker)
|
||||
- [@video@Docker Tutorial](https://www.youtube.com/watch?v=RqTEHSBrYFw)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Edge Computing
|
||||
|
||||
Edge computing moves compute closer to where data is generated or consumed, rather than sending everything to a centralized cloud region. This reduces latency for time-sensitive workloads and lowers bandwidth costs by processing data locally before sending summaries or results to the cloud. Edge nodes can be CDN points of presence, on-premises hardware, or small cloud deployments in regional facilities.
|
||||
Edge computing moves compute closer to where data is generated or consumed, rather than sending everything to a centralized cloud region. This reduces latency for time-sensitive workloads and lowers bandwidth costs by processing data locally before sending summaries or results to the cloud. Edge nodes can be CDN points of presence, on-premises hardware, or small cloud deployments in regional facilities.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@What is Edge Computing - Cloudflare Docs](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/)
|
||||
- [@article@What is Edge Computing? Is It More Than a Buzzword?](https://www.howtogeek.com/devops/what-is-edge-computing-is-it-more-than-a-buzzword/)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Event-Driven Architecture
|
||||
|
||||
Event-driven architecture is a design pattern where services communicate by producing and consuming events rather than making direct calls to each other. An event (a file upload, a database write, a user action, a scheduled trigger) causes one or more functions or services to execute in response. This decouples producers from consumers, making systems easier to scale independently and more resilient to partial failures. It is the natural architectural pattern for serverless workloads.
|
||||
Event-driven architecture is a design pattern where services communicate by producing and consuming events rather than making direct calls to each other. An event (a file upload, a database write, a user action, a scheduled trigger) causes one or more functions or services to execute in response. This decouples producers from consumers, making systems easier to scale independently and more resilient to partial failures. It is the natural architectural pattern for serverless workloads.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Event Driven Architecture Style](https://learn.microsoft.com/en-us/azure/architecture/guide/architecture-styles/event-driven)
|
||||
- [@article@Event-driven Architecture](https://aws.amazon.com/event-driven-architecture/)
|
||||
- [@video@Event-Driven Architecture: Explained in 7 Minutes!](https://www.youtube.com/watch?v=gOuAqRaDdHA)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# FaaS
|
||||
|
||||
FaaS (Function as a Service) lets you deploy individual functions that run in response to events, with no server management. The provider handles all infrastructure, scaling to zero when idle and scaling out automatically under load. AWS Lambda, Google Cloud Functions, and Azure Functions are the main platforms. FaaS is the compute model behind serverless architectures.
|
||||
FaaS (Function as a Service) lets you deploy individual functions that run in response to events, with no server management. The provider handles all infrastructure, scaling to zero when idle and scaling out automatically under load. AWS Lambda, Google Cloud Functions, and Azure Functions are the main platforms. FaaS is the compute model behind serverless architectures.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html)
|
||||
- [@official@AWS Lambda Introduction](https://docs.aws.amazon.com/lambda/latest/operatorguide/intro.html)
|
||||
- [@video@AWS Lambda Tutorial: Getting Started with Serverless Computing](https://www.youtube.com/watch?v=RtiWU1DrMaM)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# GCP
|
||||
|
||||
GCP (Google Cloud Platform) is Google's public cloud, known for its strengths in data analytics, machine learning, and Kubernetes, which Google originally developed. BigQuery, Vertex AI, and Google Kubernetes Engine are among its most widely used services. GCP has a smaller market share than AWS and Azure but is particularly strong in data-intensive and AI-driven workloads.
|
||||
GCP (Google Cloud Platform) is Google's public cloud, known for its strengths in data analytics, machine learning, and Kubernetes, which Google originally developed. BigQuery, Vertex AI, and Google Kubernetes Engine are among its most widely used services. GCP has a smaller market share than AWS and Azure but is particularly strong in data-intensive and AI-driven workloads.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Google Cloud Platform](https://cloud.google.com)
|
||||
- [@official@Cloud Computing, Hosting Services, and APIs](https://cloud.google.com/gcp)
|
||||
- [@official@Google Cloud Documentation](https://docs.cloud.google.com/docs)
|
||||
- [@article@What is Google Cloud Platform?](https://www.huntress.com/cybersecurity-101/topic/what-is-google-cloud-platform)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# GitOps
|
||||
|
||||
GitOps is an operational model where Git is the single source of truth for both application and infrastructure configuration. All changes are made through pull requests and code review; automated pipelines detect changes and apply them to the cluster without manual intervention. Tools like ArgoCD and Flux watch a Git repository and continuously reconcile the cluster state with what is defined there. GitOps combines the auditability and collaboration of version control with the automation of IaC and CI/CD.
|
||||
GitOps is an operational model where Git is the single source of truth for both application and infrastructure configuration. All changes are made through pull requests and code review; automated pipelines detect changes and apply them to the cluster without manual intervention. Tools like ArgoCD and Flux watch a Git repository and continuously reconcile the cluster state with what is defined there. GitOps combines the auditability and collaboration of version control with the automation of IaC and CI/CD.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is GitOps](https://octopus.com/devops/gitops/?utm_source=roadmap&utm_medium=link&utm_campaign=devops-gitops)
|
||||
- [@article@GitOps Interactive Benefits Diagram](https://octopus.com/devops/gitops/interactive-diagrams/?utm_source=roadmap&utm_medium=link&utm_campaign=devops-gitops)
|
||||
- [@article@GitOps Maturity Model](https://octopus.com/devops/gitops/gitops-maturity-model/?utm_source=roadmap&utm_medium=link&utm_campaign=devops-gitops)
|
||||
- [@video@What is GitOps, How GitOps works and Why it's so useful](https://www.youtube.com/watch?v=f5EpcWp0THw)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Hybrid Cloud
|
||||
|
||||
A hybrid cloud connects private and public cloud environments, allowing workloads to move between them. A common pattern is running sensitive or latency-critical workloads on-premises while using public cloud for burst capacity, backups, or less sensitive services. Hybrid architectures require careful network design and consistent identity and security policies across both environments.
|
||||
A hybrid cloud connects private and public cloud environments, allowing workloads to move between them. A common pattern is running sensitive or latency-critical workloads on-premises while using public cloud for burst capacity, backups, or less sensitive services. Hybrid architectures require careful network design and consistent identity and security policies across both environments.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is a Hybrid Cloud?](https://cloud.google.com/learn/what-is-hybrid-cloud)
|
||||
- [@video@What is Hybrid cloud?](https://www.youtube.com/watch?v=3kGFBBy3Lyg)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Hypervisors
|
||||
|
||||
A hypervisor is the software layer that makes virtualization possible. It sits between the physical hardware and the virtual machines running on top of it, allocating CPU, memory, and I/O resources to each VM while keeping them isolated from one another. Type 1 hypervisors (KVM, VMware ESXi, Hyper-V) run directly on bare metal and are used by all major cloud providers. Type 2 hypervisors (VirtualBox, VMware Workstation) run on top of a host operating system and are used primarily for local development.
|
||||
A hypervisor is the software layer that makes virtualization possible. It sits between the physical hardware and the virtual machines running on top of it, allocating CPU, memory, and I/O resources to each VM while keeping them isolated from one another. Type 1 hypervisors (KVM, VMware ESXi, Hyper-V) run directly on bare metal and are used by all major cloud providers. Type 2 hypervisors (VirtualBox, VMware Workstation) run on top of a host operating system and are used primarily for local development.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is a hypervisor?](https://www.redhat.com/en/topics/virtualization/what-is-a-hypervisor)
|
||||
- [@video@What is a Hypervisor?](https://www.youtube.com/watch?v=LMAEbB2a50M)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# IaaS
|
||||
|
||||
IaaS (Infrastructure as a Service) gives you raw computing resources over the internet: virtual machines, storage, and networking, without the overhead of managing physical hardware. You control the operating system and everything above it; the provider manages the physical layer. EC2, Google Compute Engine, and Azure Virtual Machines are IaaS products. IaaS is the foundation most other cloud service models build on.
|
||||
IaaS (Infrastructure as a Service) gives you raw computing resources over the internet: virtual machines, storage, and networking, without the overhead of managing physical hardware. You control the operating system and everything above it; the provider manages the physical layer. EC2, Google Compute Engine, and Azure Virtual Machines are IaaS products. IaaS is the foundation most other cloud service models build on.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is IaaS?](https://azure.microsoft.com/en-gb/resources/cloud-computing-dictionary/what-is-iaas)
|
||||
- [@video@IaaS Explained](https://www.youtube.com/watch?v=XRdmfo4M_YA)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# IAM
|
||||
|
||||
IAM (Identity and Access Management) is the system that controls who can access cloud resources and what they can do with them. Every action in a cloud environment (launching an instance, reading a bucket, calling an API) is authorized through IAM. Identities can be human users, service accounts, or cloud services. Policies attached to identities define allowed actions on specific resources. IAM is the foundation of cloud security; misconfigured IAM policies are one of the most common causes of cloud security incidents.
|
||||
IAM (Identity and Access Management) is the system that controls who can access cloud resources and what they can do with them. Every action in a cloud environment (launching an instance, reading a bucket, calling an API) is authorized through IAM. Identities can be human users, service accounts, or cloud services. Policies attached to identities define allowed actions on specific resources. IAM is the foundation of cloud security; misconfigured IAM policies are one of the most common causes of cloud security incidents.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@IAM - User Guide](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html)
|
||||
- [@article@Introduction to Identity and Access Management (IAM)](https://auth0.com/docs/get-started/identity-fundamentals/identity-and-access-management)
|
||||
- [@article@What is identity and access management (IAM)?](https://www.ibm.com/think/topics/identity-access-management)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Instance Types
|
||||
|
||||
Cloud providers offer a range of instance types to match different workload requirements. Each type provides a specific combination of CPU, memory, storage, and network capacity, organized into families optimized for general use, compute-intensive tasks, memory-heavy applications, or GPU workloads. Selecting the right instance type is one of the most direct levers for managing both performance and cost.
|
||||
Cloud providers offer a range of instance types to match different workload requirements. Each type provides a specific combination of CPU, memory, storage, and network capacity, organized into families optimized for general use, compute-intensive tasks, memory-heavy applications, or GPU workloads. Selecting the right instance type is one of the most direct levers for managing both performance and cost.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS EC2 Instance Types](https://aws.amazon.com/ec2/instance-types)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Instance
|
||||
|
||||
An instance is a single virtual server running in the cloud. You choose its size (CPU, memory, storage) from a catalog of instance types and pay for it by the second or hour. Instances are the basic unit of compute in IaaS environments.
|
||||
An instance is a single virtual server running in the cloud. You choose its size (CPU, memory, storage) from a catalog of instance types and pay for it by the second or hour. Instances are the basic unit of compute in IaaS environments.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@EC2 - User Guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html)
|
||||
- [@video@Introduction to Amazon EC2](https://www.youtube.com/watch?v=eaicwmnSdCs)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# Introduction
|
||||
|
||||
Cloud computing is the delivery of computing resources over the internet, including servers, storage, databases, networking, and software, provided on demand by third-party providers. Instead of owning and maintaining physical hardware, you rent what you need and pay for what you use. This model shifts infrastructure from a capital expense to an operational one, enabling teams to move f
|
||||
Cloud computing is the delivery of computing resources over the internet, including servers, storage, databases, networking, and software, provided on demand by third-party providers. Instead of owning and maintaining physical hardware, you rent what you need and pay for what you use. This model shifts infrastructure from a capital expense to an operational one, enabling teams to move f
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Cloud Computing - IBM](https://www.ibm.com/topics/cloud-computing)
|
||||
- [@article@Cloud Computing - AWS](https://aws.amazon.com/what-is-cloud-computing/)
|
||||
- [@article@What is Cloud Computing? - Azure](https://azure.microsoft.com/en-gb/resources/cloud-computing-dictionary/what-is-cloud-computing)
|
||||
- [@video@What is Cloud Computing?](https://www.youtube.com/watch?v=mxT233EdY5c)
|
||||
|
||||
@@ -6,3 +6,6 @@ Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated Kubernetes Roadmap](https://roadmap.sh/kubernetes)
|
||||
- [@article@Top 50 Kubernetes Interview Questions and Answers](https://roadmap.sh/questions/kubernetes)
|
||||
- [@official@Kubernetes Website](https://kubernetes.io/)
|
||||
- [@article@Kubernetes: An Overview](https://thenewstack.io/kubernetes-an-overview/)
|
||||
- [@opensource@kubernetes/kubernetes](https://github.com/kubernetes/kubernetes)
|
||||
|
||||
@@ -5,3 +5,6 @@ Linux is the operating system that runs the vast majority of cloud servers, cont
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated Linux Roadmap](https://roadmap.sh/linux)
|
||||
- [@course@Linux from scratch - Cisco](https://www.netacad.com/courses/os-it/ndg-linux-unhatched)
|
||||
- [@article@Linux Commands Cheat Sheet](https://assets.hostinger.com/content/tutorials/pdf/Linux-Commands-Cheat-Sheet.pdf)
|
||||
- [@video@Introduction to Linux](https://youtu.be/sWbUDq4S6Y8)
|
||||
|
||||
@@ -7,3 +7,4 @@ Visit the following resources to learn more:
|
||||
- [@article@API gateway vs. Load balancer: Do you need one or both?](https://roadmap.sh/network-engineer/api-gateway-vs-load-balancer)
|
||||
- [@article@What is Network Load Balancing? Understanding Traffic Distribution](https://www.digitalocean.com/resources/articles/network-load-balancing)
|
||||
- [@video@Load Balancer Explained](https://www.youtube.com/watch?v=1fN2UDbtGDQ)
|
||||
- [@article@What is Load Balancing?](https://www.nginx.com/resources/glossary/load-balancing/)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# Managed Kubernetes
|
||||
|
||||
Some providers specialize in managed Kubernetes as their primary product, targeting teams that want Kubernetes without the complexity of running it on a hyperscaler. Civo and Vultr are examples. They offer faster cluster provisioning, simpler pricing, and a focused feature set compared to EKS, GKE, or AKS.
|
||||
Some providers specialize in managed Kubernetes as their primary product, targeting teams that want Kubernetes without the complexity of running it on a hyperscaler. Civo and Vultr are examples. They offer faster cluster provisioning, simpler pricing, and a focused feature set compared to EKS, GKE, or AKS.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@GKE](https://cloud.google.com/kubernetes-engine)
|
||||
- [@official@EKS](https://aws.amazon.com/eks/)
|
||||
- [@official@AKS](https://azure.microsoft.com/en-us/products/kubernetes-service/)
|
||||
- [@official@Concepts of Amazon EKS](https://docs.aws.amazon.com/eks/)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Managed Relational DBs
|
||||
|
||||
Managed relational databases provide SQL-compatible storage with ACID guarantees, automatic backups, and multi-AZ failover, without requiring manual database administration. AWS RDS, Google Cloud SQL, and Azure Database for PostgreSQL are examples. They support common engines (PostgreSQL, MySQL, SQL Server) and handle routine maintenance tasks, letting teams focus on schema design and query optimization rather than server management.
|
||||
Managed relational databases provide SQL-compatible storage with ACID guarantees, automatic backups, and multi-AZ failover, without requiring manual database administration. AWS RDS, Google Cloud SQL, and Azure Database for PostgreSQL are examples. They support common engines (PostgreSQL, MySQL, SQL Server) and handle routine maintenance tasks, letting teams focus on schema design and query optimization rather than server management.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Amazon RDS](https://aws.amazon.com/rds/)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# Microservices
|
||||
|
||||
Microservices is an architectural style that structures an application as a collection of small, independently deployable services, each responsible for a specific business capability and owning its own data store. Services communicate over APIs or message queues rather than sharing a database. The approach enables teams to develop, deploy, and scale services independently, but introduces operational complexity in service discovery, distributed tracing, and failure handling that a monolithic application does not have.
|
||||
Microservices is an architectural style that structures an application as a collection of small, independently deployable services, each responsible for a specific business capability and owning its own data store. Services communicate over APIs or message queues rather than sharing a database. The approach enables teams to develop, deploy, and scale services independently, but introduces operational complexity in service discovery, distributed tracing, and failure handling that a monolithic application does not have.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Pattern: Microservice Architecture](https://microservices.io/patterns/microservices.html)
|
||||
- [@article@Microservices 101](https://thenewstack.io/microservices-101/)
|
||||
- [@article@Introduction to Microservices](https://aws.amazon.com/microservices/)
|
||||
- [@article@Microservices - Wikipedia](https://en.wikipedia.org/wiki/Microservices)
|
||||
|
||||
+8
-1
@@ -1,3 +1,10 @@
|
||||
# Monolithic vs Microservices
|
||||
|
||||
A monolithic application packages all functionality into a single deployable unit. Every feature shares the same codebase, runtime, and database, making it straightforward to develop and test locally but increasingly difficult to scale and deploy as it grows. Microservices decompose the monolith into separate services with clear boundaries. The transition involves trade-offs: microservices improve deployment flexibility and fault isolation but require more sophisticated infrastructure, monitoring, and inter-service communication patterns.
|
||||
A monolithic application packages all functionality into a single deployable unit. Every feature shares the same codebase, runtime, and database, making it straightforward to develop and test locally but increasingly difficult to scale and deploy as it grows. Microservices decompose the monolith into separate services with clear boundaries. The transition involves trade-offs: microservices improve deployment flexibility and fault isolation but require more sophisticated infrastructure, monitoring, and inter-service communication patterns.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Pattern: Monolithic Architecture](https://microservices.io/patterns/monolithic.html)
|
||||
- [@article@Monolithic Architecture - Advantages & Disadvantages](https://datamify.medium.com/monolithic-architecture-advantages-and-disadvantages-e71a603eec89)
|
||||
- [@article@Overview of Monolithic Architecture](https://www.atlassian.com/microservices/microservices-architecture/microservices-vs-monolith)
|
||||
- [@article@What is Monolithic architecture?](https://www.techtarget.com/whatis/definition/monolithic-architecture)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Multi-Cloud
|
||||
|
||||
Multi-cloud means using services from more than one cloud provider simultaneously. Organizations adopt multi-cloud to avoid vendor lock-in, meet data residency requirements in regions where one provider has no presence, or use best-of-breed services from different providers. It increases operational complexity and requires tooling that works across providers, such as Terraform or Kubernetes.
|
||||
Multi-cloud means using services from more than one cloud provider simultaneously. Organizations adopt multi-cloud to avoid vendor lock-in, meet data residency requirements in regions where one provider has no presence, or use best-of-breed services from different providers. It increases operational complexity and requires tooling that works across providers, such as Terraform or Kubernetes.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is multicloud?](https://cloud.google.com/learn/what-is-multicloud?hl=en)
|
||||
- [@video@What is Multicloud? How Do You Manage It?](https://www.youtube.com/watch?v=AjtdZ3gFRjU)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# NAS and SAN
|
||||
|
||||
NAS (Network Attached Storage) provides file-level storage access over a network, typically using NFS or SMB protocols. SAN (Storage Area Network) provides block-level storage access over a dedicated high-speed fabric, appearing to the server as a locally attached disk. Both technologies predate cloud computing and remain relevant in private cloud and hybrid architectures. Cloud-managed file storage (EFS, Filestore) and block storage (EBS, Persistent Disk) are the cloud equivalents of NAS and SAN respectively.
|
||||
NAS (Network Attached Storage) provides file-level storage access over a network, typically using NFS or SMB protocols. SAN (Storage Area Network) provides block-level storage access over a dedicated high-speed fabric, appearing to the server as a locally attached disk. Both technologies predate cloud computing and remain relevant in private cloud and hybrid architectures. Cloud-managed file storage (EFS, Filestore) and block storage (EBS, Persistent Disk) are the cloud equivalents of NAS and SAN respectively.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@NAS vs SAN - What are the differences?](https://www.backblaze.com/blog/whats-the-diff-nas-vs-san/)
|
||||
- [@video@What is a NAS](https://www.youtube.com/watch?v=ZwhT-KI16jo)
|
||||
- [@video@What is a Storage Area Network](https://www.youtube.com/watch?v=7eGw4vhyeTA)
|
||||
|
||||
@@ -5,3 +5,6 @@ NoSQL databases store data in formats other than relational tables: key-value pa
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Types of NoSQL Databases: How to Choose the Right One](https://roadmap.sh/backend/types-of-nosql-databases)
|
||||
- [@official@Amazon DynamoDB](https://aws.amazon.com/dynamodb/)
|
||||
- [@article@SQL vs. NoSQL Databases: What’s the Difference?](https://www.ibm.com/blog/sql-vs-nosql/)
|
||||
- [@article@NoSQL vs. SQL Databases](https://www.mongodb.com/nosql-explained/nosql-vs-sql)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Object Storage
|
||||
|
||||
Object storage stores data as discrete objects, each consisting of the data itself, metadata, and a unique identifier, in a flat namespace without folder hierarchy. Access is through HTTP APIs rather than a filesystem interface. It is designed for massive scale, high durability (typically 11 nines), and low cost per GB. Object storage is the default choice for backups, media files, logs, static website assets, and data lake raw storage. AWS S3, Google Cloud Storage, and Azure Blob Storage are the primary implementations.
|
||||
Object storage stores data as discrete objects, each consisting of the data itself, metadata, and a unique identifier, in a flat namespace without folder hierarchy. Access is through HTTP APIs rather than a filesystem interface. It is designed for massive scale, high durability (typically 11 nines), and low cost per GB. Object storage is the default choice for backups, media files, logs, static website assets, and data lake raw storage. AWS S3, Google Cloud Storage, and Azure Blob Storage are the primary implementations.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@What is Object Storage?](https://www.cloudflare.com/learning/cloud/what-is-object-storage/)
|
||||
- [@official@S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# PaaS
|
||||
|
||||
PaaS (Platform as a Service) provides a managed environment for deploying and running applications, abstracting away the underlying infrastructure. You bring your code; the platform handles the runtime, scaling, patching, and availability. Google App Engine, AWS Elastic Beanstalk, and Heroku are PaaS examples. PaaS trades infrastructure control for reduced operational burden.
|
||||
PaaS (Platform as a Service) provides a managed environment for deploying and running applications, abstracting away the underlying infrastructure. You bring your code; the platform handles the runtime, scaling, patching, and availability. Google App Engine, AWS Elastic Beanstalk, and Heroku are PaaS examples. PaaS trades infrastructure control for reduced operational burden.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is PaaS?](https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-paas)
|
||||
- [@video@PaaS Explained](https://www.youtube.com/watch?v=QAbqJzd0PEE)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Privacy & Compliance
|
||||
|
||||
Cloud compliance means meeting regulatory and legal requirements for how data is stored, processed, and accessed. Common frameworks include GDPR (EU data privacy), HIPAA (US healthcare data), SOC 2 (service organization controls), and PCI DSS (payment card data). Cloud providers offer compliance-ready services and share audit reports, but customers remain responsible for configuring those services correc
|
||||
Cloud compliance means meeting regulatory and legal requirements for how data is stored, processed, and accessed. Common frameworks include GDPR (EU data privacy), HIPAA (US healthcare data), SOC 2 (service organization controls), and PCI DSS (payment card data). Cloud providers offer compliance-ready services and share audit reports, but customers remain responsible for configuring those services correc
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Understanding Data Privacy Compliance](https://www.salesforce.com/platform/data-privacy-compliance/what-is-data-privacy-compliance/)
|
||||
- [@article@What is Cyber Security Compliance?](https://www.comptia.org/content/articles/what-is-cybersecurity-compliance)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Provider Landscape
|
||||
|
||||
The provider landscape refers to the ecosystem of companies that supply infrastructure, platforms, and software services over the internet. These organizations, often called Cloud Service Providers (CSPs), manage large-scale data centers and physical hardware, allowing businesses to rent computing power and storage instead of maintaining their own local servers.
|
||||
The provider landscape refers to the ecosystem of companies that supply infrastructure, platforms, and software services over the internet. These organizations, often called Cloud Service Providers (CSPs), manage large-scale data centers and physical hardware, allowing businesses to rent computing power and storage instead of maintaining their own local servers.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Cloud Service Provider](https://www.techtarget.com/searchitchannel/definition/cloud-service-provider-cloud-provider)
|
||||
- [@article@What are Cloud Providers?](https://www.redhat.com/en/topics/cloud-computing/what-are-cloud-providers)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Provisioning
|
||||
|
||||
Provisioning is the process of setting up and configuring cloud resources so they are ready to use. This includes creating instances, allocating storage, configuring networks, and applying security policies. Provisioning can be done manually through a console, programmatically via an API, or declaratively through Infrastructure as Code tools.
|
||||
Provisioning is the process of setting up and configuring cloud resources so they are ready to use. This includes creating instances, allocating storage, configuring networks, and applying security policies. Provisioning can be done manually through a console, programmatically via an API, or declaratively through Infrastructure as Code tools.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is provisioning? - RedHat](https://www.redhat.com/en/topics/automation/what-is-provisioning)
|
||||
- [@article@What is provisioning? - IBM](https://www.ibm.com/topics/provisioning)
|
||||
- [@video@Open Answers: What is provisioning?](https://www.youtube.com/watch?v=hWvDlmhASpk)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# RBAC
|
||||
|
||||
RBAC (Role-Based Access Control) assigns permissions to roles rather than to individual users. Users or service accounts are then assigned roles, inheriting the permissions those roles define. This simplifies permission management at scale: instead of editing hundreds of individual user policies, you manage a smaller set of roles. Cloud providers implement RBAC through IAM role policies (AWS), IAM roles and bindings (GCP), and Azure Role Assignments. Kubernetes also uses RBAC to control access to cluster resources.
|
||||
RBAC (Role-Based Access Control) assigns permissions to roles rather than to individual users. Users or service accounts are then assigned roles, inheriting the permissions those roles define. This simplifies permission management at scale: instead of editing hundreds of individual user policies, you manage a smaller set of roles. Cloud providers implement RBAC through IAM role policies (AWS), IAM roles and bindings (GCP), and Azure Role Assignments. Kubernetes also uses RBAC to control access to cluster resources.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Role-Based Access Control](https://auth0.com/docs/manage-users/access-control/rbac)
|
||||
- [@article@What is Role-based Access Control (RBAC)?](https://www.redhat.com/en/topics/security/what-is-role-based-access-control)
|
||||
- [@video@Role-based Access Control (RBAC) vs. Attribute-based Access Control (ABAC)](https://www.youtube.com/watch?v=rvZ35YW4t5k)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Region, Availability Zone
|
||||
|
||||
A region is a geographic area where a cloud provider operates one or more data centers, such as us-east-1 or europe-west1. Within a region, availability zones are physically separate data centers connected by low-latency links. Distributing workloads across availability zones protects against single data center failures without the latency of cross-region replication.
|
||||
A region is a geographic area where a cloud provider operates one or more data centers, such as us-east-1 or europe-west1. Within a region, availability zones are physically separate data centers connected by low-latency links. Distributing workloads across availability zones protects against single data center failures without the latency of cross-region replication.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS Global Infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/?p=ngi&loc=0)
|
||||
- [@official@AWS Regions / Availability Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# SaaS
|
||||
|
||||
SaaS (Software as a Service) delivers fully managed applications over the internet. The provider handles everything: infrastructure, runtime, application code, and updates. Users access the software through a browser or API without managing anything underneath. Gmail, Salesforce, and Slack are SaaS products. From a cloud computing perspective, SaaS is the highest level of abstraction in the service model stack.
|
||||
SaaS (Software as a Service) delivers fully managed applications over the internet. The provider handles everything: infrastructure, runtime, application code, and updates. Users access the software through a browser or API without managing anything underneath. Gmail, Salesforce, and Slack are SaaS products. From a cloud computing perspective, SaaS is the highest level of abstraction in the service model stack.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Software as a Service?](https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-saas)
|
||||
- [@video@What is SaaS?](https://www.youtube.com/watch?v=UEHdYNXiIUU)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# Scalability
|
||||
|
||||
Scalability is the capacity of a system to handle growing demand. Vertical scaling adds more power to a single machine (bigger instance). Horizontal scaling adds more machines. Cloud environments favor horizontal scaling because it avoids single points of failure and can be automated. Scalability is a design property, while elasticity is the mechanism that achieves it dynamically.
|
||||
Scalability is the capacity of a system to handle growing demand. Vertical scaling adds more power to a single machine (bigger instance). Horizontal scaling adds more machines. Cloud environments favor horizontal scaling because it avoids single points of failure and can be automated. Scalability is a design property, while elasticity is the mechanism that achieves it dynamically.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@A Word on Scalability](https://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html)
|
||||
- [@article@Performance vs Scalability](https://blog.professorbeekums.com/performance-vs-scalability/)
|
||||
- [@article@Scalable Architecture: A Definition and How-To Guide](https://www.sentinelone.com/blog/scalable-architecture/)
|
||||
- [@video@Scaling Distributed Systems - Software Architecture Introduction](https://www.youtube.com/watch?v=gxfERVP18-g)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Scaling
|
||||
|
||||
Scaling is the process of adjusting compute capacity to match demand. Cloud environments support both automatic scaling in response to real-time load and pricing-based strategies that trade reliability guarantees for lower cost. Getting scaling right reduces both over-provisioning (wasted spend) and under-provisioning (degraded performance or outages).
|
||||
Scaling is the process of adjusting compute capacity to match demand. Cloud environments support both automatic scaling in response to real-time load and pricing-based strategies that trade reliability guarantees for lower cost. Getting scaling right reduces both over-provisioning (wasted spend) and under-provisioning (degraded performance or outages).
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Scaling Horizontally vs. Scaling Vertically](https://www.digitalocean.com/resources/article/horizontal-scaling-vs-vertical-scaling)
|
||||
- [@article@Horizontal Vs. Vertical Scaling: Which Should You Choose?](https://www.cloudzero.com/blog/horizontal-vs-vertical-scaling/)
|
||||
- [@video@System Design Basics: Horizontal vs. Vertical Scaling](https://www.youtube.com/watch?v=xpDnVSmNFX0)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
# Secrets Management
|
||||
|
||||
Secrets management is the practice of storing, accessing, and rotating sensitive values (API keys, database passwords, certificates, tokens) securely. Hardcoding secrets in application code or environment variables is a common source of security breaches. Dedicated secrets managers (AWS Secrets Manager, HashiCorp Vault, GCP Secret Manager) store secrets encrypted, control access through IAM policies, provide audit logs of every access, and support automatic rotation to reduce the blast radius of a compromised credential.
|
||||
Secrets management is the practice of storing, accessing, and rotating sensitive values (API keys, database passwords, certificates, tokens) securely. Hardcoding secrets in application code or environment variables is a common source of security breaches. Dedicated secrets managers (AWS Secrets Manager, HashiCorp Vault, GCP Secret Manager) store secrets encrypted, control access through IAM policies, provide audit logs of every access, and support automatic rotation to reduce the blast radius of a compromised credential.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@How to Manage Secrets in Web Applications?](https://cs.fyi/guide/secret-management-best-practices)
|
||||
- [@article@Why DevSecOps Teams Need Secrets Management](https://www.keepersecurity.com/blog/2023/01/26/why-devsecops-teams-need-secrets-management/)
|
||||
- [@article@AWS Secrets Management Website](https://aws.amazon.com/secrets-manager/)
|
||||
- [@article@Vault Website](https://www.vaultproject.io/)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Serverless Computing
|
||||
|
||||
Serverless computing is a model where the cloud provider manages all infrastructure automatically. You deploy code (functions) that run in response to events, with no servers to provision, patch, or scale. The provider handles execution environment management, scales to zero when idle, and charges only for the compute time consumed during function execution. It shifts the operational model from managing capacity to writing event-driven logic.
|
||||
Serverless computing is a model where the cloud provider manages all infrastructure automatically. You deploy code (functions) that run in response to events, with no servers to provision, patch, or scale. The provider handles execution environment management, scales to zero when idle, and charges only for the compute time consumed during function execution. It shifts the operational model from managing capacity to writing event-driven logic.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is Serverless?](https://www.redhat.com/en/topics/cloud-native-apps/what-is-serverless)
|
||||
- [@article@What is Serverless Computing?](https://www.cloudflare.com/en-gb/learning/serverless/what-is-serverless/)
|
||||
- [@video@What is Serverless?](https://www.youtube.com/watch?v=vxJobGtqKVM)
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Service Mesh
|
||||
|
||||
A service mesh is an infrastructure layer that handles service-to-service communication in a microservices architecture. It manages traffic routing, load balancing, retries, timeouts, circuit breaking, and mutual TLS encryption between services, without any of that logic living in application code. A sidecar proxy (Envoy is the most common) runs alongside each service and intercepts all traffic. Istio and Linkerd are the main implementations. Service meshes add significant operational complexity and are most justified in large deployments with many services.
|
||||
A service mesh is an infrastructure layer that handles service-to-service communication in a microservices architecture. It manages traffic routing, load balancing, retries, timeouts, circuit breaking, and mutual TLS encryption between services, without any of that logic living in application code. A sidecar proxy (Envoy is the most common) runs alongside each service and intercepts all traffic. Istio and Linkerd are the main implementations. Service meshes add significant operational complexity and are most justified in large deployments with many services.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is a Service Mesh (AWS blog)?](https://aws.amazon.com/what-is/service-mesh/)
|
||||
- [@article@What is a Service Mesh (RedHat blog)?](https://www.redhat.com/en/topics/microservices/what-is-a-service-mesh)
|
||||
- [@video@What is a Service Mesh?](https://www.youtube.com/watch?v=vh1YtWjfcyk)
|
||||
|
||||
+5
-1
@@ -1,3 +1,7 @@
|
||||
# Shared Responsibility Model
|
||||
|
||||
The shared responsibility model defines which security tasks the cloud provider handles and which the customer must handle. The provider is responsible for the security of the cloud: physical infrastructure, hardware, hypervisors, and managed service internals. The customer is responsible for security in the cloud: operating systems, application code, data, network configuration, and identity management. The boundary shifts depending on the service model: with IaaS the customer manages more; with SaaS almost everything is the provider's responsibility.
|
||||
The shared responsibility model defines which security tasks the cloud provider handles and which the customer must handle. The provider is responsible for the security of the cloud: physical infrastructure, hardware, hypervisors, and managed service internals. The customer is responsible for security in the cloud: operating systems, application code, data, network configuration, and identity management. The boundary shifts depending on the service model: with IaaS the customer manages more; with SaaS almost everything is the provider's responsibility.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# SLA
|
||||
|
||||
An SLA (Service Level Agreement) is a contract between a cloud provider and a customer that defines the expected level of service, typically expressed as an uptime percentage. AWS S3, for example, offers a 99.99% availability SLA. SLAs also specify what compensation the provider offers if the target is not met. Understanding SLAs is important when designing for reliability and choosing between services.
|
||||
An SLA (Service Level Agreement) is a contract between a cloud provider and a customer that defines the expected level of service, typically expressed as an uptime percentage. AWS S3, for example, offers a 99.99% availability SLA. SLAs also specify what compensation the provider offers if the target is not met. Understanding SLAs is important when designing for reliability and choosing between services.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Defining Availability, Maintainability and Reliability in SRE](https://devops.com/defining-availability-maintainability-and-reliability-in-sre/)
|
||||
- [@video@SLIs, SLOs, SLAs, oh my! (class SRE implements DevOps)](https://www.youtube.com/watch?v=tEylFyxbDLE)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Storage Classes & Tiering
|
||||
|
||||
Cloud object storage services offer multiple storage classes with different cost and retrieval trade-offs. Hot tiers store frequently accessed data at higher cost per GB but with immediate retrieval. Cool and cold tiers are cheaper for data accessed infrequently. Archive tiers (Glacier on AWS, Coldline and Archive on GCP) offer the lowest storage cost but charge retrieval fees and have delays of minutes to hours. Lifecycle policies automatically move objects between tiers based on age or access patterns, optimizing cost without manual intervention.
|
||||
Cloud object storage services offer multiple storage classes with different cost and retrieval trade-offs. Hot tiers store frequently accessed data at higher cost per GB but with immediate retrieval. Cool and cold tiers are cheaper for data accessed infrequently. Archive tiers (Glacier on AWS, Coldline and Archive on GCP) offer the lowest storage cost but charge retrieval fees and have delays of minutes to hours. Lifecycle policies automatically move objects between tiers based on age or access patterns, optimizing cost without manual intervention.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@AWS S3-IA](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html)
|
||||
- [@official@Bucket / Object Lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
# Cloud Storage
|
||||
|
||||
Cloud storage provides durable, scalable, and managed storage for different types of data and access patterns. Providers offer multiple storage types suited to different use cases: object storage for unstructured data at scale, block storage for low-latency database volumes, and file storage for shared filesystems. Managing the lifecycle and compliance of stored data is as important as choosing the right storage type
|
||||
Cloud storage provides durable, scalable, and managed storage for different types of data and access patterns. Providers offer multiple storage types suited to different use cases: object storage for unstructured data at scale, block storage for low-latency database volumes, and file storage for shared filesystems. Managing the lifecycle and compliance of stored data is as important as choosing the right storage type
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Storage Types](https://aws.amazon.com/s3/storage-classes/)
|
||||
|
||||
@@ -5,3 +5,6 @@ Version control tracks changes to code and configuration over time, enabling col
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@roadmap@Visit the Dedicated Git and GitHub Roadmap](https://roadmap.sh/git-github)
|
||||
- [@course@Why version control? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
|
||||
- [@article@What is version control?](https://www.atlassian.com/git/tutorials/what-is-version-control)
|
||||
- [@video@What is a Version Control System and why you should always use it](https://www.youtube.com/watch?v=IeXhYROClZk)
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Virtual Machines
|
||||
|
||||
A virtual machine is a software-based emulation of a physical computer that runs an operating system and applications just like a dedicated hardware device. By using a hypervisor to partition the resources of a single physical server—such as CPU, memory, and storage—it allows multiple independent virtual machines to operate simultaneously on the same hardware. Each machine functions as a self-contained system, enabling users to run different operating systems or software environments in isolation while sharing the underlying physical infrastructure.
|
||||
A virtual machine is a software-based emulation of a physical computer that runs an operating system and applications just like a dedicated hardware device. By using a hypervisor to partition the resources of a single physical server—such as CPU, memory, and storage—it allows multiple independent virtual machines to operate simultaneously on the same hardware. Each machine functions as a self-contained system, enabling users to run different operating systems or software environments in isolation while sharing the underlying physical infrastructure.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is a Virtual Machine and how does it work?](https://azure.microsoft.com/en-gb/resources/cloud-computing-dictionary/what-is-a-virtual-machine)
|
||||
- [@video@Virtualization Explained](https://www.youtube.com/watch?v=UBVVq-xz5i0)
|
||||
|
||||
@@ -7,3 +7,5 @@ Visit the following resources to learn more:
|
||||
- [@article@What is a Virtual Network? How it Works and Its Types?](https://www.pynetlabs.com/what-is-a-virtual-network/)
|
||||
- [@video@Virtual Private Cloud (VPC) Explained](https://www.youtube.com/watch?v=2fPgKvDBfbs)
|
||||
- [@video@Amazon Virtual Private Cloud (VPC) Routing Deep Dive](https://www.youtube.com/watch?v=LJNNMTicv1c)
|
||||
- [@official@VPC](https://aws.amazon.com/vpc/)
|
||||
- [@video@AWS VPC Beginner to Advanced uses](https://www.youtube.com/watch?v=g2JOHLHh4rI)
|
||||
|
||||
Reference in New Issue
Block a user