Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Architecting Scalable Applications in the Cloud


Published on

There is an increasing importance to architect applications for both growth and optimal user experience. Modern development tools allow you to develop fantastic applications, but there are pitfalls with architecting the applications in the wrong way. This talk will discuss industry proven best practices for building highly scalable web sites and applications and how they might be implemented on Windows Azure.

Published in: Technology
  • Be the first to comment

Architecting Scalable Applications in the Cloud

  1. 1. Let’s get started…
  2. 2. So you have a scalability problem? Congratulations!
  3. 3. Scalability <> Performance
  4. 4. Scalability is how your application behaves as the number of users increases
  5. 5. Performance is how your application behaves for each user
  6. 6. CPU Utilization Transactions /second
  7. 7. Cost per Request Number of Requests
  8. 8. Load <> Stress
  9. 9. Load is how many simultaneous users your application can serve
  10. 10. Stress is how well your applicationbehaves when resources become limited
  11. 11. NetworkWhere are the Databasescalability limits? Web server Code
  12. 12. Pattern: Nickel Defense
  13. 13. Pattern: Scale Up
  14. 14. PATTERN: Scale Out Load Balancer
  15. 15. PATTERN: SpecializeWeb Application Web Services Image Server
  16. 16. PATTERN: Partition the database 1 Reference Transaction
  17. 17. PATTERN: Partition the database 2 Read Copy Read Copy Write Copy
  18. 18. PATTERN: Partition the
  19. 19. Balance the computing load
  20. 20. Offload the work
  21. 21. Web Worker
  22. 22. NoSQL
  23. 23. Distribute globally
  24. 24. Cacheresponsibly
  25. 25. Plan for concurrency
  26. 26. Anti-patterns• Blaming another department• “It works great on my machine!”• Attempting to maintain state• Spending all your time looking at the code• Caching everything (twice!)• Services calling services – especially across the network or networks
  27. 27. Question: “Scale Later”?
  28. 28. Azure: Core Services Azure Storage SQL Azure Web Web Worker Worker Web (Queues) (DB) Worker(Compute) (Compute) (Compute) (Compute) (Compute) (Blobs) (Compute) (Tables)
  29. 29. Your Next Step