Use cases for observers include:
Updating the UI from database changes (data binding).
Syncing local state from background worker (like a ServiceWorker) or another tab making changes.
I like this idea to add observer support to current IndexedDB design for web developer to provide better experience and consistent data to the user when multiple tabs are open.
The only concern/limitation so far to me is addressed in https://github.com/dmurph/indexed-db-observers/issues/24#issuecomment-222052352
The transaction ordering has been confirmed to be restricted even if it’s an empty transaction.
I’d still like to see if we can improve it instead of restricting it.
Thanks for your efforts to improve the use cases of the IndexedDB!