You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realized that several additional data is required from the client side:
Node Position for UI render
Node Size for UI render
Node Sub-type, for example, telegram is a sub-type of restApi
Trigger Sub-type, similar to Node Sub-type, more granular types
We could always add extra data field to save those info, but leveraging database seems more nimble in making changes and adding more data. Compared to AVS, posgres with prisma offers much more benefits:
Fast and easy data migration
Can add as many extra fields as we want
Data caching mechanism later, which can dramatically reduce data read of AVS
Single connection with AVS so there won’t be network issue.
The challenge lies in syncing the data of the three layers:
AVS <--> Posgres <--> Web Client
We need to combine or transform the data from the AVS in the backend, get them ready for the client, and then send over.
The text was updated successfully, but these errors were encountered:
I realized that several additional data is required from the client side:
Node Position for UI render
Node Size for UI render
Node Sub-type, for example, telegram is a sub-type of restApi
Trigger Sub-type, similar to Node Sub-type, more granular types
We could always add extra data field to save those info, but leveraging database seems more nimble in making changes and adding more data. Compared to AVS, posgres with prisma offers much more benefits:
The challenge lies in syncing the data of the three layers:
AVS <--> Posgres <--> Web Client
We need to combine or transform the data from the AVS in the backend, get them ready for the client, and then send over.
The text was updated successfully, but these errors were encountered: