We've been depending on Hasura v1 despite v2 reaching production readiness, since there was stability and no need to upgrade for access to new features, but with bugs appearing due to suspected upstream memory leaks, it's time to upgrade. In conjunction with this change, separating the background processing from query resolution will facilitate improved horizontal scaling and adds separation of concerns.
Proposed Solution
Introduce a new background program to handle DB management and the off-chain asset sync.
Upgrade to Hasura 2
Fixes a bug that was preventing the server starting up if the asset sync progress wasn't satisfied on initial load
Improves logging of an uncaught exception and percentage display sometime showing NaN
Important Changes Introduced
The Asset table no longer has limited VARCHAR columns, as it has been the source of sync errors in the past. The complete metadata submission is validated to be smaller than a defined size, so there's no need for fragile limits at the storage level.
Context
We've been depending on Hasura v1 despite v2 reaching production readiness, since there was stability and no need to upgrade for access to new features, but with bugs appearing due to suspected upstream memory leaks, it's time to upgrade. In conjunction with this change, separating the background processing from query resolution will facilitate improved horizontal scaling and adds separation of concerns.
Proposed Solution
NaNImportant Changes Introduced