JenniferMiller
4 years agoQrew Member
Best practices - combining two apps to one
Looking for advice on best practices.
I currently have two related apps that, as they've evolved, I am thinking would make much more sense to be in one app... for better user experience, easier/cleaner reporting, and easier/cleaner API calls from/to external systems. My concern with doing this is the number of fields already on each table. By combining the tables in these apps, I would end up with over 750 fields on one table... should I be concerned with performance issues if I do this? We use these applications to drive our daily production operations so performance issues would be a huge concern.
------------------------------
Jennifer Miller
------------------------------
I currently have two related apps that, as they've evolved, I am thinking would make much more sense to be in one app... for better user experience, easier/cleaner reporting, and easier/cleaner API calls from/to external systems. My concern with doing this is the number of fields already on each table. By combining the tables in these apps, I would end up with over 750 fields on one table... should I be concerned with performance issues if I do this? We use these applications to drive our daily production operations so performance issues would be a huge concern.
------------------------------
Jennifer Miller
------------------------------