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
Any application that communicates with remote services and remote resources needs to be sensitive to transient faults. Applications that run in the cloud are especially vulnerable to transient faults. This is due to the nature of the environment including the inevitable random connectivity issue over the internet. As such, these types of transient faults will often be encountered. A transient fault is the momentary loss of network connectivity and the temporary unavailability of a service or application or even a time out of an application that arises as a result. That being said, such transient faults are generally self correcting.
Transient faults can obviously impact the perceived availability of an application. Ensuring a cloud hosted application can operate reliably means it must be able to respond to transient faults in an elegant manner. The application needs to be able to detect a fault when it occurs. It then needs to determine if the fault is likely transient or if it's a more long lasting fault. In addition to being able to detect faults, and what type of faults they are, the application must also be capable of retrying the operation that it was attempting during the fault if it determines that the fault is in fact transient. It also must be able to keep track of the number of times the operation has been retried. Applications that elegantly handle transient faults must use appropriate strategies when attempting retries. A retry strategy will specify the number of times the application should retry, the delay between each attempted retry, and what actions to take after a failed retry attempt.
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.