Archiving: Introduction

In Course 2, you built a working multiparty room and verified the live media flow.

Now you add archiving to that same app: recording controls in the UI, backend archive handlers, and playback when recording is complete.

You will follow the same order used across this path: define user-facing behavior first, then wire server-side archive actions, and finally validate the full recording lifecycle end to end.

You can keep using the same backend/frontend setup from Course 2 and focus only on the recording-specific pieces.

If you want a quick refresher before starting, check Archiving overview and How events work.

Recording flow

• UI triggers start/stop actions.
• Backend routes start and stop archives.
• UI reacts to archive events and exposes playback when available.

Archive events used by the client UI

When an archive recording starts and stops, events are emitted in the clients. For example, the OpenTok.js library includes archiveStarted and archiveStopped events dispatched by the Session object.

What you must verify in this course

• Start/stop actions are reliable.
• UI state matches archive state.
• Playback route works when archive status is available.