Resources Worksheet

The cost of a copy: what an application store adds to a process.

Most application platforms keep the app's working rows in their own store and synchronise them from your systems.

The lines

Nine costs to put a figure beside

CostWith an application storeWith SmartAppsYour figure
Storage of the copyRows × columns × retention, per app storeThe rows stay in the source____
Synchronisation jobsJobs to build and to watch, per source and per appA handler registered once; change capture where offered____
Row and source capsEdition upgrades when the working set growsCapacity tier of the platform____
Drift between syncsDecisions taken on rows that changed since the last sync; time to reconcileThe screen reads the row when it opens____
Access rules kept twicePolicies re-modelled in the store and kept aligned with the sourceInherited from each source at read time____
Write pathAn integration per write, with its own error handlingReleased interface per object, acknowledgement in the log____
Audit reconstructionJoining the store's history with the source's to answer an auditorOne log with values, decision and acknowledgement____
Time to first screenDays until the store holds the rowsThe day the system is connected____
Per-user or per-app licencesSeats for every participant, including outside partiesApps, users and instances included in capacity____
How to fill it in

Pick one processThe one with the most participants and the most systems.

Bring a process; leave with an app

The first session builds the first screen on your live rows.