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.

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.

Work pages, shared sign-in

Find waiting work without loading the whole inbox. Each application's inbox retrieves pages in the database, keeping the view responsive as case volumes grow. End users review the open application's work a page at a time.

Sign-in state is shared across servers, so any server can answer a sign-in request. A sign-in code is accepted once, even when requests reach different servers. People use the same sign-in flow while the service handles requests across its servers.

Application boundaries still apply to the work shown. My tasks and the case monitor follow the open application. Explore Applications for the dashboard, application switcher and role-based access.

Sign-in requests reach generic application servers connected to shared state, with a code accepted only once.
Servers share sign-in state so any server can answer and a code is accepted once.

Review rule cost

See a rule's cost class while designing it. DynamicForm labels each rule Light, Moderate or Heavy, making processing cost part of the design review.

Heavy rules need explicit, recorded acceptance. Review the business purpose alongside the class before accepting that rule.

Rule timings are monitored, supporting review after the rule is designed. Use the class and monitoring together when considering rule choices. Explore Rules and calculations for the supported operations and the places where rules apply.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Updated 16 November 2026