멀티 클라우드 서비스 매트릭스

같은 기준으로 클라우드 기능을 비교합니다.

AWS, Google Cloud, Azure, Cloudflare의 동등한 서비스를 찾고 운영 모델과 제약을 비교합니다.

비교 그룹 6개

스토리지

Object storage

Store unstructured objects behind HTTP APIs for applications, analytics, media, and archives.

AWS

Amazon S3

사용 시점: Broad object-storage platform and data-lake foundation
운영: Bucket policy, IAM, lifecycle, replication, and a large integration surface
특성: Strong read-after-write consistency with many storage classes
확인 사항: Data transfer, request tiers, and optional features make cost modeling detailed

서비스 가이드 열기

Google Cloud

Cloud Storage

사용 시점: Object storage integrated with analytics and machine-learning services
운영: Uniform access, lifecycle, Autoclass, and regional or multi-region placement
특성: Strong global consistency with automatic class management options
확인 사항: Location type and data-processing region should match the surrounding pipeline

서비스 가이드 열기

Azure

Blob Storage

사용 시점: Object and data-lake storage for Azure applications and Microsoft data tooling
운영: Storage accounts, containers, access tiers, lifecycle, and private endpoints
특성: Block, append, and page blob types with hierarchical namespace option
확인 사항: Storage-account boundaries and feature compatibility require early planning

Cloudflare

R2

사용 시점: S3-compatible objects served through Workers and Cloudflare's network
운영: Buckets, bindings or S3 API, lifecycle, event notifications, and cache
특성: Strong consistency and no internet egress fee
확인 사항: The ecosystem and storage-class range are narrower than hyperscaler object stores

서비스 가이드 열기

컴퓨트

Serverless runtime

Run request or event-driven application code while the provider manages capacity and scaling.

AWS

AWS Lambda

사용 시점: Short event-driven functions across the AWS service ecosystem
운영: Functions, versions, concurrency, event sources, and IAM roles
특성: Invocation-based scaling with bounded execution duration
확인 사항: Cold starts, packaging limits, and per-service integration settings shape design

서비스 가이드 열기

Google Cloud

Cloud Run

사용 시점: Portable HTTP services and jobs packaged as containers
운영: Revisions, service identity, concurrency, min instances, and traffic splitting
특성: Request-driven container scaling, including scale to zero
확인 사항: Long-running state must live outside instances and startup cost depends on the image

서비스 가이드 열기

Azure

Azure Functions

사용 시점: Event-driven functions integrated with Azure triggers and bindings
운영: Function apps, hosting plans, deployment slots, identities, and bindings
특성: Multiple hosting plans trade scale behavior against isolation and predictability
확인 사항: Plan choice materially changes networking, cold starts, and execution limits

Cloudflare

Workers

사용 시점: Low-latency APIs and web applications across a global edge network
운영: Deployments, routes, bindings, observability, and compatibility flags
특성: Isolate-based execution with rapid global startup
확인 사항: CPU and runtime constraints favor web-native, bounded workloads

서비스 가이드 열기

컨테이너

Container platform

Operate containerized workloads that need more control than a function or request-only runtime.

AWS

Amazon EKS

사용 시점: Managed Kubernetes integrated with AWS networking and identity
운영: Clusters, node groups or Auto Mode, add-ons, upgrades, and IAM
특성: Upstream Kubernetes control plane with flexible worker capacity
확인 사항: Kubernetes and VPC complexity remain part of the operating model

서비스 가이드 열기

Google Cloud

GKE

사용 시점: Managed Kubernetes with Autopilot and fleet policy options
운영: Clusters, release channels, Autopilot or nodes, fleets, and workload identity
특성: Deep Kubernetes automation and Google-originated operational patterns
확인 사항: Standard mode still requires deliberate node, networking, and upgrade management

서비스 가이드 열기

Azure

AKS

사용 시점: Managed Kubernetes for Azure and Microsoft-centric environments
운영: Clusters, node pools, Entra identity, networking, upgrades, and policy
특성: Kubernetes integrated with Azure networking and governance
확인 사항: Networking mode and identity choices are hard to change later

Cloudflare

Containers

