3 ms·

Thanks for the meaningful insights. The challenge we are seeing here is that we are not generating the code on the fly (both way sync like you mentioned in Del

Thanks for the meaningful insights. The challenge we are seeing here is that we are not generating the code on the fly (both way sync like you mentioned in Delphi) as we are also hosting the application on the SaaS cloud along with several other users apps and a lot of code will be clubbed/shared between the several layers. Users will be able to add the frontend/GUI code but we don't allow them to execute the backend code in our environment (only the code written by our backend team will be executed in our environment, like other NoCode platforms) Once they ask for an code export, then we will generate a code on the basic of their project, do some configurations changes so that it can run as a standalone app and then pass on that generated code to the client/user so that they can host it themselves or modify it to meet their specific/complex use case which might not be possible on our NoCode platform. Once they have exported the code, they cannot import it back. Its one way export only.

mikewarot 5y ago
Why not let them run code in the backend? Obviously you wouldn't let them have access to everything, but you could allow them to write event responders or things like that, which run in a VM, which you control very tightly, and only give X cycles to per second, etc. It could allow a whole lot more flexibility.
- vishal_sahu 5y ago
  Actually we don't provision separate VM for each app, and they run in a shared environment with other Apps, so if the access is given to execute their code and if the code is consuming good CPU/RAM, then it can bring-down/affect other apps as well. Hence not seeing the option for them to execute their code. But yes, if they want to write their code, they can always use AWS Lambda or similar services to execute their code and make an API call to pull/push the data from there and use them in the app by connecting it to that code via APIs.

mikewarot 5y ago

Why not let them run code in the backend? Obviously you wouldn't let them have access to everything, but you could allow them to write event responders or things like that, which run in a VM, which you control very tightly, and only give X cycles to per second, etc. It could allow a whole lot more flexibility.

vishal_sahu 5y ago
Actually we don't provision separate VM for each app, and they run in a shared environment with other Apps, so if the access is given to execute their code and if the code is consuming good CPU/RAM, then it can bring-down/affect other apps as well. Hence not seeing the option for them to execute their code. But yes, if they want to write their code, they can always use AWS Lambda or similar services to execute their code and make an API call to pull/push the data from there and use them in the app by connecting it to that code via APIs.