ııı motion.mdVideo style specification
Supabase / V388

Supabase Pipelines — near real-time analytics sync

Visualize traffic pressure first, then explain division of responsibilities through destination configuration and continuous synchronization, giving the product a clear cause and effect.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 36.10 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Supabase Pipelines — near real-time analytics sync · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#050807}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsSource databaseRequest flow linesLatency chartDestination configuration formDestination databaseField tableSync status
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Pressure turns from normal load into a visible bottleneck

As data bars multiply on both sides of the single database, the latency panel changes from normal green to rising red. The black background keeps flow lines and values clear; magnitude and color change together so viewers understand the emerging problem.

02

Let data flow to the other end only after configuration is complete

Let data flow to the other end only after configuration is completeRule example
0.00 / 7.30 seconds
14.2–21.5 seconds · Motion example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Supabase Pipelines — near real-time analytics sync · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#050807}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="14.2" data-end="21.5"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>

Show adding a destination, selecting its type and region, and starting the pipeline in order. Draw the two databases only after startup, with thin green flow lines moving continuously from source to destination. Avoid bidirectional arrows that confuse the meaning.

03

Schema changes propagate along the same path

After a field is added to the left table, a change label travels along the connecting line. On arrival, the field appears and highlights in the right table. Keep field types and names consistent; distinguish the dark-blue destination table from the near-black source table.

04

Adapt to another synchronization product

When changing the source, destination, fields, and operation names, preserve the causal chain of pressure—workload separation—configuration—synchronization. The conclusion should explain the outcomes for production and analytics separately, rather than describing every change as faster speed.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 6.61 seconds
6.61s
Composition reference at 13.01 seconds
13.01s
Composition reference at 19.02 seconds
19.02s
Composition reference at 25.03 seconds
25.03s
Composition reference at 34.03 seconds
34.03s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • When changing the source, destination, fields, and operation names, preserve the causal chain of pressure—workload separation—configuration—synchronization. The conclusion should explain the outcomes for production and analytics separately, rather than describing every change as faster speed.

Production constraints

Source database / Request flow lines / Latency chart / Destination configuration form / Destination database / Field table / Sync status

  • Visualize traffic pressure first, then explain division of responsibilities through destination configuration and continuous synchronization, giving the product a clear cause and effect.
  • As data bars multiply on both sides of the single database, the latency panel changes from normal green to rising red. The black background keeps flow lines and values clear; magnitude and color change together so viewers understand the emerging problem.
  • Show adding a destination, selecting its type and region, and starting the pipeline in order. Draw the two databases only after startup, with thin green flow lines moving continuously from source to destination. Avoid bidirectional arrows that confuse the meaning.