4 ms·
> If you would evaluate a low-code backend builder, how would you do it? Firstly I would check if it’s open source. There’s a reason companies & individuals us
by gitgud 3y ago
> If you would evaluate a low-code backend builder, how would you do it?
Firstly I would check if it’s open source. There’s a reason companies & individuals use open source programming languages… because it’s way less risky. The same is true for a low-code language/system.
Can I version it in git? Can it be reliably tested? Can I self-host it?
As far as functionality of the low-code: is it expressive? Can I make loops, variables, conditions? Can I bundle things into reusable Lego blocks? Can I use libraries or make fetch requests? Can I add environment variables? Can I add authentication, users, permissions?
There’s a lot to evaluate with a new system, low-code or not
- jarirajari 3y agoChecklist - open source. This I would do my self too, but only because I am a technical person - version control. Agree, but in my case only API will be available for you to version (versions are of course in backend too) - testing. Agree and this is important. But what kind of testing? Would end-to-end tests be enough i.e. separated env with data set and Postman? - self-hosting. Private SaaS anyone? - functionality: thanks for reminding me of the importance of loops, variables, and conditions. These can be implemented. - authentication and authorization. Definitely required for mature software!