Instructions for Windows Azure Developer

Today came across a very interesting article on the Internet, tells the story of the most important things to remember are to each Windows Azure developer. As for me, each item is really important, and all together will help you not only save time and nerves, but also the money list was filtered a bit for some moments, I was totally disagree. So here it is this short list.

a. How can I treat customer inquiries at least as far as possible, and submit them to third-party resources (such as blobs in the repository for static content ).

2. use. Shared Access Signature. for direct access to private content. Access can be worn as a temporary or canceled at the request of.

3. Get access to the blob by. CDN. In this case, the content will be delivered to end kastomeram quickly, and the number of network devices will be involved on the contrary a minimum.

4. If you are using. CDN. Do not forget about the time of aging elements in a content delivery network. The default is 72 hours.

5. If you are using. CDN. Also do not forget to use the versioning URLs. This will significantly reduce the number of problems with the caching of data in. CDN.

6. For the most ... Windows Azure AppFabric Caching. With distributed caching can reduce the waiting time, and in some cases, the cost of.

7. Think about that use a large number of small instances, but not in excess of a couple of productive machines. Eventually you should get a bigger performance boost.

8. use. SQL Azure Federations. to partition the data set on the shards, and improve system performance.

9. Do not forget to do your application performance tuning using the standard means of measurement and optimization.

10. For Web applications, do not forget to include additional types of content compression (preferably, by the way, not only for cloud applications).

11. If you are using. AppFabric Caching. , It is desirable to cache the size of small objects. This will improve the performance of the solution.

12. Use VM- role only in cases where the process of installing a component tightened over time or require manual intervention.

13. In most cases you only need to be. Startup. Tasca to install the necessary components, so the VM- role only for very specific cases.

14. Use an asynchronous pattern of programming and. Windows Azure Queues. instead of the synchronous approach your roles.

15. Do not connect the device directly to the. SQL Azure. database. Proxies access via the service layer (. SOA. pattern - the perfect candidate).

16. Do not forget to use the / y option to prevent annoying confirmations ( very important for. Startup. Taxco ).

17. To monitor a particular process, use. ProgramEntryPoint. or. NetFxEntryPoint. instead of. Startup. Tasca.

18. Set. NetworkTrafficRules. for greater protection of your roles.

19. If you are using. Windows. Azure Traffic Manager. - Create a page to monitor the status of your application.

20. If you are using. Windows Azure Table Storage. - Use the parameter. SaveChangesOptions. Batch. to save the transaction and increase productivity.

21. Virtualke size selection is crucial. A sober assessment of your subject area, the level of the anticipated loads and select the appropriate size of the virtual machine.

22. Do not use the default account for the. AppFabric Service Bus. Create your own account and give it the necessary set permishenov. How to do it is written here in this. publications.

23. Do not save login for. SQL Azure. established on the portal developer, in the connection string. Create your own username you need to work a minimum of law and you do not need to use the SA for this.

24. When using the queue (. Windows Azure Queues. ) Use the method. GetMessages (count). instead of. GetMessage. - This will greatly reduce the number of transactions and improve the performance of your solutions.

25. If you are using. Worker. roles, which are periodically poll the queue, use the technique of ... This will reduce the number of requests and improve the performance of the solution.

26. Of course if you use the 25th paragraph - think over how to return to your life. Worker. roles. AppFabric Service Bus. can be an ideal candidate for this, but it is worth paying attention to the cost of such a flexible solution.

27. Scale your application in all directions, both horizontally and vertically:).

Source:. Windows Azure Best Practices.