Customer Process Manager framework (Legacy)

Generally been a good experience, however, have found a few challenges. 1) Locating qualified resources with Pega experience has been more difficult than expected. 2) Our business was expecting to have the ability to make minor updates / modifications to rules. We have found that is not realistic for two reasons. a) Our business users are not technically astute and b) their primary focus is on the operation of the business. 3) Our implementation is rather unique as we have an instance at our HQ and 26 other instances (1 for each of our ships) and we syncronize data between them. We would prefer to have a single instance, however due to limited satellite coverage globally, we require this architecture. Due to this process when we synchronize data, we found the existing version was designed such that as the database grows so does the application server requirements / footprint in terms of memory / CPU. We understand that this is primarily due to the architecture/design where some portion of the database is loaded in memory and upon inserts/updates, Pega determines whether the row needs to be updated or inserted in the database when importing data. We have been advised this does not exist in the most current version.