Develop your skills for autoscaling on Azure with this course from Cloud Academy. Learn how to improve your teams and development skills and understand how they relate to scalable solutions. What's more, in this course you can analyze and execute how to deal with transient faults.
This Course is made up of 19 lectures that will guide you through the process from beginning to end.
To discover more Azure Courses visit our content training library.
- Learn how to develop applications for autoscale
- Prepare for the Azure AZ-303 certification
- Design and Implement code that addresses singleton application instances
This course is recommended for:
- IT Professionals preparing for Azure certification
- IT Professionals that need to develop applications that can autoscale
There are no prior requirements necessary in order to do this training course, although an understanding of MS Azure will prove helpful
In almost all cases, you need to avoid duplicating layers of retry code. Designs that implement retry at all stages of an operation that includes a hierarchy of requests should be avoided. Of course, if there are specific requirements that call for this type of functionality, my all means use it. However, avoid it when you can! In cases where you must duplicate layers of retry code, be sure to implement policies that prevent an excessive number of retries. It's critical to remember that you should never implement an endless retry mechanism. Doing so will likely prevent your service or resource from recovering from an overload situation.
This will likely result in throttling and refuse connections that could continue for a long period of time. Per best practices, you should use a finite number of retries when possible. Another option, is to implement a pattern. A pattern such as circuit breaker would allow the service to recover. When possible, try to avoid using regular retry intervals. This is especially true in cases where you have a large number of retry attempts when accessing services or resources in the cloud. In this type of scenario, the best approach would be to implement an exponential back off strategy that includes a circuit breaking capability. By introducing randomization into retry intervals, you can prevent multiple instances of either the same client or of different clients from sending retries simultaneously.
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.