Origin / Edge Server

What is it?

These are the two roles in a content delivery setup:

• Origin = the single source of truth. The server where the freshly processed stream actually lives.
• Edge = the many local copies. Servers near viewers that fetch from the origin once, then serve thousands of nearby people.

Think of a newspaper: the origin is the printing press; the edges are the newsstands in every neighborhood. Readers buy from the newsstand — nobody queues at the press.

Practical example

During a big live event, two million people press play. The edges in each region request the new video chunk from the origin once, then hand it out locally to everyone nearby. The origin answers a few hundred requests instead of two million — that's the whole trick behind surviving viral moments.

Key things to know (non-technical)

• Viewers should never hit the origin directly; if they do (a "cache miss" storm), the origin can fall over exactly when the event matters most.
• "Edge" is simply where the CDN meets the viewer — the last stop before their screen.
• One origin can feed edges worldwide; protecting the origin = protecting the whole broadcast.
• Backup origins exist for the same reason backup ingest does: no single point of failure.

In Tupic Live

Tupic Live's architecture should keep a small, protected origin per stream and lean on CDN edges for all viewer traffic — this is what makes the difference between "the app died during our biggest event" and a smooth viral night.