Auto-sync: 2026-04-21 20:03
This commit is contained in:
40
wiki/entities/AWS.md
Normal file
40
wiki/entities/AWS.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: AWS (Amazon Web Services)
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
---
|
||||
|
||||
# AWS (Amazon Web Services)
|
||||
|
||||
**AWS** is Amazon's cloud computing platform, providing a broad set of infrastructure and application services across 200+ fully featured services.
|
||||
|
||||
## Overview
|
||||
|
||||
AWS is one of the three major public cloud providers (alongside Azure and Google Cloud), offering the most extensive range of services.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | EC2, Lambda |
|
||||
| Storage | S3, EBS |
|
||||
| Database | RDS, DynamoDB, Aurora |
|
||||
| AI/ML | SageMaker, Bedrock |
|
||||
| Analytics | Redshift, Athena |
|
||||
| Networking | VPC, Route 53, CloudFront |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
AWS is commonly used alongside Azure and Google Cloud in multi-cloud strategies:
|
||||
- **General infrastructure** — Often primary compute and storage provider
|
||||
- **Enterprise integration** — Strong Active Directory and enterprise app ecosystem
|
||||
- **Market position** — Largest market share among cloud providers
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — AWS as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on AWS-native services
|
||||
- [[FinOps]] — Managing AWS costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
40
wiki/entities/Azure.md
Normal file
40
wiki/entities/Azure.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Azure (Microsoft Azure)
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
---
|
||||
|
||||
# Azure (Microsoft Azure)
|
||||
|
||||
**Microsoft Azure** is a cloud computing platform operated by Microsoft, providing a broad range of services for application and workload hosting.
|
||||
|
||||
## Overview
|
||||
|
||||
Azure is one of the three major public cloud providers, particularly strong in enterprise environments with Microsoft ecosystem integration.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Virtual Machines, Azure Functions |
|
||||
| Storage | Blob Storage, Azure Files |
|
||||
| Database | Azure SQL, Cosmos DB |
|
||||
| AI/ML | Azure AI, Azure OpenAI Service |
|
||||
| Analytics | Synapse, Databricks |
|
||||
| Enterprise | Active Directory, Microsoft 365 integration |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
Azure is commonly used alongside AWS and Google Cloud in multi-cloud strategies:
|
||||
- **Enterprise workloads** — Strong Windows Server and SQL Server integration
|
||||
- **AI services** — Azure OpenAI Service for enterprise AI applications
|
||||
- **Hybrid cloud** — Deep integration with on-premises Windows environments
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — Azure as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on Azure-native services
|
||||
- [[FinOps]] — Managing Azure costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
95
wiki/entities/Cloud-Maturity-Model.md
Normal file
95
wiki/entities/Cloud-Maturity-Model.md
Normal file
@@ -0,0 +1,95 @@
|
||||
---
|
||||
title: Cloud Maturity Model (CMM)
|
||||
source: https://www.bacancytechnology.com/blog/cloud-maturity-model
|
||||
tags: [Cloud, Maturity, Framework, Cloud-Adoption, Enterprise]
|
||||
---
|
||||
|
||||
# Cloud Maturity Model (CMM)
|
||||
|
||||
## Overview
|
||||
|
||||
The **Cloud Maturity Model** (CMM) is a structured framework for evaluating an organization's cloud adoption readiness. Developed and described by the Open Alliance for Cloud Adoption (OACA), it provides a systematic approach for organizations of all sizes and experience levels to assess their current cloud state, identify gaps, and plan their cloud transformation journey.
|
||||
|
||||
## Key Definition
|
||||
|
||||
The OACA describes CMM as a framework that:
|
||||
- Assists organizations in identifying tailored solutions for adopting cloud or hybrid IT environments
|
||||
- Evaluates organizations' readiness for adopting the cloud
|
||||
- Helps assess their current use of cloud services
|
||||
- Sets future goals for developing a cloud migration strategy
|
||||
- Conducts GAP analysis
|
||||
- Identifies areas for improving cloud infrastructure based on business objectives
|
||||
|
||||
## The 5 Maturity Levels
|
||||
|
||||
| Level | Name | Description |
|
||||
|-------|------|-------------|
|
||||
| **Level 0** | Legacy | No cloud usage, relies solely on outdated systems |
|
||||
| **Level 1** | Initial Readiness (Ad hoc) | Some cloud experience, primarily for SaaS or specific business units, no clear strategy |
|
||||
| **Level 2** | Repeatable, Opportunistic | Established procedures, cloud services used extensively, but approach not fully systematic |
|
||||
| **Level 3** | Systematic and Documented | Documented practices, outsourced/cloud management services, efficient operations |
|
||||
| **Level 4** | Measured | Transparent governance model, cloud-native applications widely adopted across organization |
|
||||
| **Level 5** | Optimized | Open, interoperable cloud environment, data-driven decisions, flexible workload placement |
|
||||
|
||||
## Key Components
|
||||
|
||||
### Business Capability Areas
|
||||
- Finance (CAPEX to OPEX shift)
|
||||
- Enterprise Strategy
|
||||
- Organizational Structure
|
||||
- Culture and Skills
|
||||
- Governance and Compliance
|
||||
- Business Processes
|
||||
- Procurement and Commercial
|
||||
|
||||
### Technical Capability Areas
|
||||
- IT Architecture
|
||||
- Applications Modernization
|
||||
- DevOps
|
||||
- Security
|
||||
- IaaS / PaaS / SaaS / STaaS / IPaaS
|
||||
- Data and Information Services
|
||||
- Network Infrastructure
|
||||
- AI and IoT Integration
|
||||
- APIs
|
||||
|
||||
### Three Core Evaluation Dimensions
|
||||
1. **People** — Skills, ways of working, training programs
|
||||
2. **Processes** — Workflow updates, continuous improvement
|
||||
3. **Technology** — Infrastructure changes, new tech adoption
|
||||
|
||||
## Benefits of Implementing CMM
|
||||
|
||||
1. **Enhanced Strategic Planning** — Focus on high-impact areas
|
||||
2. **Improved Team Communications** — Shared framework for goals
|
||||
3. **Enhanced Application Performance** — Smoother cloud apps
|
||||
4. **Enhanced Security and Performance** — Best practices adherence
|
||||
5. **Faster Time to Market** — Efficient resource use
|
||||
6. **Industry Benchmarking** — Compare against sector peers
|
||||
7. **Cost-Savings** — Efficiency and automation emphasis
|
||||
|
||||
## Related Models and Frameworks
|
||||
|
||||
| Model | Focus |
|
||||
|-------|-------|
|
||||
| **CMM 4.8** | IT organization's business/technology functions across cloud domains |
|
||||
| **Cloud Native Maturity Model** | CNCF ecosystem, scalable applications |
|
||||
| **Cloud Security Maturity Model (CSMM)** | Cloud security across 12 categories |
|
||||
| **Software Assurance Maturity Model (SAMM)** | Entire software lifecycle |
|
||||
| **AWS CAF** | AWS-specific transformation roadmap |
|
||||
| **Azure CAF** | Microsoft Azure adoption |
|
||||
| **Google Cloud Adoption Framework** | Google Cloud transition |
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Cloud-Adoption-Strategy]]
|
||||
- [[Multi-Cloud-Strategy]]
|
||||
- [[Cloud-Native]]
|
||||
- [[DevOps-Maturity]]
|
||||
- [[FinOps]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]]
|
||||
- [[sources/cloud-operating-model-key-strategies-and-best-practices.md]]
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
40
wiki/entities/Cloud-Provider.md
Normal file
40
wiki/entities/Cloud-Provider.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Cloud Provider
|
||||
tags: [Cloud, Infrastructure, IaaS]
|
||||
---
|
||||
|
||||
# Cloud Provider
|
||||
|
||||
## Overview
|
||||
|
||||
**Cloud Provider** 指提供云计算服务的企业或组织,通过互联网按需提供计算资源、存储、应用和服务。主要云提供商形成了一个竞争激烈的市场,企业可通过多云策略在不同提供商之间分配工作负载以优化性能和成本。
|
||||
|
||||
## Major Cloud Providers
|
||||
|
||||
| Provider | Full Name | Key Strengths |
|
||||
|----------|-----------|---------------|
|
||||
| AWS | Amazon Web Services | 最早、最大生态,计算/存储/AI 最全面 |
|
||||
| Azure | Microsoft Azure | 企业级集成、Microsoft 365 深度整合、混合云 |
|
||||
| GCP | Google Cloud Platform | 数据分析、AI/ML、Kubernetes 原生 |
|
||||
| OCI | Oracle Cloud Infrastructure | 数据库、企业应用、Exadata |
|
||||
| Alibaba Cloud | 阿里云 | 亚太市场份额、中国市场首选 |
|
||||
| IBM Cloud | IBM Cloud | 企业 AI、混合云、红帽集成 |
|
||||
|
||||
## Key Concepts
|
||||
|
||||
- **IaaS** (Infrastructure as a Service): 基础架构级云服务(VM、存储、网络)
|
||||
- **PaaS** (Platform as a Service): 平台级云服务(数据库、开发框架)
|
||||
- **SaaS** (Software as a Service): 软件级云服务(CRM、ERP、协作工具)
|
||||
- **多云策略 (Multi-Cloud)**: 同时使用多个云提供商的策略
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud Strategy]]
|
||||
- [[Vendor Lock-In]]
|
||||
- [[Cloud Migration]]
|
||||
- [[High Availability]]
|
||||
- [[Scalability]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
23
wiki/entities/DORA-Metrics.md
Normal file
23
wiki/entities/DORA-Metrics.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# DORA Metrics
|
||||
|
||||
## Source
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
|
||||
## Summary
|
||||
The DORA (DevOps Research and Assessment) metrics are four key measures used to assess DevOps performance and maturity:
|
||||
|
||||
1. **Deployment Frequency** — How often code is deployed to production
|
||||
2. **Lead Time for Changes** — Time from code commit to production deployment
|
||||
3. **Change Failure Rate** — Percentage of deployments causing failures
|
||||
4. **Mean Time to Recovery (MTTR)** — Time to restore service after failures
|
||||
|
||||
## Related Sources
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]]
|
||||
|
||||
## Related Concepts
|
||||
- [[concepts/DevOps-Maturity]]
|
||||
- [[concepts/CI-CD-Pipeline]]
|
||||
|
||||
## Ingested
|
||||
- Date: 2026-04-21
|
||||
60
wiki/entities/DevOps-Maturity-Model.md
Normal file
60
wiki/entities/DevOps-Maturity-Model.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# DevOps Maturity Model
|
||||
|
||||
## Source
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**:
|
||||
|
||||
| Stage | Name | Key Characteristics |
|
||||
|-------|------|---------------------|
|
||||
| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release |
|
||||
| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing |
|
||||
| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process |
|
||||
| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring |
|
||||
| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline |
|
||||
|
||||
## Key Focus Areas
|
||||
|
||||
1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset
|
||||
2. **Automation** — AutoDevOps for continuous delivery and deployment
|
||||
3. **Structure and Process** — Standardized, small-batch, transparent processes
|
||||
4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets
|
||||
5. **Technology** — Tool selection aligned with team needs
|
||||
|
||||
## Quality Criteria
|
||||
|
||||
- Assessment criteria (standards for evaluating maturity)
|
||||
- Five maturity levels
|
||||
- Core DevOps practices (release management, CI/CD, IaC, security)
|
||||
- Relevant metrics (deployment frequency, MTTR, change failure rate)
|
||||
- Cultural guides
|
||||
- Tools and technologies
|
||||
- Roles and responsibilities
|
||||
|
||||
## Business Benefits
|
||||
|
||||
- Quicker adjustment to market changes
|
||||
- Capability to seize new opportunities
|
||||
- Better scalability via IaC
|
||||
- Enhanced operational performance
|
||||
- Faster delivery times
|
||||
- Improved quality via continuous monitoring and feedback
|
||||
|
||||
## Security Integration (DevSecOps)
|
||||
|
||||
The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production.
|
||||
|
||||
## Related Concepts
|
||||
- [[concepts/DevOps-Maturity]]
|
||||
- [[concepts/DORA-Metrics]]
|
||||
- [[concepts/DevSecOps]]
|
||||
- [[concepts/CI-CD-Pipeline]]
|
||||
- [[concepts/Infrastructure-as-Code]]
|
||||
- [[concepts/Continuous-Deployment]]
|
||||
|
||||
## Ingested
|
||||
- Date: 2026-04-21 (initial)
|
||||
- Date: 2026-04-24 (updated with Phase 1-5 details)
|
||||
41
wiki/entities/Google-Cloud.md
Normal file
41
wiki/entities/Google-Cloud.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Google Cloud Platform (GCP)
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
---
|
||||
|
||||
# Google Cloud Platform (GCP)
|
||||
|
||||
**Google Cloud Platform (GCP)** is Google's cloud computing platform, providing infrastructure and application services with strengths in AI/ML, data analytics, and container technologies.
|
||||
|
||||
## Overview
|
||||
|
||||
GCP is one of the three major public cloud providers, particularly known for Kubernetes (originated at Google), data analytics, and machine learning capabilities.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Compute Engine, Cloud Functions, GKE |
|
||||
| Storage | Cloud Storage, Filestore |
|
||||
| Database | Cloud SQL, BigQuery, Firestore, Spanner |
|
||||
| AI/ML | Vertex AI, TensorFlow, Gemini |
|
||||
| Analytics | BigQuery, Dataflow, Looker |
|
||||
| Networking | VPC, Cloud CDN, Cloud Load Balancing |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
GCP is commonly used alongside AWS and Azure in multi-cloud strategies:
|
||||
- **Machine Learning** — Often preferred for ML/AI workloads (Vertex AI, TensorFlow)
|
||||
- **Data Analytics** — BigQuery for data warehousing and analytics
|
||||
- **Container-native** — GKE (Google Kubernetes Engine) for container orchestration
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — GCP as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on GCP-native services
|
||||
- [[Kubernetes]] — GKE as managed Kubernetes
|
||||
- [[FinOps]] — Managing GCP costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
24
wiki/entities/HemantSawant.md
Normal file
24
wiki/entities/HemantSawant.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Hemant Sawant"
|
||||
type: entity
|
||||
tags: [devops, author, linkedin]
|
||||
sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]
|
||||
last_updated: 2026-04-22
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md]]
|
||||
|
||||
## Summary
|
||||
Hemant Sawant is a DevOps practitioner and thought leader who publishes articles on LinkedIn about DevOps culture, organizational transformation, Agile practices, and cloud-native engineering. The ingested article covers a comprehensive DevOps transformation framework including the four foundational pillars, Agile integration strategies, and a strategic transformation playbook.
|
||||
|
||||
## Key Claims
|
||||
- DevOps transformation requires dismantling silos between Development and Operations through cross-functional teams
|
||||
- Four foundational pillars: Collaboration, Automation, Continuous Improvement (Kaizen), Customer-Centricity
|
||||
- Agile and DevOps are symbiotic — DevOps extends Agile agility to operations
|
||||
- Transformation requires leadership buy-in, upskilling investment, and pilot-driven quick wins
|
||||
|
||||
## Connections
|
||||
- [[DevOps Culture]] — Primary topic of his writing
|
||||
- [[DevSecOps]] — Future trend mentioned in his article
|
||||
- [[GitOps]] — Future trend mentioned in his article
|
||||
30
wiki/entities/Open-Alliance-for-Cloud-Adoption.md
Normal file
30
wiki/entities/Open-Alliance-for-Cloud-Adoption.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Open Alliance for Cloud Adoption (OACA)
|
||||
source: https://www.bacancytechnology.com/blog/cloud-maturity-model
|
||||
tags: [Cloud, Framework, Organization, Cloud-Adoption]
|
||||
---
|
||||
|
||||
# Open Alliance for Cloud Adoption (OACA)
|
||||
|
||||
## Overview
|
||||
|
||||
The **Open Alliance for Cloud Adoption (OACA)** is an organization that defines and promotes the Cloud Maturity Model (CMM) as a framework for enterprise cloud transformation.
|
||||
|
||||
## Role in Cloud Maturity Model
|
||||
|
||||
OACA describes CMM as a framework that:
|
||||
- Assists organizations in identifying tailored solutions for adopting cloud or hybrid IT environments
|
||||
- Evaluates organizations' readiness for adopting the cloud
|
||||
- Helps assess their current use of cloud services
|
||||
- Sets future goals for developing a cloud migration strategy
|
||||
- Conducts GAP analysis
|
||||
- Identifies areas for improving cloud infrastructure based on business objectives
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Cloud-Maturity-Model]]
|
||||
- [[Cloud-Adoption-Strategy]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]]
|
||||
60
wiki/entities/cloud-computing.md
Normal file
60
wiki/entities/cloud-computing.md
Normal file
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Cloud Computing
|
||||
---
|
||||
|
||||
# Cloud Computing
|
||||
|
||||
**Cloud Computing** is the delivery of computing services—including servers, storage, databases, networking, software, analytics, and intelligence—over the Internet ("the cloud") to offer faster innovation, flexible resources, and economies of scale.
|
||||
|
||||
## Key Characteristics
|
||||
|
||||
- **On-demand self-service**: Provision resources as needed without human intervention
|
||||
- **Broad network access**: Access via internet from anywhere on any device
|
||||
- **Resource pooling**: Multi-tenant model with resources pooled to serve multiple consumers
|
||||
- **Rapid elasticity**: Scale resources up or down dynamically
|
||||
- **Measured service**: Pay-as-you-go pricing model
|
||||
|
||||
## Common Misconceptions
|
||||
|
||||
Cloud computing is widely misunderstood. Key myths include:
|
||||
|
||||
1. **Cloud is not secure** — Reality: Major providers invest heavily in security (encryption, MFA, ISO 27001, HIPAA, GDPR compliance) and offer 24/7 monitoring
|
||||
2. **Cloud is "someone else's computer"** — Reality: Cloud is a vast network of sophisticated data centers with redundancy, auto-failover, and global distribution
|
||||
3. **Cloud is too expensive** — Reality: Pay-as-you-go, reserved instances, auto-scaling, and serverless models can significantly reduce costs vs. on-premises
|
||||
4. **You lose control over data** — Reality: Cloud providers offer robust data governance, permissions management, and hybrid/multi-cloud options
|
||||
5. **Only for large enterprises** — Reality: SMBs and startups benefit greatly from flexible pricing and enterprise-grade technology
|
||||
6. **Migration is too complex** — Reality: Phased migration, hybrid cloud, and professional services enable smooth transitions
|
||||
7. **Performance is unreliable** — Reality: Major providers offer SLAs exceeding 99.99% uptime with redundant infrastructure and automated failover
|
||||
|
||||
## Cloud Deployment Models
|
||||
|
||||
- **Public Cloud**: Resources shared across multiple organizations (AWS, Azure, GCP)
|
||||
- **Private Cloud**: Dedicated to a single organization (on-premises or hosted)
|
||||
- **Hybrid Cloud**: Combines public and private clouds
|
||||
- **Multi-Cloud**: Uses multiple public cloud providers simultaneously
|
||||
|
||||
## Related Concepts
|
||||
## Cloud Providers
|
||||
|
||||
In multi-cloud strategies, organizations typically work with multiple providers:
|
||||
|
||||
- [[AWS]] — Amazon Web Services
|
||||
- [[Azure]] — Microsoft Azure
|
||||
- [[Google-Cloud]] — Google Cloud Platform
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Cloud Security]]
|
||||
- [[Cloud Migration]]
|
||||
- [[High Availability]]
|
||||
- [[Multi-Cloud Strategy]]
|
||||
- [[Vendor-Lock-In]]
|
||||
- [[Data-Sovereignty]]
|
||||
- [[FinOps]]
|
||||
- [[Infrastructure as Code]]
|
||||
- [[Serverless Computing]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[The Myths and Misconceptions About Cloud Computing (LinkedIn)|the-myths-and-misconceptions-about-cloud-computing-linkedin]]
|
||||
- [[How Can a Multi Cloud Strategy Transform Your Business ROI|sources/how-can-a-multi-cloud-strategy-transform-your-business-roi]]
|
||||
Reference in New Issue
Block a user