Timeline for Provision new Azure PaaS staging environment as a copy of Production
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2022 at 20:01 | comment | added | Arkadeep | If we put the DBs into elastic pools, then I guess this issue will be over.. Keeping a single web DB can handle the situation. but again your point is correct. Should have multiple web dbs and solr slave for different CD web apps. | |
| Apr 13, 2022 at 8:30 | comment | added | Richard Hauer | The issue is that your new web app will still be connected to the prod db, xconnect and solr. When you run load tests you will max out your DB and Solr, dos’ing your production site. #1 would be ok for an emergency bug fix, but it’s not going to work for load testing. | |
| Apr 13, 2022 at 5:04 | comment | added | Arkadeep | This one I believe for UAT env, not prod. Even though, can you please highlight the exact issue on point #1? Happy to learn. :) | |
| Apr 12, 2022 at 13:08 | comment | added | Richard Hauer | Neither of these suggestions are a good plan considering OP is planning to run load testing on the new environment. Both of these approaches will DOS the production environment. | |
| S Mar 8, 2022 at 18:32 | history | suggested | Ashish | CC BY-SA 4.0 |
improved formatting
|
| Mar 8, 2022 at 18:29 | review | Suggested edits | |||
| S Mar 8, 2022 at 18:32 | |||||
| Mar 8, 2022 at 18:18 | history | answered | Arkadeep | CC BY-SA 4.0 |