Single vs. Multiple Tier Recommendations for DSP Applications
|
Application |
Number of Tiers |
|
dspMigrate/ADM |
1 Tier Though the decision to use multiple tiers is based on customer requirements, avoid multi-tier setups because of the inherent overhead in code promotion management. One qualified technical FTE is necessary for this setup. A client may require a multiple tier setup because their industry is heavily regulated (e.g., the pharmaceutical industry) or to comply with corporate IT policies (e.g., banking requests require a separate production environment and data center network). |
|
ISA/dspMonitor |
1 Tier (Cleansing Reports) 2 Tier (Data Quality) |
|
dspCompose |
3 Tier (with or without dspMonitor or ISA) |
|
dspConduct: |
3 Tier minimum |
Multi-Instancing Recommendations for DSP
Applications
In Multi-Instancing, code is not promoted between DSP environments; multiple DSP instances manage “different” parts of the migration project.
Use multiple instances to address performance issues, volume issues or to separate waves to make managing them easier.
When determining whether to use multiple instances, consider the number of concurrent waves, the number of users and WebApps, data volumes and testing cycles.
HCM and HR data almost always requires an additional DSP instance. It is a best practice to isolate HR data to its own server set.