Skip to content

Star model

A central entity with satellites around it.

A relationship map: one thing in the middle, the things that describe it around it, in star-schema vocabulary. The bare text after the shortcode is the TITLE; fact: names the centre, with its fields on indented lines; each dim is a satellite. Dimensions spread evenly clockwise from 12 in written order — place one yourself with at 4 or at top-right. Terse form dim: A, B, C when placement does not matter. The ring grows until nothing collides, so the size comes from the content rather than a fixed radius.

A block written inside it is drawn below it. What goes inside what

@star_model Telemetry warehouse
  fact: TaskExecutionEvents
  dim Agents at 12
  dim Models at 3
  dim LatencyBuckets at 6
  dim CostCenters at 9

Telemetry warehouse

TaskExecutionEvents

Agents
Models
LatencyBuckets
CostCenters
Settings
SettingTypeRequiredDefaultMeaning
layoutclock · listnoclockclock arranges the dimensions around the fact. list writes it out instead — a star model with fifteen dimensions is a list of fifteen dimensions, and a wheel of tiny text helps nobody.
More examples
@star_model(layout=list) Order analytics
  fact: Orders
  dim: Customer, Product, Date, Store, Channel, Device, Campaign

Order analytics

Orders

  • Customer
  • Product
  • Date
  • Store
  • Channel
  • Device
  • Campaign
@star_model Order analytics
  fact: Orders
  dim: Customer, Product, Date, Store

Order analytics

Orders

Customer
Product
Date
Store
@star_model Event model
  fact: TaskExecutionEvents
    event_uuid: uuid, pk
    agent_id: fk -> Agents
    latency_ms: int
  dim Agents at 12
  dim Models at 4

Event model

TaskExecutionEvents

event_uuid: uuid, pk

agent_id: fk -> Agents

latency_ms: int

Agents
Models