Remove Database Remove Latency Remove Scalability Remove Video
article thumbnail

Scalable Annotation Service?—?Marken

The Netflix TechBlog

Scalable Annotation Service — Marken by Varun Sekhri , Meenakshi Jindal Introduction At Netflix, we have hundreds of micro services each with its own data models or entities. The service should be able to serve real-time, aka UI, applications so CRUD and search operations should be achieved with low latency.

article thumbnail

Designing Instagram

High Scalability

Generating machine learning based personalized recommendations to discover new people, photos, videos, and stories relevant one’s interest. We will use a graph database such as Neo4j to store the information. Additionally, we can use columnar databases like Cassandra to store information like user feeds, activities, and counters.

Design 334
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

Data Reprocessing Pipeline in Asset Management Platform @Netflix

The Netflix TechBlog

Production Use Cases Real-Time APIs (backed by the Cassandra database) for asset metadata access don’t fit analytics use cases by data science or machine learning teams. Data sharding completely based on the asset type may have created the wide rows considering some types like VIDEO may have many more assets compared to others like TEXT.

Media 237
article thumbnail

Building Netflix’s Distributed Tracing Infrastructure

The Netflix TechBlog

Investigating a video streaming failure consists of inspecting all aspects of a member account. If we had an ID for each streaming session then distributed tracing could easily reconstruct session failure by providing service topology, retry and error tags, and latency measurements for all service calls. Storage: don’t break the bank!

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. This architecture shift greatly reduced the processing latency and increased system resiliency. Reloaded was well-architected, providing good stability, scalability, and a reasonable level of flexibility.

article thumbnail

Why Traditional Monitoring Isn’t Enough for Modern Web Applications

Dotcom-Montior

Modern web applications and pages, such as single-page applications, that put the user experience at its utmost priority are expected to be available 24/7, anywhere in the world, usable on any screen size, secure, flexible, scalable and be ready to meet traffic spikes on demand. Network latency. Database connectivity.

article thumbnail

Procella: unifying serving and analytical data at YouTube

The Morning Paper

When each of those use cases is powered by a dedicated back-end, investments in better performance, improved scalability and efficiency etc. That’s hard for many reasons, including the differing trade-offs between throughput and latency that need to be made across the use cases. are divided. Reporting and dashboarding use cases (e.g.