![]() ![]() With the introduce of deployment slots azure makes deployment process much more secure and developer friendly. They could take the advantage of your broken code and can mess with your business. Deploying a bad version of your website often create/opens new hole for hacker.After the deployment completes the website might restart and this results in a cold start for the website, the first request will be slower (can be significant depending on the website) and this can ultimately drop some traffic of your website.So, the gist of entire process is that no matter which deploying strategy (WebDeploy, FTP, git, CI or any other way) you might be using today have the following two major weaknesses From our experience we have seen that moving stuff between environments required a series of backups, deployment scripts, scheduled downtime etc. Once the product pass all the testing phases the developed solution then moved to production server. On the other hand the production site run on standalone server(s). Usually beta/uat/etc testing was carried out in separate environments. So, testing in QA and UAT, A/B testing all becomes the integral parts of the process. And as we work on for them it turns out that testing plays a vital role in the entire process to ensure the development of a perfect solution that matches client requirement. ![]() We, software developer mainly develop products/features to fulfill the dream of client requirement. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |