cdn_streaming_conversion_conf
Table of Contents
CDN
Implementation
Static resources - P1
- Dev
Make application use versioned static assets incl. js,css,videos, images and static pages. (except streaming). Decide on Ruby Gem. Make endpoints configurables.
- Install and configure AWS client
- DNS additions
- Deploy Script
Modify deploy script to respect versioning and push to S3.
- Recurring maintenance task
Delete old versions.
Streaming video content - P2
- Dev
Copy uploaded assets over to S3 directory and UX changes.
- Use the new endpoints.
Streaming / Conversion - P1
- Streaming / Conversion servers to be setup.
Sidenote:
Config: 4core, 2G RAM, faster IOPS. Estimated Cost: 152.21$ (Opsource).
Will originally function as dedicated streaming servers using distributed FS.
Conversion [Video] - P2
- Dev
Make application use external endpoints for video conversion. Message broker?. Discussion needed.
- AWS
Elastic transcoder expensive.
- Dedicated Server
IOPS, different data center.
Conversion [Docs] - P2
- Dev
Look into using open office TCP sockets to offload this to a dedicated conversion server.
cdn_streaming_conversion_conf.txt · Last modified: 2018/08/31 16:16 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
