Most application platforms keep the app's working rows in their own store and synchronise them from your systems.
| Cost | With an application store | With SmartApps | Your figure |
|---|---|---|---|
| Storage of the copy | Rows × columns × retention, per app store | The rows stay in the source | ____ |
| Synchronisation jobs | Jobs to build and to watch, per source and per app | A handler registered once; change capture where offered | ____ |
| Row and source caps | Edition upgrades when the working set grows | Capacity tier of the platform | ____ |
| Drift between syncs | Decisions taken on rows that changed since the last sync; time to reconcile | The screen reads the row when it opens | ____ |
| Access rules kept twice | Policies re-modelled in the store and kept aligned with the source | Inherited from each source at read time | ____ |
| Write path | An integration per write, with its own error handling | Released interface per object, acknowledgement in the log | ____ |
| Audit reconstruction | Joining the store's history with the source's to answer an auditor | One log with values, decision and acknowledgement | ____ |
| Time to first screen | Days until the store holds the rows | The day the system is connected | ____ |
| Per-user or per-app licences | Seats for every participant, including outside parties | Apps, users and instances included in capacity | ____ |
The first session builds the first screen on your live rows.