Anda di halaman 1dari 1

http://aka.

ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
PLAN AND DESIGN BUILD AND DEPLOY RUN AND TUNE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons A highly scalable application requires the use of specific patterns and practices. Cloud Services are built for scalability. Web and worker instances can be increased and This phase contains the processes that refine the application, keep it running, and
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons Designing for optimal performance and scale-out is key. Use the patterns below decreased at will. Workloads can be distributed using messaging, such as queues or enable scaling out (and in) as needed. Tuning your application takes time and requires
A key benefit of Windows
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
to help you architect your solution and continually refine your application. Service Bus Topics. instrumentation and monitoring.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
Azure is creating highly
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
Tables and blobs provide massive storage capacity and SQL Database supplies rela-
tional
Its a good practice to continually assess the metrics and balance against running costs.

scalable applications using


http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons capabilities. Other services such as caching can be easily integrated into a service.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons

Cloud Services.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignScaleOut http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
Applications can shrink and
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
SCALE OUT WITH SCALE UNITS
http://aka.ms/AzPstrScalabilityV1DesignScaleOut
http://aka.ms/AzPstrScalabilityV1DesignScaleOut
SAVING STATE
http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
stretch to accommodate
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignScaleOut http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunVisibility
http://aka.ms/AzPstrScalabilityV1DesignScaleOut
changes in usage, removing
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
VS.
http://aka.ms/AzPstrScalabilityV1DesignScaleOut http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunVisibility
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignScaleOut
the need for expensive
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignScaleOut
http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
CLIENTS http://aka.ms/AzPstrScalabilityV1RunVisibility
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignScaleOut http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1RunVisibility
VISIBILITY & MONITORING
on-premises hardware.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
Use more instances, not bigger hardware. Scale in
http://aka.ms/AzPstrScalabilityV1DesignScaleOut
and out using scale units that are easily duplicated
http://aka.ms/AzPstrScalabilityV1DesignScaleOut
The durability of a web and worker role instance is
http://aka.ms/AzPstrScalabilityV1DesignSaveState
not assured, therefore its state (customer data, stage http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunVisibility
Strategically instrument the app to monitor potential
http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
and deployed. Scale units consist of a number of role
http://aka.ms/AzPstrScalabilityV1DesignScaleOut in a workflow, etc.) must be saved externally.
http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunVisibility
bottlenecks. There are two kinds of monitoring:
A key strategy is to design
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
instances and their support services.
http://aka.ms/AzPstrScalabilityV1DesignScaleOut http://aka.ms/AzPstrScalabilityV1DesignSaveState
Save state to durable storage (Table, SQL Database, http://aka.ms/AzPstrScalabilityV1RunVisibility
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignScaleOut
For example, a scale unit could be 3 web roles, 2
http://aka.ms/AzPstrScalabilityV1DesignSaveState
Blobs), where other instances can resume the work. http://aka.ms/AzPstrScalabilityV1BuildAndDeploy INTERNAL: Monitoring processes inside the system is
http://aka.ms/AzPstrScalabilityV1RunVisibility
in scale units, which are a
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignScaleOut
worker roles, 1 queue, and 2 SQL Database instances.
http://aka.ms/AzPstrScalabilityV1DesignSaveState essential to determine when additional scale-out is
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignSaveState
http://aka.ms/AzPstrScalabilityV1DesignScaleOut needed.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignSaveState http://aka.ms/AzPstrScalabilityV1RunVisibility
base configuration of web
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignScaleOut
http://aka.ms/AzPstrScalabilityV1RunVisibility
EXTERNAL: Monitor the performance from outside the
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
DECOUPLED COMMUNICATIONS http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
CHUNKY, NOT CHATTY http://aka.ms/AzPstrScalabilityV1BuildAndDeploy application to ensure service performance is within
and worker role instances
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1RunVisibility
acceptable ranges.

with supporting services


http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
such as data stores and
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
LOAD BALANCER
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
caching.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
Avoid tying up valuable resources by using an
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunScale
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
asynchronous decoupled programming method. Web
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
role instances put autonomous messages into a
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunScale
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
queue for pickup by worker role instances, which
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
continue the work. Throughput is controlled by the
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
Network calls require overhead for packet framing,
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
serialization, processing, and so on. Rather than use http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunScale
SCALE: BIGGER, BETTER, FASTER
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1RunScale
WEB WORKER STORAGE
"chatty" messages, batch them into fewer chunky
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
number of role instances producing and processing http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty ROLE(S) ROLE(S)
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
With visibility into the app, you can control scale
packages. Note, however, that batching can increase WEB ROLE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
messages. Explore using Windows Azure Service Bus
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1RunScale
with more precision. To automate, a separate pro-
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
or Storage Queues. http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
latency and exposure to potential data loss.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm INSTANCES cess monitors the system's vital signs. When a
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty
http://aka.ms/AzPstrScalabilityV1DesignChunkyNotChatty http://aka.ms/AzPstrScalabilityV1RunScale
threshold is crossed a new scale unit is deployed.
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignDecoupledComm
Three reasons to create
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1RunScale
When a lower threshold is crossed, a scale unit can
be removed.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons

Windows Azure scalable


http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
RETRY FOR FAULT TOLERANCE
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
CACHING
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunScale
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignCaching http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunScale
applications:
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1RunScale
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
DEMAND PEAKS
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
Transient errors and throttling are unavoidable in
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
Your app reaches thousands of users (or more)
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons large-scale systems. Instead of simply failing the
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol Windows Azure Caching improves performance by
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignCaching
although usage varies, sometimes greatly. http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
operation, implement a robust retry strategy across storing recently used data for immediate reuse.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
the application to provide resiliency against failures.
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
Too many retries too quickly can add additional load,
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1DesignCaching
Application throughput and latency are typically
http://aka.ms/AzPstrScalabilityV1DesignCaching
bound by how quickly data and context can be
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunAutomation
DISTRIBUTED USERS AND DEVICES
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
Your users are spread out, even around the
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
so also employ a backoff strategy that allows the
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
resource to recover by waiting after
http://aka.ms/AzPstrScalabilityV1DesignCaching
retrieved, shared, and updated.
http://aka.ms/AzPstrScalabilityV1DesignCaching http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
MESSAGING
http://aka.ms/AzPstrScalabilityV1RunAutomation
AUTOMATION: SCRIPT FOR SUCCESS
http://aka.ms/AzPstrScalabilityV1RunAutomation
globe. http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons multiple retries.
http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol http://aka.ms/AzPstrScalabilityV1DesignCaching
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignRetryforFaultTol http://aka.ms/AzPstrScalabilityV1RunAutomation
Maintaining a running, highly scaled application
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
PARTITIONABLE WORKLOADS
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning http://aka.ms/AzPstrScalabilityV1BuildAndDeploy involves repeating operations on a regular basis.
http://aka.ms/AzPstrScalabilityV1RunAutomation
Your processes are divided into optimal-size FAN-OUT QUERIES HORIZONTAL PARTITIONING Concurrently develop a library of scripts that can be
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
loads of work, since cloud applications scale http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning http://aka.ms/AzPstrScalabilityV1RunAutomation
run on multiple deployments when needed. You can
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1RunAutomation
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
by adding capacity in chunks.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery manage Windows Azure services with the Service
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery Management API.
http://aka.ms/AzPstrScalabilityV1RunAutomation
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning WORKER ROLE WORKER ROLE WORKER ROLE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
Note: Not all of these need to be present in your
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
application, however, one that does not exhibit any of
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning WORKER ROLES
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
these characteristics is probably not an ideal fit.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
As user data increases, the need for storage increases.
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
TYPE: X TYPE: Y TYPE: CACHE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
The database must be partitioned. This graphic shows
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
a horizontal partition (also known as a shard) where http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery intact tables are separated into
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
Database lookup logic is placed in a cloud service. To individual databases. Each users data can be
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
find data, that cloud service determines the
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery
databases to query. The query is then fanned out to
distributed to particular databases. SQL Database
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
instances can also be partitioned using federation.
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1RunLoadTest
!
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons those databases.
http://aka.ms/AzPstrScalabilityV1DesignFanOutQuery You can create and delete databases very quickly.
http://aka.ms/AzPstrScalabilityV1DesignHorzPartitioning
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunLoadTest
LOAD TESTING: GETTING LOADED
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity http://aka.ms/AzPstrScalabilityV1RunLoadTest
Load test the system with both stress tests and by
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons VERTICAL AFFINITY
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy simulating real-life usage. Vary the load size to
http://aka.ms/AzPstrScalabilityV1RunLoadTest
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons

Plan & Design http://aka.ms/AzPstrScalabilityV1DesignVertAffinity avoid surprises! Ensure that responsiveness meets
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1RunLoadTest
user requirements, and that the entire system is
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
Build & Deploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunLoadTest
resilient.
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1RunLoadTest
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity http://aka.ms/AzPstrScalabilityV1BuildAndDeploy http://aka.ms/AzPstrScalabilityV1RunLoadTest
Run & Tune
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
When many users access data simultaneously, traffic
becomes a problem as scale increases. Design your http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
processes to access exclusive partitions to minimize STORAGE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
traffic and resource usage. http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
For example, assume databases are partitioned by
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
user. Ideally all operations that access a single user's
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
data are routed to a specific set of service instances.
Those instances access a single database partition
http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
holding all the user's data. http://aka.ms/AzPstrScalabilityV1BuildAndDeploy
SQL DATABASE TABLE STORAGE BLOB STORAGE
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1DesignVertAffinity
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons

http://aka.ms/AzPstrScalabilityV1Title
http://aka.ms/AzPstrScalabilityV1LeftPaneBenefitsAnd3Reasons

Scaling Applications Using Windows Azure Cloud Services Like it? Get it.
http://gettag.mobi
2013 Microsoft Corporation. All rights reserved. Created by the Windows Azure Team Email: AzurePoster@microsoft.com Part no. 098-117613