First and foremost, Corteza is a great low-code platform with numerous out-of-the-box capabilities that is also open source; congrats to the planet crust team and fellow community members
I’m thinking about using Corteza for a live project and have a few queries. Kindly note that I have successfully installed Corteza locally and have read through the documentation quickly.
- Do we have any performance metrics for Corteza? As far as I can tell, the equivalent database structure is as follows:
- Table gets translated to compose_module
- Table columns to compose_module_field
- Each table row mapped to compose_record
- Actual row values to compose_record_value
I’ve usually worked with configuration in which a certain object, like Products, has its own table with appropriate columns (fields) and records (rows). With the corteza structure described above, I think all records for all tables/modules are stored in the compose record value table, which may expand enormously in a high volume system. For example, if we have 2M records for each module/table, we may have 200M records with 100 modules. I’m curious whether this can have an effect on database and app performance. Maybe someone who is operating such a system may provide some thoughts.
Is there a way to manually insert records (through sql query) and map them according to Corteza’s configuration, i.e. module, field, records?
Is it feasible to archive/move data, for example, if we manage a production instance with recent data and an archive instance with older data (perhaps solely for retrieval/selection through web-app)?
I’m searching for instructions on how to compile the source code so that I may run the different components (Server, corredor, web-app) independently and perhaps in different systems (Windows/Linux). Any advice would be much appreciated.