DynamicForm Start free trial
Step 13 of 15 · Speed at scale · topic 1 of 4

Control · Speed at scale

Heavy data. Normal speed.

A system built by configuration must still answer in a blink when a manager opens a dashboard over a year of cases. DynamicForm's architecture does the heavy work ahead of time and keeps the answers ready in Redis.

Start free trialSee the architecture
Dashboards read prepared answers from RedisA manager opens a dashboard on a laptop and it opens instantly, because the tiles come from Redis, which holds ready-made results for my cases, my team, work lists and menus. The database prepares those results in the background, off-peak.My dashboardOpens instantlyRedisready-made resultsMy casesMy teamWork listsMenusfrommemoryYourdatabaseHeavy counting runsin the background,off-peakBusy database or not, the dashboard reads a prepared answer.
A dashboard opening instantly from Redis, while the database prepares results in the background.
In short

Dashboards, work lists and menus are served from Redis as prepared results, so heavy data does not slow users down. Saves return at once while the heavy writing happens in the background.

In this stop

3 more topics on Speed at scale

  1. How it stays fastEach person's and each team's dashboard figures are worked out in the background, off-peak, and kept in Redis. Opening a dashboard reads a prepared…
  2. What users noticeManagers see their team's figures without waiting, however many cases sit behind them.
  3. QuestionsShort, direct answers to the questions buyers ask most about Speed at scale.

Build your first app free

Up to 10 users. 30 days to build, then 30 days live after go-live.

Start free trialTalk to sales

Updated 30 September 2026