사용 시점: On-demand full-process workloads coordinated by Workers
운영: Container images, instances, lifecycle API, Worker control plane, and storage
특성: Container capacity attached to Cloudflare's edge application platform
확인 사항: It is not a managed Kubernetes service and has a newer operational ecosystem

서비스 가이드 열기

메시징

Asynchronous messaging

Decouple producers and consumers, absorb bursts, and retry work outside the request path.

AWS

Amazon SQS

사용 시점: Work queues with standard or FIFO delivery
운영: Queues, visibility timeout, redrive policy, consumers, and IAM
특성: Pull-based queue semantics with at-least-once standard delivery
확인 사항: Fan-out usually adds SNS or EventBridge

서비스 가이드 열기

Google Cloud

Pub/Sub

사용 시점: Topic-based event distribution and streaming ingestion
운영: Topics, subscriptions, retention, filters, schemas, and identities
특성: Each subscription tracks delivery independently for fan-out
확인 사항: Queue and ordered-processing patterns need subscription and ordering-key design

서비스 가이드 열기

Azure

Service Bus

사용 시점: Enterprise queues and topics with ordering and transactions
운영: Namespaces, queues, topics, subscriptions, sessions, and rules
특성: Broker features include sessions, dead lettering, duplicate detection, and transactions
확인 사항: Throughput tiers and namespace capacity need explicit planning

Cloudflare

Queues

사용 시점: Managed delivery to consumer Workers near the rest of a Cloudflare application
운영: Queues, producers, consumers, batching, retries, and dead letters
특성: Push or pull consumption with at-least-once delivery
확인 사항: The broker feature set is intentionally smaller than enterprise messaging suites

서비스 가이드 열기

Generative AI platform

Access foundation models and build governed AI applications with evaluation, retrieval, and observability.

AWS

Amazon Bedrock

사용 시점: Managed access to multiple model providers inside AWS
운영: Model access, inference profiles, guardrails, knowledge bases, and agents
특성: Serverless model APIs with AWS identity and network controls
확인 사항: Model availability, region, and feature support vary by provider and model

Google Cloud

Vertex AI

사용 시점: Unified custom ML and generative AI development on Google Cloud
운영: Models, endpoints, pipelines, RAG, evaluation, monitoring, and IAM
특성: Managed model lifecycle plus Gemini and partner model access
확인 사항: The platform is broad, so teams need clear boundaries between training and application layers

서비스 가이드 열기

Azure

Azure AI Foundry

사용 시점: Model catalog and AI application tooling integrated with Azure
운영: Projects, model deployments, content safety, evaluations, and connections
특성: Strong Microsoft and Azure OpenAI integration
확인 사항: Naming, portal surfaces, quotas, and regional model availability change frequently

Cloudflare

Workers AI + AI Gateway

사용 시점: Run or route inference close to edge applications
운영: Model bindings, gateway routing, caching, rate limits, logs, and provider keys
특성: Edge-native inference and a control plane for multiple external providers
확인 사항: Training and deep model lifecycle tooling are outside the core platform

에지

Edge delivery and CDN

Cache and secure web content close to users while controlling origins, routing, and invalidation.

AWS

CloudFront

사용 시점: CDN tightly integrated with AWS origins and security services
운영: Distributions, behaviors, cache policies, origins, functions, and invalidations
특성: Global cache with detailed per-path behavior configuration
확인 사항: Policy combinations and data transfer pricing take time to model

Google Cloud

Cloud CDN

사용 시점: CDN attached to Google Cloud external load balancing
운영: Backend services, cache modes, signed URLs, invalidation, and Cloud Armor
특성: Global anycast entry through the load-balancing stack
확인 사항: The load balancer is a required architectural component rather than an optional front end

Azure

Azure Front Door

사용 시점: Global application delivery, acceleration, and web protection
운영: Profiles, endpoints, routes, origins, rules, WAF, and private link
특성: Layer 7 global routing and CDN in one service
확인 사항: Classic and Standard/Premium generations differ, so migration state matters

Cloudflare

Cloudflare CDN

사용 시점: Reverse-proxy CDN and security in front of internet origins
운영: Zones, DNS proxying, cache rules, WAF, Workers, and tiered cache
특성: Anycast network with security and compute on the same request path
확인 사항: Some enterprise routing and cache controls depend on plan level