Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client side needs extra data in Trigger and Node #61

Closed
chrisli30 opened this issue Jan 27, 2025 · 0 comments
Closed

Client side needs extra data in Trigger and Node #61

chrisli30 opened this issue Jan 27, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@chrisli30
Copy link
Member

chrisli30 commented Jan 27, 2025

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.

@chrisli30 chrisli30 added the documentation Improvements or additions to documentation label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant