Escolar Documentos
Profissional Documentos
Cultura Documentos
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.
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.
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