Forum Discussion

MikeTamoush's avatar
MikeTamoush
Qrew Commander
4 years ago

Number of Apps, Best Practice

I've always read, and indeed from my own experience, to keep the number of apps I have to a minimum, if possible. This is for a few reasons: 1. Avoid Cross App Relationships 2. Much easier to mana...
Ask about Quickbase functionality
MarkShnier__You's avatar
MarkShnier__You
Icon for Qrew Legend rankQrew Legend
4 years ago
If you have one large app and you split it into two, but you have cross up relationships then you'll have gained nothing. Cross up relationships are not the problem.  Really the problem is when you have an app or a cluster of apps which are cross linked to each other then you are restricting that app to run on one server process.  If you have a busy app with lots of concurrent users than performance will be degraded and your users will complain.    

The best practice would be to have more apps and not have them cross linked. The only way to do that if you have common tables is to use Sync tables or some kind of pipeline to mirror the information across.   That way each app gets their own server process.

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
  • MikeTamoush's avatar
    MikeTamoush
    Qrew Commander
    4 years ago
    Sorry, I should have been more clear. Yes, when I have a cluster of apps (that will have cross app relationships) the only reason I split them, is if there is a clearly defined reason to from an organizational standpoint. I typically like to have as few apps as possible, just from a management of apps standpoint.

    If I can ever split apps with no report links, T2T imports, or cross app relationships I do so.

    I was just wondering if anyone has found any other advantage to splitting an app, instead of just one giant app (assuming splitting will still have cross app relationships).


    ------------------------------
    Mike Tamoush
    ------------------------------