@vidierre,
I appreciate the thoughtful answer - it's fascinating. I've got a pretty varied technical background. I started my career doing programming and relational database design for a consulting firm in the early 1990's before doing a bunch of software company management (led services, product, engineering and even led a business unit of a public enterprise software company).
I went into Low Code with my eyes open on limitations. My philosophy has been: If I get this thing off the ground and my biggest problem is scale, I'll have the $ to replatform it. A year in, I still believe that.
I 100% agree with you that an architectural mindset is required. But lack of understanding of Caspio in the early stages led to some mistakes. There will be more... I started developing and learned along the way - both from a CASPIO perspective and an application perspective - that I could have designed better or used different standards. I also think the "where did I implement that function" problem (trigger, task, data page, webhook) is universal and not at all unique to Low Code.
I'm curious about your comment about users and scalability... That's a complete mystery to me. I know that Caspio is built on enterprise class sql and aws... My use case is not high intensity, but I do feel like I'm flying blind in that area. Any rules of thumb that you've found helpful?
Regarding custom code management... I'm looking at building a utility to extract the custom code from Caspio so that I can - for example - find all the places that a table or column is referenced in custom SQL.
I'd love to stay in touch with anyone who's approaching LowCode with an enterprise mindset. I think that Caspio and others are underestimating the opportunity of solving some of these enterprise-class problems.... and I don't think they are impossible.