This blog post is located over here; Managing Scalable Azure Infrastructure
Here are my notes while the above portfolio is being restored; I...accidentally deleted it while mass cleaning out my Drive and didn't realize for a week. Oops. If anyone has a contact at Google who would like to help, I'm on LinkedIn.
They're messy, but the gold shines through.
In Summary (Load Balancing and maintenance);
I created two azure load balancers for web app redundancy and speed; this eliminates single points of failure. Health probes let me know if something needs attention.
Distributes web traffic across multiple virtual machines, making it resilient + scalable, maintain performance, and eliminate single points of failure.
A health probe makes sure everything is up and operational, and LB rules distribute HTTP traffic.
Hands-on experience configuring 2 azure load balancers, a tool that, at it’s base basicness, has multiple components that ensure uptime, optimize web traffic, and improve application reliability.
Optimized web traffic and ensured application uptime and reliability by configuring 2 azure load balancers and health probes across multiple service regions that maintain performance by eliminating single points of failure.
Testing Load Balancers
In Summary -After I set up the LBs, I tested load balancers in two regions to ensure uptime and redundancy [by stopping and starting virtual machines [simulated a failure] to watch the data carry over to the other machine]
Ensure IPs are static.
Configuring static IP addresses for the load balancers. Other devices like laptops or phones do not have static IPs because of [lot of jargon/reasons you could pay me to go into], but we want our load balancer VMs to be firm and in place.
Also, less admin overhead for us.
We want scalable and fault tolerate infrastructure! Dynamic IPs means our LB VMs aren’t secure.
First, what is Internet Information Services?
It’s a Microsoft Web Server tool to serve HTML (web) pages. If you’ve never heard of it, nor me until I did this.
I install it onto a VM using the Powershell command so we don’t expose the virtual machine to the greater internet unnecessarily. It's more secure this way!
What happens to make sure if one aspect goes down? We need redundancy (The irony of me typing this, this entire post, because I accidentally deleted my Google Site where the original information is.)
We use Blob Replication;
Between storage accounts (and I guess those storage accounts can cross regions if they’re attached to it.
Updates in primary storage are copied to secondary account
Supports disaster recovery, fault tolerance, and content synch
If you replicate it, if something goes down, then it’s somewhere else
Also ties in with a Content Delivery Network (CDN) - it delivers the assets to the visitor.
I then mapped CNAME and URL records to the proper URL (Again, the irony is not lost on me, as I did that 10 minutes before writing this post as I accidentally deleted my Google Site where the original information is from both Sites and Trash!)
Comments
Post a Comment