Forum Discussion
Roy-Wanyoike
1 month agoQrew Captain
From an architecture perspective, what warning signs tell you an app is becoming too relationship-heavy before actual performance issues appear? For example, are there common indicators like excessive lookup chains, too many summary dependencies, report delays, or difficulty troubleshooting formulas?
I’m also interested in best practices for designing large-scale Quickbase apps that may eventually cross the 250K–1M+ record range. At what point do you typically start introducing patterns like archive tables, stored fields, or pipelines instead of relying purely on native relationships?