Apps, Performance, and Best Practice

Hi Mark,

I'm really interested in (and potentially concerned by!) your comment:

"If you do go the route of separate apps, then you cannot make any cross app relationships or cross app saved table to table imports as that just makes it one giant app under the covers.  So you need to use Sync tables to replicate master files like customers or warehouses."

Could you clarify please.

My specific situation is I have a master database (used for content management, and not the fastest due to prolific use of summary fields) and a slave which I update overnight using API_RunImport.

The slave is used to serve read only data to our customers within our web app via API calls).

Are you saying that these two apps are run a single thread because of the use of the import API to refresh the slave tables, and therefore I won't actually be seeing any performance gain from separating the two?

And if this is the case, are you are saying the only way to break this and ensure separate threads for the two apps is for the refresh of the slave tables to be using Connected tables / Quicbase Sync?

Thanks

David