Re: How do you make the choice between a single app or multi app model for a company?
If you con architect the entire app in one, I'd go that route.
If you start to push the table count of 60, then I'd consider breaking them up.
It also depends on anticipated record counts because that affect app size. QB will charge you more if your apps are too big, so if we anticipate the app getting too big (10 Million records, 40+ tables, etc.) we will break it into multiple apps.
Also things to consider are cross functional roles or groups of roles within the company (i.e. Supply chain vs Manufacturing vs fulfillment, etc.) Do they need to be together, or do they just some information from other departments.
What is your business use case? Maybe that will help clarify the needs.
If you start to push the table count of 60, then I'd consider breaking them up.
It also depends on anticipated record counts because that affect app size. QB will charge you more if your apps are too big, so if we anticipate the app getting too big (10 Million records, 40+ tables, etc.) we will break it into multiple apps.
Also things to consider are cross functional roles or groups of roles within the company (i.e. Supply chain vs Manufacturing vs fulfillment, etc.) Do they need to be together, or do they just some information from other departments.
What is your business use case? Maybe that will help clarify the needs.
