What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: 02 Why Microsoft Azure
Select a size
02 Why Microsoft Azure
Microsoft Azure Fundamentals Why Microsoft Azure?
Bob Tabor | http://www.LearnVisualStudio.NET
Why do we need Microsoft Azure at all?
Tempting to jump in and start writing code and deploying services
First, let’s get oriented to the forest – or even ask why we’re standing in front of this forest?
Basics of client / server architecture
More clients => more load => more resources to handle it
Qualities of a well architected application:
To manifest these qualities, you need a strategy for expanding compute resources quickly as need arises
To manifest these qualities, you need a strategy for expanding compute resources quickly as need arises:
You typically choose to scale up when any single request demands more memory and processing power to complete, and the bottleneck / latency in the system is the intensive number of software objects created in the computer’s memory or the intensive algorithms and business logic that is performed. In this case, the key to completing each incoming request more efficiently is to provide each incoming request with more processing power.
Conversely, you typically scale out when any single request requires less memory and processing power to complete, but the real bottleneck / latency is in network communication, disk access, etc. In this case, the key to completing each request more efficiently is to run it in parallel to other requests as each wait on external components to complete -- again, waiting on disk access, network access, etc.
It’s common to do both
Scale out is made possible through a load balancer
Importance of redundancy, takes different forms at various parts in the system.
Benefits of virtualization
Opportunities for Azure
Near instant provisioning to meet load
Scale back down when load subsides
Load balancing is baked in
Leveraging existing investments in virtualization
Hybrid approach doesn’t require long term commitment or investment
Devote manpower to building competency in low-level pursuits where you have complete control OR on higher level business problems?
Take on expense of building out a data center for a temporary spike in load OR spend time and money elsewhere?
Do I provision enough servers to handle future demand (we cannot predict)?
Do I provision enough servers to handle today’s demand (risking the fact that we may experience load we cannot handle)?
Scaling, redundancy, failover, etc.
New architectural options
Something for everyone – small and large organizations
In client / server architected systems there’s usually a variable demand
In the past, handling spikes in demand required preparing ahead of time – building out a large server farm (just in case)
Microsoft Azure allows for immediate provisioning and de-provisioning – pay only for what you use
Microsoft has invested in redundancy, failover, caching, storage, machine learning, authorization, etc. and you can leverage it inexpensively