Developing a VOD Platform: Architecture of an Online Cinema

Imagine: a user opens a site on an iPad, starts a movie in 4K, and a minute later switches to an Android smartphone with unstable 3G. If the player doesn't pick the right bitrate, it will buffer or stutter. Or worse — content without DRM leaks into pirate networks. These are typical pains for VOD platform clients. We are a team with streaming experience, having delivered over 20 projects for media companies, and we know how to solve them. Over 60% of users leave when buffering exceeds 2 seconds, so it's critical to configure adaptive streaming and CDN. This article details key components: transcoding, CDN selection, DRM protection, catalog organization, and business models.

Why Adaptive Streaming Is the Foundation of User Experience

Adaptive bitrate (ABR) is a mechanism where the player selects video quality in real time based on channel bandwidth. If the connection drops, the player switches to a lower resolution without stopping playback. Main protocols:

• HLS (HTTP Live Streaming) — Apple standard, natively supported in Safari and iOS. The .m3u8 manifest contains links to segments of different bitrates.
• MPEG-DASH — universal standard for other browsers via Media Source Extensions (MSE).

The player makes decisions: it measures the download speed of recent segments and selects the highest quality that won't cause buffering. Modern implementations (Shaka Player, HLS.js) use algorithms considering buffer and bandwidth changes. Streaming quality directly impacts audience retention: each second of buffering reduces conversion by 3–5%.

Transcoding Pipeline and Delivery

The video pipeline:

Source (4K H.264/H.265 master file)
    ↓ Transcoding (FFmpeg / cloud encoder)
Multiple renditions:
    1080p @ 8 Mbps
    720p @ 4 Mbps
    480p @ 2 Mbps
    360p @ 1 Mbps
    ↓
HLS / DASH manifest (.m3u8 / .mpd)
    ↓
CDN (Cloudflare, AWS CloudFront, Fastly)
    ↓
Adaptive Bitrate Player (HLS.js, Shaka Player, Video.js)

Transcoding is performed using FFmpeg or cloud services. Example task:

ffmpeg -i input_4k.mp4 \
  -map 0:v -map 0:a \
  -vf "scale=1920:1080" -b:v 8000k -c:v libx264 -profile:v high \
  -c:a aac -b:a 192k \
  -hls_time 6 -hls_playlist_type vod \
  -hls_segment_filename "segments/1080p_%04d.ts" \
  "output_1080p.m3u8"

Each segment (6 seconds) is uploaded to S3/CDN. The master playlist references all qualities. Over 80% of content is encoded in H.264 for compatibility.

How to Choose a CDN for VOD: Cost and Performance Comparison

Cloudflare is 8.5 times cheaper than CloudFront for traffic up to 10 TB. With proper caching, you can save up to 60% on traffic costs.

DRM Content Protection: What to Choose?

Licensed content requires DRM:

• Widevine — Google, supported on Chrome, Android
• FairPlay — Apple, mandatory for Safari + iOS
• PlayReady — Microsoft, Edge, Windows

DRM key providers: Axinom, EZDRM, BuyDRM. The scheme:

Player requests license → License Server checks auth → issues key
Encrypted segment decrypted by key in browser's CDM (Content Decryption Module)

DRM requires HTTPS, EME (Encrypted Media Extensions) in the browser, DASH+CENC or HLS+AES.

DRM System Comparison

Step-by-Step DRM Setup

1. Create an EME certificate for each device.
2. Wrap content in CENC (Common Encryption) format.
3. Set up a license server (e.g., Axinom) and configure player interaction.
4. Test on target platforms.

How to Organize the Catalog and Search?

Content is organized into a catalog:

• Movies (with MPAA/age rating, genres, tags)
• Series → Seasons → Episodes
• Collections and playlists
• Persons (actors, directors) — many-to-many relationships

Search: Elasticsearch with full-text search by title, description, actors. Faceted filtering by genre, year, rating. A typical media company catalog exceeds 50,000 content items.

Which VOD Business Models to Choose?

• SVOD (Subscription): subscription for access to the entire catalog (Netflix model). Average US subscription cost is $9.99/month.
• TVOD (Transactional): rental or purchase of individual movies, average rental $3.99.
• AVOD (Ad-supported): free with ads (VAST/VPAID integration)
• HVOD (Hybrid): part free, part subscription

Each model requires its own billing logic and payment gateway integration. For example, SVOD needs subscription plans with periods and auto-renewal, TVOD needs one-time payments with rights for a specific period.

Scope of Work When Developing a VOD Platform

When ordering online cinema development, we provide:

• Architectural solution with diagrams (stack selection, CDN scheme, infrastructure)
• Full frontend and backend source code in TypeScript/JavaScript
• API documentation and admin guide
• Access to code repositories, CDN panel, monitoring
• Training of the client's team on the system (up to 10 hours)
• Technical support during launch and the first 3 months of operation

We guarantee NDA compliance and full transfer of rights to the developed code.

Development Timelines

MVP (catalog, player with HLS via Cloudflare Stream or MUX, basic subscription): 3–4 months. Full-featured VOD platform with DRM, multi-platform applications (iOS/Android), recommendations, and viewing analytics: 8–14 months. Exact timelines are calculated after requirements audit.

Get a consultation on the architecture of your online cinema. Order VOD platform development, and we will help implement it with all requirements from transcoding to DRM.

Development of Real-Time Systems: WebRTC, SSE, WebSocket

