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

The node palette & component families

Which family a node belongs to, which kind of Grid offers it, and what each plan can place.

"Which of these do I use for a database?" RodGrid has four families of node and one candidate in each, and they do not say the same thing about your system.

Three of the four, one per family. The next section says which Grid offers each.

  • Architecture: Relational Database. A component of a system. This family holds concrete technologies and generic building blocks, and it is the family Traffic Simulation models. Drawing a system? Use these.
  • Design Patterns: Data Store. An abstract role: something persists here, with no technology attached. Use these to model a pattern.
  • Flow / LLD: Stored Data. A flowchart symbol, for modeling logic and algorithms. Low-level design has its own group next to it, LLD / UML, where a table is an Entity.
  • Shapes: Cylinder. A drawing. Type "database" on it and it still says less than the real node, and Traffic Simulation leaves it out of the numbers. Shapes are for annotating and grouping, which Organizing large diagrams: frames, groups & annotations covers.

Placing the node you chose is in Build your first diagram.

The Grid decides what is on offer

  • Diagram Grid: Architecture and Shapes.
  • Pattern Grid (Start from scratch with Pattern pressed): Design Patterns and Shapes.
  • Challenge Grid: only the components that exercise allows, from the family its kind calls for, and no Shapes. Flow Challenges use Flow / LLD; low-level-design Challenges use LLD / UML.

So on a Diagram Grid the question has a short answer: open Data Stores. Diagram and Pattern Grids also list a Custom group, for what the catalog lacks; Making the catalog yours: custom components covers it.

What each plan places

On the Free plan you get Shapes, the generic design-pattern roles (Actor, Service, Event, Queue…), and a starter set of generic, vendor-neutral Architecture nodes: enough to diagram a real system. The named-technology library and the GoF/DDD/integration pattern sections come with a paid plan, and the Comment balloon in Shapes needs Premium. No plan adds Flow / LLD to a Diagram Grid or a Pattern Grid; on a Challenge the exercise picks the components, and every plan can place them.

A node you cannot place stays in the list with a lock and the plan it needs. On a Grid someone else owns, the owner's plan decides what is locked.

Search instead of scrolling

Groups start collapsed, apart from Shapes, so for a component you can name, type a few letters into the search box. It filters every group the palette is showing and opens the ones that match, and it reads more than names: cache also finds Redis. Component names follow the language you picked, and the English name works too. It cannot reach a family this Grid does not offer: observer finds that role on a Pattern Grid, not on a Diagram Grid.

A node the catalog has retired stays in the list greyed out and marked with what replaced it, rather than disappearing from under a Grid that uses it.

A choice to make on Weather Service

The Weather Service Challenge settles the family for you: Architecture, fourteen components, nothing locked. The database question comes back one level down. The brief wants responses cached and forecasts refreshed on a schedule, so which node holds them: Redis, PostgreSQL, Neo4j, or more than one? Decide before you open the palette, then search for it. Stripe is in there too, and the brief gives you no reason to place it.

Practice this