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.

[OPS50] Preparing for growth Capacity planning and scaling

53 views

Published on

Descrição: Quando o seu crescimento ou a demanda por seus sistemas excederem, ou se prevê que excedam, sua capacidade atual - esse é um "bom" problema.  No entanto, isso pode ser tanto uma ameaça à confiabilidade do seu sistema quanto qualquer outro fator.

Nesta sessão, mergulhe nos conceitos básicos de planejamento de capacidade e estimativa de custos, incluindo as ferramentas que o Azure fornece para ajudar com ambos.

Terminamos com uma discussão e demonstração de como os Traders Tailwind aplicaram criteriosamente os recursos de dimensionamento do Azure.  Aprenda como satisfazer seus clientes e uma demanda crescente, mesmo quando "desafiado" pelo sucesso.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

[OPS50] Preparing for growth Capacity planning and scaling

  1. 1. Preparing for Growth— Capacity Planning and Scaling Dean Bryen Principal Cloud Advocate
  2. 2. Resources Session Resources Hub aka.ms/OPS50 Session Code on GitHub aka.ms/OPS50repo All Event Session Resources aka.ms/mymsignitethetour
  3. 3. Here’s our map The Dickerson Hierarchy of Reliability
  4. 4. OPS50 OPS40 OPS30 OPS20 OPS10Monitoring Incident response Post-incident review Testing/release Capacity/scale DEV UX Welcome to the OPS learning path
  5. 5. OPS50Capacity/scale Our session today
  6. 6. New product line launching soon! The revolutionary electric Hammer!
  7. 7. THE ELECTRIC HAMMER!
  8. 8. iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Website Mobile for frontend Backend for frontend Single points of failure
  9. 9. iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Website Mobile for frontend Backend for frontend Pre-provisioned capacity
  10. 10. iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Website Mobile for frontend Backend for frontend Unknown costs
  11. 11. iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Website Mobile for frontend Backend for frontend Tailwind Traders architecture
  12. 12. When may we need to scale? Sometimes we can plan for scale Sometimes we’re hit by surprise Hopefully, the system just takes care of it
  13. 13. A quick primer
  14. 14. Some pre-requisites Scaling up Scaling out Manually scaling Auto-scaling DIY scale Inherent scale https://aka.ms/OPS50architecture
  15. 15. Scalability ❤️ Reliability Most of the time….
  16. 16. Planning for scale and growth
  17. 17. Do I need to do capacity planning in the cloud?
  18. 18. iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Mobile for frontend Backend for frontend Website
  19. 19. Understanding how Azure CosmosDB measures capacity
  20. 20. Request units (RU/s)
  21. 21. Retrieving capacity metrics
  22. 22. Azure Cosmos DB capacity planning—organic growth 2530 5100 7435 10081 0 2000 4000 6000 8000 10000 12000 July August September October Users Example Tailwind Traders usage Users
  23. 23. Azure Cosmos DB capacity planning—organic growth 151 198 254 300 5000 5000 5000 5000 0 1000 2000 3000 4000 5000 6000 July August September October Storage Capacity Example Tailwind Traders usage Storage
  24. 24. Azure Cosmos DB capacity planning—organic growth 0 100 200 300 1000 1000 1000 1000 0 200 400 600 800 1000 1200 July August September October RU/s Usage Provisioned RU/s Example Tailwind Traders usage Throughput
  25. 25. Azure Cosmos DB capacity planning—organic growth 0 100 200 300 400 500 600 700 800 900 1000 1100 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 0 200 400 600 800 1000 1200 RU/s Usage Provisioned RU/s Example Tailwind Traders usage Throughput
  26. 26. But what about in-organic growth? It’s a cross team effort
  27. 27. In-organic planning Example known event! What we know What we can expect
  28. 28. Azure Cosmos DB capacity planning—organic growth 151 198 254 300 400 5000 5000 5000 5000 5000 0 1000 2000 3000 4000 5000 6000 July August September October November Storage Capacity After marketing event Storage Example Tailwind Traders usage
  29. 29. Azure Cosmos DB capacity planning—organic growth 0 100 200 300 500 1000 1000 1000 1000 1000 0 200 400 600 800 1000 1200 July August September October November RU/s usage Provisioned RU/s Example Tailwind Traders usage Throughput After marketing event Sufficient capacity
  30. 30. In-organic planning—cost 75 59.52 134.52 100 59.52 159.52 0 20 40 60 80 100 120 140 160 180 Storage Throughput Total Before Event (USD) After Event (USD) Example Tailwind Traders usage
  31. 31. The cloud has limits too The cloud offers a whole new level of scale. However, there are some limits to know about. aka.ms/OPS50limits
  32. 32. Service limits and quotas: portal
  33. 33. List usages—API 124 1000
  34. 34. Keep an eye on the cost Adding more servers makes you more scalable But it can cost more, too
  35. 35. Cost management
  36. 36. Scaling Tailwind Traders
  37. 37. Perform regular architecture reviews Keeping on top of things once deployed, will ensure you’re always ready for scale aka.ms/OPS50architecture
  38. 38. Scaling vs. finding the bugs Do we always need to scale? Or is there a bug?
  39. 39. You work closely with developers to make your systems more scalable
  40. 40. Tailwind Traders architecture iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile My coupons Cart Popular products Website Mobile for frontend Backend for frontend Products
  41. 41. Scaling our products service Azure Region Availability Zone B
  42. 42. Scaling our products service: scale sets Azure Region Availability Zone AAvailability Zone B
  43. 43. Why use scale sets? Autoscaling Leverage Availability Zones Automatically create and integrate with load balancers
  44. 44. Some considerations Avoid instance stickiness Remove persistent data Design for scale-in
  45. 45. Scaling our products service: decoupling Azure Region Availability Zone AAvailability Zone B
  46. 46. Scaling with queues
  47. 47. Scaling our products service: caching Azure Region Availability Zone AAvailability Zone B Redis cache
  48. 48. Scaling our products service: database Redis cache Azure Region Availability Zone AAvailability Zone B Read replica
  49. 49. Read replica #Master Connection String ApplicationIntent=ReadWrite #Read Replica Connection String ApplicationIntent=ReadOnly #Full Example ApplicationInte nt=ReadOnly
  50. 50. Azure Region Scaling our products service: DB sharding Availability Zone AAvailability Zone B A B C A B C Read replica
  51. 51. Why we may need to shard Too much data Too much throughput Physical isolation
  52. 52. What’s next? Going global? Do we need to go global? Can we leverage a CDN? Would independent systems be more suitable? What consistency do we need for the data?
  53. 53. Tailwind Traders architecture iOS and Android client applications Rewards app Azure Kubernetes Service Stock Profile Products My coupons Cart Popular products Website Mobile for frontend Backend for frontend
  54. 54. Summary: planning for growth Are you aware of your service limits Can you plan for scale using capacity planning? Can you predict your future cloud spend?
  55. 55. Summary: scale Could you leverage an inherently scalable cloud service instead? Should we fix the bug? Or scale our resources? Are you able to scale horizontally? Can you decouple your system using queues? Will caching help?
  56. 56. Summary: reliability Are you leveraging availability zones for reliability? Do you really need to go global?
  57. 57. /Docs alert aka.ms/OPS50architecture
  58. 58. /MS Learn alert aka.ms/OPS50MSLearnCollection Complete interactive learning exercises, watch videos, and practice and apply your new skills
  59. 59. /Microsoft Certification alert Microsoft Certified: Azure Solutions Architect Expert Get hired, stay ahead, and receive the recognition you deserve #MSIgniteTheTour aka.ms/SolutionsArchitectCert
  60. 60. Free Certification Exam on Fundamentals or Role-based Certifications Find a Learning Partner to help you prepare aka.ms/LearningPartner Begin with free online training Microsoft.com/Learn Learn more about Microsoft Certifications Microsoft.com/Certifications Now is your chance to stand out among your peers. Get certified and prove your expertise to employers and peers and get the recognition and opportunities you've earned. Exclusive offer for Microsoft Ignite The Tour attendees aka.ms/FreeExam_MSIgnite Limited to one per eligible attendee. Terms and conditions apply. Please see website for details.
  61. 61. Resources Session Code on GitHub Session Resources aka.ms/mymsignitethetour All Event Resources aka.ms/OPS50repo aka.ms/OPS50 #MSIgniteTheTour Get Certified Azure Solutions Architect Expert aka.ms/SolutionsArchitectCert

×