Is trame suitable for building a website project with separated front-end and back-end? #515
-
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Trame is mainly focused at bringing desktop like application to the web. In other words, creating desktop app with a web front-end that can run locally, in the cloud, jupyter or on HPC. If your goal is to create a web-app that scale because most/all of the processing is done on the client side, trame is not for you. Trame can still be used with a front/back end separation, but that won't remove the fact that trame expect the processing to happen on the server side. For the django integration, a trame process could run as an asynchronous task. So if django can support In term of technology stack, if you want more than vtk.js on the client side to do things, you should look into VTK/wasm. |
Beta Was this translation helpful? Give feedback.
Trame is mainly focused at bringing desktop like application to the web. In other words, creating desktop app with a web front-end that can run locally, in the cloud, jupyter or on HPC.
If your goal is to create a web-app that scale because most/all of the processing is done on the client side, trame is not for you.
Trame can still be used with a front/back end separation, but that won't remove the fact that trame expect the processing to happen on the server side.
For the django integration, a trame process could run as an asynchronous task. So if django can support
async
in python, then technically they can both coexist, but I would not suggest that in anyway. Think of it that way, woul…