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...
Forum Discussion
I agree with Mark as far as sync or pipelines goes. I like sync better than pipelines but that's mostly because pipelines has a tendency to just blow up randomly and not actually show you the issue it is having. If the error handling was more clear I would not mind using pipelines as much.
I currently help maintain something that used to be basically one giant app that did everything. We have been working on splitting parts out of it for a long time now. It is work that takes a lot of planning because you end up tied up by many things you need to fix before you can move one workflow out of your app to another.
The absolute worst part imo about the one app approach is that once your single app goes above 1GB in size the sandbox is crippled. You can no longer import ANY records automatically when creating your sandbox, not all and not 50, none. You either create a full app copy and get to deal with 2 large apps while you work or you create your own program to make sure your app copy has a small amount of records by purging them table by table when creating it. This is a big reason we are trying to split out our gigantic app into smaller ones.
Working in the sandbox with zero records sucks. You can import them manually but it is annoying to do when you have a ton of tables. Then your records are not related either unless you really go above and beyond when doing your imports.
I have asked Quickbase staff in the past if there were any plans for increasing the 1GB limit and they said not at all. This was not just customer service that told me this but a higher up that I forget the name of unfortunately.
I currently help maintain something that used to be basically one giant app that did everything. We have been working on splitting parts out of it for a long time now. It is work that takes a lot of planning because you end up tied up by many things you need to fix before you can move one workflow out of your app to another.
The absolute worst part imo about the one app approach is that once your single app goes above 1GB in size the sandbox is crippled. You can no longer import ANY records automatically when creating your sandbox, not all and not 50, none. You either create a full app copy and get to deal with 2 large apps while you work or you create your own program to make sure your app copy has a small amount of records by purging them table by table when creating it. This is a big reason we are trying to split out our gigantic app into smaller ones.
Working in the sandbox with zero records sucks. You can import them manually but it is annoying to do when you have a ton of tables. Then your records are not related either unless you really go above and beyond when doing your imports.
I have asked Quickbase staff in the past if there were any plans for increasing the 1GB limit and they said not at all. This was not just customer service that told me this but a higher up that I forget the name of unfortunately.
- Austin,
Good thought on the app size. Luckily, my biggest app is 160mb so I don't see that as a problem in my case. Though, i rarely if ever work in the sandbox because I have cross app relationships, and typically what I need to work on relies on working on 2 apps.
I'm with you on Sync over Pipeline. I find it much easier. Sync is a heavier load from a resource standpoint though, so you need to be careful if they run every hour. If they run once in the middle of the night, not really an issue.
------------------------------
Mike Tamoush
------------------------------
