SPIKE: design for async dashboard updates

[severinbeauvais]

The Problem

The business dashboard can fetch data before the Filer has finished processing a just-submitted filing, so the dashboard is out of date even though it was just loaded.

Similarly, the business dashboard can fetch some data (eg, business object) that doesn't match other data (eg, ledger) because they are separate fetch calls and their state could have changed between the two calls.

Or, a filing is done in the background (eg, Change of Addresses, or Involuntary Dissolution, or Expiry of Limited Restoration), and the dashboard doesn't update to show the latest state.

Example issues:

• a business that was just dissolved might still display as active in the dashboard (including involuntary dissolution or expiry of limited restoration)
• a business that was just restored might still display as historical in the dashboard
• a business that was just frozen might still display as usable in the dashboard
• a business that was just unfrozen might still display as unusable in the dashboard
• any filing that was just filed might display as "filed and pending" even though it's actually now completed

Refreshing the dashboard (F5) usually syncs up the latest (now-updated) data, but users don't know to do that, or if and when they should do that, and this is not a good user experience.

Proposed Solution 1 - polling for changes

Pros

Cons

Proposed Solution 2 - server event using persistent connection (websockets)

Pros

Cons

Proposed Solution 3 - gRPC

Ref: https://grpc.io/