There are quite a few things to consider in a design like this, many of which are out of scope of this library's feature set.

Binding to the nodes/edges in the Svelvet graph seems to be in progress:#428. There are workarounds to bind to this data currently, but it's still a bit clunky.

As for the whole backend part of your application, you'd probably open up aWebSocket to deal with live syncing of your frontend network and your backend. As for the runtime, there's not a 'direct' conversion to your server-side code: you'll probably need to implement this yourself, depending on what your application needs to do. You then need to implement storing user flows, authentication, databases, etc...

It's a reasonably complex task, but have you considered other options that already do this?
Node-Red may already be close to the thing you want to build. The backend 'logic' runs on the server, but you edit the nodes in your browser.
NoFlo did a similar thing, however it's not been maintained/updated in a few years.

Implementing this kind of thing from scratch could be a fun project, but it might be worth seeing if one of these existing tools can cover your needs.

Best of luck!

There are quite a few things to consider in a design like this, many of which are out of scope of this library's feature set.

Binding to the nodes/edges in the Svelvet graph seems to be in progress:#428. There are workarounds to bind to this data currently, but it's still a bit clunky.

As for the whole backend part of your application, you'd probably open up aWebSocket to deal with live syncing of your frontend network and your backend. As for the runtime, there's not a 'direct' conversion to your server-side code: you'll probably need to implement this yourself, depending on what your application needs to do. You then need to implement storing user flows, authentication, databases, etc...

It's a reasonably complex task, but have you considered other options that already do this?Node-Red may already be close to the thing you want to build. The backend 'logic' runs on the server, but you edit the nodes in your browser.NoFlo did a similar thing, however it's not been maintained/updated in a few years.

Implementing this kind of thing from scratch could be a fun project, but it might be worth seeing if one of these existing tools can cover your needs.

Best of luck!

1. Thank you so much for the answer. You already gave me some nice ideeas. In short, I wont use node-red unless Svelvet implementation compleatly fails . I prefer making a very small working poc for a future project to see how things are going.

2. You are right. For each node, I could have a server function. If its necesary users can play on a node and a server function will trigger in live editing mode.(action triggered by ws)
   When the user saves the flow, I think I will need to make an interpretor that runs those functions step by step (I will have to figure out a way to interpass the variables between functions)

The hard thing that I will face is that I am still new to this library, so the flow map will be actually a difficult challenge. I will need to detect connections and variables(that user sets inside blocks) abd construct the flow in a JSON format.

I will start the project in november, until then I need to do some pre-planning with my tech stack. I feel confident that Svelvet would be my best candidate. If not, then I will do it with node-red.