28. • Easy to start.
• Easy to build.
• Easy to deploy.
• Easy to scale.
29.
30.
31. Web Server
1. Request for a foo.com arrives
to ARR/Load Balancer
IIS ARR
(LB) 2. ARR gets info from Runtime DB
about foo.com and determines
which Web server(s)) should host
the site.
(Antares is actively monitoring all
Web Servers in the farm)
Azure Runtime DB Web Site
LB DB 3. ARR forwards request to the
designated Web Server
4. Web Server provisions site
* de-provision inactive sites
Storage 5. Web Server executes request
accessing site’s content and site’s
Controller DB
32. 1. Request for a foo.com arrives
Web Server
IIS ARR
to ARR/Load Balancer, which
already “familiar” with foo.com
(LB)
2. ARR “remembers” foo.com and
route the request to the right web
Server(s).
3. Web Server executes request
accessing site’s content and site’s
Azure DB
LB Web Site
DB * Subsequent requests to this site
get routed to a Web Server that
has the site provisioned.
Storage
Controller
33. IIS ARR Web Server All DBs are running on
SQL Azure
(LB)
Azure Blobs as durable
storage
Runtime Windows Azure Worker
DB Roles
Web Sites
Azure DBs
LB
API Frontend
Storage Cloud
Deployment Controller Drive
Server(s)
34. IIS ARR Web Server All DBs are running on
SQL Azure
(LB)
Azure Blobs as durable
storage
Site (W3WP.exe)
Runtime Windows Azure Worker
DB Roles
Web Sites
Azure Metering DBs
LB Monitor resources usage
DWAS
API Frontend Dynamic Web Activation
Service
Storage Cloud W3WP.exe IIS Application
Deployment Controller Pool Process
Drive
Server(s)
