Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Snapshots: comparing a Grid with its past self

Save a named milestone, diff the live Grid against it, and put the Grid back if you need to.

Memory can tell you a Grid changed since the review. It cannot tell you that one component was added and one connection replaced by two, while eleven other boxes only moved. A snapshot, a named point-in-time copy of a Grid, gives you something to check against, and a diff lists what is different now.

Saving a milestone

Open the panel with the history icon in the editor's top bar (Review snapshots & diff). Type a name and click Save snapshot. Name it after the decision or milestone it holds, such as "before the review" or "v1 shipped". Left blank, it is saved as "Untitled snapshot", which tells the next reader nothing. A Grid keeps up to 50 named snapshots.

NoteCapturing a snapshot needs the Premium plan. Viewing and diffing snapshots that already exist stays open to any Grid manager, so a Grid's history stays readable even if the plan behind it changes; restoring one, like capturing, needs Premium. A Grid manager is the Grid's owner, not someone invited with edit access.

On Premium the app also keeps an automatic history while a Grid manager has the Grid open to edit: a milestone at most every ten minutes, and only if something changed. The last twenty are kept, in a pool of their own that never evicts a named one, and they appear in the list as "Automatic snapshot". So save a named snapshot for a moment you would deliberately compare against; the automatic ones land on a timer, and the oldest drops off.

What the comparison lists

The compare icon on a snapshot shows the difference from that snapshot to the current Grid, and comparing writes nothing to the Grid. It always runs against the live Grid: you cannot compare two old snapshots with each other. After a summary line and counts, it lists components added, removed, renamed or edited (with the field named), connections added, removed or changed (a different endpoint or label), frames added, removed, renamed or holding different members, and comments added, removed or changed, listed under Notes.

Layout changes are reported separately, on purpose

Dragging a subsystem to a tidier position is not a design change, so a node that was only moved or resized goes into a moved count and is not listed by name. A node that moved and was also renamed or edited shows up as the rename or the edit.

The kind of change a diff names for you

Suppose the review's outcome was "put a queue between the API and the worker", and this is the Grid afterwards. If you deleted the old direct connection and drew two new ones, the summary against the earlier snapshot reads 1 component added · 2 connections added, 1 connection removed, and nobody has to take your word for it.

The comparison has blind spots. A new node color or edge style is not reported, and neither are walkthroughs, so "This snapshot matches the current Grid" means the structure matches.

It also reports change, not correctness: you still have to judge whether each change should have happened. Checking a diagram: Explain and Simulate is for that question, and Presenting a Grid: walkthroughs and scenario overlays is for taking people through the result.

Putting the Grid back

The restore icon replaces the live Grid with the snapshot after you confirm. It arrives as a normal edit, so undo still works and everyone connected sees it. The Grid's title and its walkthroughs go back too, whether or not the diff showed them. Scenario overlays are not part of a snapshot, so restore leaves the current ones alone. If you may want today's version later, save it as a snapshot first.

To take back one thing, use the button beside a component or connection in the comparison: it re-creates what was removed, reverts what changed, or removes what was added. Entries under Frames and Notes do not have one. It needs the same plan as restore, and edit access.

Watch outThe bin icon on a snapshot deletes it at once, with no confirmation and no undo. Snapshots also live inside their Grid, so permanently deleting the Grid removes them. A copy outside the product is a file: Getting diagrams in and out.

Say it first, then compare

On Premium, draw your first honest design for the Rate Limiter Challenge on a new Diagram Grid, because the snapshot panel is missing from a Challenge's own Grid, and save a named snapshot. Then revise it against the brief's demand that the limit works across multiple server instances. Before you open the comparison, describe your change in one sentence. Then read the diff and see whether it agrees with your sentence.

Practice this