Remove 2007 Remove Efficiency Remove Infrastructure Remove Innovation
article thumbnail

Rebuilding Netflix Video Processing Pipeline with Microservices

The Netflix TechBlog

The Netflix video processing pipeline went live with the launch of our streaming service in 2007. We rolled out encoding innovations such as per-title and per-shot optimizations, which provided significant quality-of-experience (QoE) improvement to Netflix members. This introductory blog focuses on an overview of our journey.

article thumbnail

Improving our video encodes for legacy devices

The Netflix TechBlog

we announced our intention to stream video over 13 years ago, in January 2007?—?and and thus fall back to less efficient encode families. Since then, we have applied innovations such as shot-based encoding and newer codecs to deploy more efficient encode families. 264/AVC Main profile family.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Scaling Media Machine Learning at Netflix

The Netflix TechBlog

We have been leveraging machine learning (ML) models to personalize artwork and to help our creatives create promotional content efficiently. Our goal in building a media-focused ML infrastructure is to reduce the time from ideation to productization for our media ML practitioners.

Media 290
article thumbnail

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

Egnyte is a secure Content Collaboration and Data Governance platform, founded in 2007 when Google drive wasn't born and AWS S3 was cost-prohibitive. Infrastructure Optimization. Egnyte was founded in 2007. What Infrastructure Do You Use? Video Transcoding. Permissions. Recommendations. Hybrid Sync. Offline access.

article thumbnail

Strategic IT Does More than Assume Technology Risk, it Mitigates Business Risk

The Agile Manager

Thus leadership and its derivative characteristics - notably innovation and responsiveness - are the result of calculated, not wanton, risk taking. Software development capacity, IT infrastructure, and software as a service are all examples of risk assumption. Look for another Capital Markets paper in July 2007.