Last week I got a chance to attend Microsoft Tech Ed 2014 @ Ashok Lalith. Bangalore
Thought of putting up the Best Practices which Microsoft suggests when moving existing Apps to Azure
Best Practice on Azure
Migration.
•Lift and shift- will not work and testing is required
•I am here today and will on cloud tomorrow, will not be happened
•Go for a Workload based approach
Steps for moving.
Don’t move your existing app suddenly, as a first step choose a least critical app and follow the below order
1. ISAAS – start as VM
2. Make it PAAS enabled -
3. Make it Service enabled
Best Practice
•Keep separate subscription for different type of VM..E.g. one for DEV test and other Live.
•The maximum IOPS we can get is 500 hence Create separate disks. For example in SQL create log files, data files etc. in separate disks.
•Don’t store anything on temp disk.
•Use azcopy for copying data to between.
•Enable Geo Replication…
http://azure.microsoft.com/blog/2014/09/03/azure-sql-database-standard-geo-replication/
•Locate a nearest storage location for you app... If your app is in India choose a storage location from India (Microsoft will be opening a datacentre for Azure in India soon).
•Never keep one VM in an availability set .
•Configure VM to start all service on reboot .
•Cloud Service in a subscription is limited to 200 .
•Use Wcat - to create test load on websites.
Thought of putting up the Best Practices which Microsoft suggests when moving existing Apps to Azure
Best Practice on Azure
Migration.
•Lift and shift- will not work and testing is required
•I am here today and will on cloud tomorrow, will not be happened
•Go for a Workload based approach
Steps for moving.
Don’t move your existing app suddenly, as a first step choose a least critical app and follow the below order
1. ISAAS – start as VM
2. Make it PAAS enabled -
3. Make it Service enabled
Best Practice
•Keep separate subscription for different type of VM..E.g. one for DEV test and other Live.
•The maximum IOPS we can get is 500 hence Create separate disks. For example in SQL create log files, data files etc. in separate disks.
•Don’t store anything on temp disk.
•Use azcopy for copying data to between.
•Enable Geo Replication…
http://azure.microsoft.com/blog/2014/09/03/azure-sql-database-standard-geo-replication/
•Locate a nearest storage location for you app... If your app is in India choose a storage location from India (Microsoft will be opening a datacentre for Azure in India soon).
•Never keep one VM in an availability set .
•Configure VM to start all service on reboot .
•Cloud Service in a subscription is limited to 200 .
•Use Wcat - to create test load on websites.
No comments:
Post a Comment