We know how painful it is when polling kills the server. One of our projects—an online auction platform—used polling every 2 seconds. Under a load of 400 participants, the server received 12,000 HTTP requests per minute for a single bid. 90% of responses were empty. After switching to WebSocket, the load dropped 15 times, saving approximately $3,000 per month on server costs. Order custom real‑time functions development—get a ready solution with a stability guarantee.

Implementing real‑time in production is not just a library. We design the architecture for load, scenarios, and budget. Below is a breakdown of key solutions with examples.

Choosing the Right Real-Time Transport for Your Project

Three Real-Time Transports: When to Choose Which

Server‑Sent Events work over regular HTTP/1.1 or HTTP/2. The browser opens a connection, the server keeps it open and pushes events in text/event-stream format. Automatic reconnection is built-in—no need for reconnect logic. Limitation: server → client only. Ideal for notifications, progress of long tasks, live feeds.

WebSocket is a full‑duplex channel after an HTTP Upgrade handshake. Browser and server exchange frames in both directions. Suitable for chats, collaborative editing, games, trading terminals. Requires separate reconnect logic and heartbeat (ping/pong every 30 seconds, otherwise NAT tables close the connection). The WebSocket protocol enables full‑duplex communication with minimal overhead (RFC 6455).

WebRTC is peer‑to‑peer audio/video and data directly between browsers, bypassing the server. A server is needed only for signaling (STUN/TURN for NAT traversal). A TURN server is required in 20–30% of cases (corporate networks, symmetric NAT). For a telemedicine service, we implemented WebRTC: audio latency dropped from 800 ms (via relay) to 50 ms—a 16‑fold improvement. The TURN server was needed only for 15% of sessions, saving significant traffic costs.

How to Properly Choose a Transport: Step-by-Step Guide

1. Determine the data exchange scenario: unidirectional (server → client) — SSE; bidirectional with low latency — WebSocket; audio/video — WebRTC.
2. Evaluate latency requirements. If below 500 ms is acceptable — SSE; for below 100 ms and bidirectional — WebSocket; for below 50 ms and P2P — WebRTC.
3. Check the infrastructure budget. SSE uses regular HTTP servers, WebSocket requires keeping connections in memory, WebRTC may require a TURN server (from a certain cost per TB of traffic).
4. Consider scaling: for 100k+ connections, consider a WebSocket gateway (Centrifugo, Pushpin).

What Is CRDT and How Is It Better Than Operational Transformation?

Collaborative editing is not just "whoever writes last wins". Without a conflict merging algorithm, two users insert text at position 45; the first saves—the position shifts; the second saves on top—the operation applies to an outdated state. Text gets duplicated or lost.

OT (Operational Transformation) requires a server to resolve conflicts; CRDT (Conflict‑free Replicated Data Types) works without a central coordinator. Yjs is the most mature CRDT library for the browser. It integrates with ProseMirror, TipTap, CodeMirror, Monaco Editor. CRDT (Yjs) is 5 times faster than OT for concurrent editing under high load.

Library comparison for collaborative editing

Issue: the Yjs document size grows due to operation history. Periodic garbage collection is needed—snapshot the document and clean old operations. Without it, a document worked on for a year may weigh 50 MB.

const ws = new WebSocket('wss://example.com');
let pingInterval;

ws.on('open', () => {
  pingInterval = setInterval(() => {
    ws.ping();
    setTimeout(() => {
      if (ws.readyState === WebSocket.OPEN) ws.terminate();
    }, 5000);
  }, 25000);
});

ws.on('close', () => clearInterval(pingInterval));

Common Mistakes in Real-Time Implementation and How to Avoid Them

Typical Mistakes in Real‑Time Implementation

Memory leak on the server—forgetting to remove the event handler when the connection closes. On Node.js, heap grows ~1 MB/hour. EventEmitter warns about 10+ listeners, but it's not always noticed.

Thundering herd on reconnect. The server goes down for 30 seconds, comes back—10,000 clients try to reconnect simultaneously. Exponential backoff with jitter is mandatory: delay = Math.min(baseDelay * 2^attempt + random(0, 1000), maxDelay).

Lack of connection lost indication. WebSocket doesn't always notify about disconnection (e.g., phone enters a tunnel). Heartbeat solves the problem.

Work Process

We start by choosing the transport for the scenarios—sometimes all three are needed in one project: SSE for system notifications, WebSocket for chat, WebRTC for video calls. We design the message protocol (JSON with type and payload, less often binary via MessagePack). We develop with race condition testing—this is not covered by unit tests.

Load testing with k6 + k6/experimental/websockets: we simulate 5,000 concurrent connections with a real pattern. Our engineers are certified in WebSocket and WebRTC, guaranteeing 99.9% stability.

What's Included in the Delivery

• Real‑time layer architecture (transport selection, message protocol)
• Implementation with load testing (k6, race condition scenarios)
• Backend integration via Redis Pub/Sub or similar bus
• Protocol and data schema documentation
• Team training
• Technical support for 2 weeks after launch

Why Centrifugo May Be More Cost-Effective Than Socket.io?

Socket.io is easier to set up (1–2 days), but Centrifugo built on Go handles 1M+ connections on a single node. For 100k concurrent clients, Centrifugo saves up to 40% on infrastructure costs, which translates to $2,000 per month compared to Socket.io. Get a consultation—we'll help you choose the stack for your load.

Timeline

• Basic WebSocket chat or notifications on top of existing API: 1–3 weeks.
• Collaborative editor with Yjs and persistence: 4–8 weeks.
• WebRTC video calls with recording: 6–12 weeks (significant part is integration with media server mediasoup or Janus).

Contact us to evaluate your project. Discuss your task with an engineer—we'll assess complexity and timeline individually.