[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-14。"],[[["\u003cp\u003eCloud CDN accelerates web content delivery by caching static assets like CSS, JavaScript, and images closer to users, while Media CDN is optimized for high-throughput media streaming and large file downloads.\u003c/p\u003e\n"],["\u003cp\u003eCloud CDN is ideal for small, high-rate object delivery, such as for ad tech and e-commerce, and is also suitable for compliance-heavy needs like serving firmware downloads.\u003c/p\u003e\n"],["\u003cp\u003eMedia CDN excels at handling large-scale video streaming and software downloads due to its origin shielding, high capacity, and detailed logging capabilities.\u003c/p\u003e\n"],["\u003cp\u003eNeither Cloud CDN nor Media CDN are suitable for real-time video delivery using RTMP or WebRTC protocols, or for serving sensitive, user-specific data.\u003c/p\u003e\n"],["\u003cp\u003eA multi-CDN strategy using both Cloud CDN and Media CDN, or combining them with other providers, can improve performance, reduce costs, and provide failover capabilities during outages.\u003c/p\u003e\n"]]],[],null,["# Choose a CDN product\n\n[Cloud CDN](/cdn/docs/overview) is Google Cloud's web acceleration Content Delivery\nNetwork platform that helps you cache regularly accessed static content closer to your users.\nCloud CDN is optimized for serving a mix of static and dynamic\nlatency-sensitive web assets, such as CSS, JavaScript, HTML, and image files.\n\n[Media CDN](/media-cdn/docs/overview) is Google Cloud's media delivery CDN\nplatform that complements Cloud CDN. Media CDN is optimized for\nhigh-throughput egress workloads such as streaming video and large file downloads.\n\nUsing Cloud CDN and Media CDN can improve performance for your\nusers, lower your origin infrastructure resource usage, and reduce your network\ndelivery costs.\n\nThe two products support a similar set of features, but each product is\noptimized for certain use cases. Comparing Cloud CDN to\nMedia CDN is similar to comparing Cloud SQL to BigQuery.\nCloud CDN and Cloud SQL are for *small* queries at scale.\nMedia CDN and BigQuery are\ndesigned for throughput and extreme scale. Using Media CDN for serving\nJavaScript or CSS (web workloads)\nis similar to trying to use BigQuery for 5-GB tables with a few\nthousand rows. It works, but it's not optimized for that use case.\n\nUse cases\n---------\n\nThe following table describes some common use cases and the recommended CDN product.\n\n### Exceptions\n\nThe following table describes use cases where Cloud CDN\nor Media CDN aren't suitable.\n\nGet started with a CDN product\n------------------------------\n\nTo start working with a CDN product, see the following pages:\n\n- [Cloud CDN](/cdn/docs/overview)\n\n- [Media CDN](/media-edge/docs/overview)\n\nSupported CDN features\n----------------------\n\nThe following tables summarize the features available in Cloud CDN and\nMedia CDN.\n\n### Origin and backend support\n\n### Caching\n\n### Route matching and origin selection\n\n### Supported protocols\n\n### Logging and monitoring\n\n### Automation and APIs\n\n### Security\n\n### Edge computing\n\n### Content authentication\n\n### Compliance\n\nTransition between the two products\n-----------------------------------\n\nIf you already have a multi-CDN deployment with CDN steering and\nswitching products, you can transition between them by using DNS, or\nconfigure one of them as an additional CDN.\n\n[Cloud DNS server policies](/dns/docs/policies) might be an option for\nrouting traffic between CDNs or transitioning from one CDN to the other.\n\nUse a multi-CDN strategy\n------------------------\n\nTo optimize performance and lower costs, you can use Cloud CDN and\nMedia CDN with each other or with other CDNs by implementing\nmulti-CDN deployment strategies.\n\nMulti-CDN strategies, where your content is hosted with more than one CDN\nprovider, can help you optimize CDN services by region and CDN capabilities\noffered by different providers. They can also be useful if you host high-traffic\nevents and need to distribute traffic to multiple providers. In the case of\nmicro-outages with one provider, you can quickly shift traffic to another CDN\nprovider.\n\nA CDN deployment with a primary CDN and a secondary CDN is an example of a\nmulti-CDN deployment strategy. The primary CDN serves the majority of traffic,\nand the secondary serves a minority. If there are issues with the primary CDN,\nusers can direct traffic to the secondary CDN as a failover strategy and not\nhave to wait the usual period for the cache to get hot while already serving\ncontent.\n\nTo get started, route traffic to each CDN or split a portion of your existing\ntraffic to a new CDN using [DNS server policies](/dns/docs/policies) or\nsimilar traffic redirection services."]]
