QuickBase Architecture Considerations
So, I'm new to QuickBase, and I'm trying to understand the true intent of this 'codeless' application. I have a complex set of data interactions that I must control, and I'm wondering if I should...
Forum Discussion
We run our whole company (a website development and Internet marketing firm) on one single app with 71 tables and growing. Everything is connected to everything. Honestly, I don't know why anyone would want to create multiple "apps" when everything needs to be integrated. That's how you cut through departmental silos. QuickBase is totally fine in helping you encapsulate, encode and manage the complexities of your business logic. Honestly, the only thing I've run into that is hard is the arbitrary but hard limit of a single table being limited to 500 mb. But that would apply regardless of whether you architected your app as one or many. I think you will have it be ultimately more complex if you have multiple apps.