Superior Streaming and CDN Solutions: Cloud Storage Revolutionizes Digital Media
Download as PPTX, PDF1 like2,820 views
This document discusses video streaming infrastructure requirements and how object storage can help meet those requirements. It outlines the key elements of a video streaming infrastructure, including scalable, flexible, high-performance storage. Traditional on-premises storage solutions have limitations around scaling and availability that can be addressed through an object storage approach. Object storage provides scalability to hundreds of petabytes, built-in data protection and no single point of failure. Real-world examples are presented of media companies using object storage as the origin server storage in hybrid on-premises and public cloud architectures.
More Related Content
Similar to Superior Streaming and CDN Solutions: Cloud Storage Revolutionizes Digital Media (20)
Superior Streaming and CDN Solutions: Cloud Storage Revolutionizes Digital Media
- 1. Friday, May 26, 2017 Yannick Guillerm – Director Technical Marketing Superior Streaming and CDN Solutions: Cloud Storage Revolutionizes Digital Media Making Magic
- 2. What am I going to talk about? Elements of a Video Streaming Infrastructure Requirements Zoom on the Heart of the Beast: STORAGE How can Object Storage help? Where Does Object Storage fit? Media ISV Eco System Real Examples
- 3. Elements of a Video Streaming infrastructure
- 6. Create your own streaming infrastructure – Key points SCALABLE Starts at 100TB At launch and Scale to multiple PBs with 100s subscribers FLEXIBLE Accommodate Multiple apps: Ingest Encode Browse Stream Preview etc PERFORMANCE Steady read/write perf. That will grow on demand As subscribers are added RELIABLE No downtime! Don’t want Service to stop In middle of ‘Better Call Saul’ Binge watching ADAPTABILITY Should easily adapt to: Multiple file formats/sizes New video standard New workflows New workloads New CDN providers PUBLIC CLOUD Should be compatible With public cloud Providers to take Advantage of cloud Based workflows: Encode Archive DRM etc AND … COST!!!
- 7. What you don’t want! DAAAADDD !!!
- 8. Zoom on the Heart of the Beast: STORAGE!
- 9. • Where all source streaming files are stored • Input for ingest and encoding • Output for packaging/streaming and then CDN/Edge cache and finally your device • Origin Server Storage has to: Scale in size and performance easily Accommodate multiple protocols Accommodate multiple ISV applications and workloads Be able to sustain GB/s in & out Can’t never go down: NO DOWNTIME! Origin Server
- 10. • On-Prem Storage • Pros: Known solution! Fairly “easy” to install and Administer • Cons: Does not easily scale to multi-PBs Performance limitations at Scale Limited protocols (File System only) DOWNTIME when adding capacity of upgrading software Migration when software upgrade to N+x Volume Management & quota management nightmare COST! Where People Store It All Today? - 1
- 11. • Storage at CDN Provider • Pros: Again: known solution! “Easy and convenient” – CDN to provide Origin and Edge – 1 solution • Cons: Does not easily scale to multi-PBs Technical limitations of a given CDN provider Can’t share with other CDN providers = content monetization limitations COST! Where People Store It All Today? - 2
- 12. • Object Storage – SDS based approach • Pros: Scales to 100s of PBs No downtime Very high data protection and availability Offers object and file system protocols Augment video workflows with additional use cases Storage Admin job morphing to Dev Ops Admin simplified – 1 guy to manage multi-PBs Cost • Cons: Storage Admin job morphing. Requires Linux administration There is relief!
- 13. How can Object Storage Help? What is Object Storage ?
- 14. • No File System/inode limitations: scales to 100s of PBs and beyond • Runs on Standard X86 Server: HW freedom and no NAS vendor lock • Built-in data protection and geo- distribution mechanisms: NO DOWNTIME! • Built-in rebuild, balance mechanism: very high durability and availability • Shared-nothing architecture: no single point of failure • Built-in multi-protocols: Object and File System • Much lower cost What is Object Storage VS.
- 15. From a bunch of Servers to a distributed Object Store• Standard Linux distribution install (CentOS, RHEL, Ubuntu, Debian) • Standard SDS software install SSD X 2 HDD X n RAM CPU Raid Controller X 6 Servers Rep x 3 Erasure Coding 4+2 Storage Nodes (Disk I/O Process): X 6 Linux I/O processes for Metadata traffic on SSDs X 6 Linux I/O processes for Data traffic on HDDs
- 16. Object Storage supports both legacy and modern applications Type Connector Strength Object S3 AWS S3 compatible REST API, supports AWS IAM, Active Directory (AD), Bucket/object ACLs, scale-out metadata and fast listing HTTP REST Native Scality REST API, highly scalable, lightweight File NFS NFS v3, supports Kerberos (AD), advisory-locking (NLM), and user/group quotas SMB SMB 2.x and subset of SMB 3.x FUSE Local Linux file system driver, great for application servers REST REST access to files (global namespace between file system and object) Not shown: Messaging Connectors, *Compliance requires additional license
- 17. Scalable, any-to-any data flow Scales to millions of simultaneous requests • Any application can talk to any connector • Any connector can talk to any storage node Connectors • Are stateless and can be load balanced • Multiple connectors can share the same namespace Consistent response time at scale • Storage nodes retrieve requested data or find the correct node deterministically, no matter the scale • No central metadata databases or indexes, no lookups needed for replicas • Lookups are cached, they are only needed on recent topology changes APPLICATION A APPLICATION B APPLICATION N HDD … STORAGE NODE CONNECTOR (File) CONNECTOR (Object) CONNECTOR N STORAGE NODE STORAGE NODE N HDD … HDD …
- 18. What will an Object Storage deployment look like? Web/Mobile Applications S3 or REST based Applications IP SW LOAD BALANCED HTTP/S IP LOAD BALANCED SDS software Local & Geo-protection Self-healing Scale-out object storage Management & Monitoring Security Windows Applications Linux Applications Compliance STORAGE SERVICES: RUNS ON YOUR CHOICE OF x86 PHYSICAL SERVERS ACCESS SERVICES (CONNECTORS): RUNS WITH THE STORAGE SERVICES OR SEPARATE SERVERS (PHYSICAL OR VMs) TOR SWITCHES S3 REST OBJECT ACCESS NFS SMB FUSE REST FILE ACCESS
- 19. Where Does Object Storage fit? – ORIGIN SERVER STORAGE
- 20. Object Storage as Origin Server Storage
- 21. A trend/reality – “Hybrid” On-Prem + Public Cloud Approach
- 24. Real Examples
- 25. HTTP/REST HTTP/REST HTTP/REST HTTP/REST HTTP/REST CDMI NFS NFS HTTP/REST CDN CDN CDN USPServer Transcoding LiveDVR Encoders USPServer USPServer ScalityRINGStorage Local and Geo-Protection • Any Hardware File / Object / OpenStack • Multi-Workload HTTP Live Streaming (HLS) HTTP Dynamic Streaming (HDS) Microsoft Smooth Streaming UnifiedOrigin
- 26. ScalityRINGStorage Local and Geo-Protection • Any Hardware File / Object / OpenStack • Multi-Workload CDN 1 CDN 2 CDN 3 Multi-bitrate Multi-resolution Content Processing System All Content andElementary Streamsfor Deliveryin MP4s& AudioStreams JITPServers HTTPServers StreamingServers CDNOrigin(Prepackaged top~10% of Content) + EdgeServers Asset Library/CPS Metadata
- 27. Questions?
- 28. Thank You ! Booth #SL8505 www.scality.com
Editor's Notes
- #17: We don’t want to talk about OpenStack in the slides anymore. It is there for older versions of OpenStack if you’re asked the question but we don’t do any development in regards to OpenStack anymore. So we got rid of the OpenStack section for the protocols. CDMI: we don’t mention CDMI on purpose in this slide anymore. We really want to favor the S3 protocol. But again CDMI still exists and is supported so if you’re asked it is there.
- #18: Animated slide
- #19: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.
- #21: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.
- #22: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.
- #24: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.
- #26: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.
- #27: Like in slide 5 – No mention of CDMI in the slide on purpose to favor the S3 protocol. But CDMI is still out there if you’re asked.