Skip to main content

Media distribution platform

Media distribution platforms focus on effective distribution of the media content, predominantly videos. With the increasing demand on enabling the web presence with dynamic video content, the platform adds immense value paving ways for generating revenue. It is not unusual to see the popular content management organizations will expand to provide media distribution services.

In simple words, media distribution involves content ingestion, content processing, content categorization, content management, content protection, content distribution, content delivery targeted specifically to content consumption layer.

Content ingestion is a process of gathering content from various sources. When acquired from various sources, they need to converted in uniform format to manage it efficiently. For example, news clip recorded on the field can be in raw digital format, or user generated home video uploaded to the system, or Warner brothers new movie made available in the system. Before making the content available, the content needs to be verified that whether the content needs to be re-purposed in a format that system can manage. Content ingestion may also consider transcoding the content into different formats for delivery. For example, the content is transcoded with 3gp format for mobile consumption. Content ingestion can be manual or automatic. In automated version, content ingestion works on the metadata. Content ingestion will involve workflow management in the bigger operations.

Content management is the next big chunk in the system, that focusses on content processing, metadata management, categorization of content, content access and protection mechanisms, internal communication mechanisms and external communication mechanisms that keep the entire platform operational. Pre-dominantly it comprises of repository management, asset management, restrictions/rights management sub systems.




While content ingestion and management form the start link of the disribution channel, content delivery mechanism forms the end link of the channel. Mainly, web browser, set top box, mobile devices form the consumption layer for which content delivery mechanism has to be designed. Delivery mechanism's prime responsbility is to deliver the content with minimum or no latency, as the latency will have the major impact on the experience. Content delivery happens through content delivery networks (CDN). CDNs can be either self hosted infrastructure or third party services from the providers like Akamai. CDNs are specialized to deliver content from the optmized end point for the end user.

End user experience is of utmost priority in a distribution framework. Most platforms will have specialized CRMs, analytical softwares to determine the user behavior, monitor user interactions and so on...

Comments

Popular posts from this blog

Essential GCP services for a new age application

Identity and resource management IAM  Identity aware proxy Resource Manager Stackdriver Monitoring Stackdriver Monitoring: Infrastructure and application monitoring Stackdriver Logging: Centralized logging Stackdriver Error Reporting: Application error reporting Stackdriver Trace: Application performance insights (latency) Stackdriver Debugger: Live production debugging Development management Cloud Deployment Manager: Templated Infrastructure deployment Cloud Console: Web based management console Cloud shell: Browser based terminal/CLI Development tools Cloud SDK: CLI for GCP Container registry: Private container registry Container builder: Build/Package container artifacts Cloud source repository: Hosted private git repository Database services Cloud SQL: Managed MySQL and PostgreSQL Cloud BigTable: HBase compatible non-relational DB Cloud Datastore: Horizontally scalable non-relational (ACID) Cloud Spanner: Horizontally scalable relation...

GCP: GAE - Memcache best practices

Memcache is a distributed in-memory data cache in front of or in place of robust persistent storage for some tasks. GAE includes a memory cache service for this purpose. Best practices for using memcache: 1. Handling memcache API failures gracefully; Do not expose errors to the end users 2. Use batching capability of the API when possible 3. Distribute load across your memcache keyspace Use sharding and aggregating for improving performance efficiency. Use TTL (expiration policy) to make sure the memcache does not fill-up indefinitely Use getIdentifiable() and putIfUntouched() for managing the values that may get affected by concurrent updates Use batching (getMulti ("comments", "commented_by") ) to fetch related values together instead of one by one Use graceful error handling

RAID Levels: Redundant Array of Independent Disks

Standard RAID levels comprise of configurations that employ the techniques of * STRIPING * MIRRORING * PARITY  to create large reliable data stores using general purpose HDDs. Levels are standardized by SNIA (Storage Networking Industry Association) in Common RAID Disk Drive Format (DDF) RAID 0 >> STRIPING (No fail-over, No Redundancy, Total loss of information if disk fails, each disk size will be of smallest disk size in the set of the disks) RAID 1 and its variants >> MIRRORING (Copy of write will be in more than one disk, Redundancy, less performant) RAID 5 >> Distributed PARITY RAID 6 >> Dual PARITY Source:   Wikipedia