[AzurePT] Desenvolvimento para o Windows Azure: Diferença para o developer
•
0 j'aime•517 vues
Desviei-me um pouco do título e dei mais ênfase à arquitectura dos serviços.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (18)
Similaire à [AzurePT] Desenvolvimento para o Windows Azure: Diferença para o developer
Similaire à [AzurePT] Desenvolvimento para o Windows Azure: Diferença para o developer (20)
Plus de Vitor Tomaz
Plus de Vitor Tomaz (8)
Dernier
Dernier (20)
[AzurePT] Desenvolvimento para o Windows Azure: Diferença para o developer
- 4. Recusos Capacidade CAPACIDADE Poucos recursos disponíveis Prevista Demasiados recursos Capacidade Real TEMPO
- 5. Capacidade Escalabilidade Capacidade on Prevista Demand CAPACIDADE Não há Elasticidade recursos desperdiçados Baixo Investimento Capacidade Real TEMPO
- 6. Escalabilidade Custos
- 7. Packaged Infrastructure Platform Software Software (as a Service) (as a Service) (as a Service) You manage Applications Applications Applications Applications You manage Data Data Data Data Runtime Runtime Runtime Runtime Managed by vendor Middleware Middleware Middleware Middleware You manage Managed by vendor O/S O/S O/S O/S Managed by vendor Virtualization Virtualization Virtualization Virtualization Servers Servers Servers Servers Storage Storage Storage Storage Networking Networking Networking Networking
- 12. Fabric Controller Fabric Controller Fabric Controller Datacenter Datacenter Datacenter
- 15. Aggregation Routers and Load Balancers LB AGG LB Top of Rack Switches TOR TOR TOR TOR TOR … … … … … Power Distribution PDU PDU PDU PDU PDU Units
- 16. Aggregation TOR Routers and Load Balancers Agg LB LB Top of Rack Switches … TOR TOR TOR Nodes Nodes Nodes … PDU PDU PDU Power Distribution PDU Units
- 17. SQL Exchange Word SQL Azure Server Online Server Datacenter
- 18. Windows Image Repository Fabric Controller Deployment Server Parent Windows Azure Role Role RoleRole PXE Maintenance OS OS ImagesImages Images Images Server Windows FC Host Azure Agent Node OS Windows Azure Hypervisor
- 19. Role B Worker Role www.mycloudapp.net Count: 2 Update Domains: 2 Size: Medium www.mycloudapp.net Load Balancer
- 20. Nó físico Guest Guest Guest Partition Partition Partition Role Instance Role Instance Role Instance Guest Guest Guest Agent Agent Agent Trust boundary Host Partition Image Repository (OS FC Host Agent VHDs, role ZIP files) Fabric Controller (Primary) Fabric Controller (Replica) … Fabric Controller (Replica)
- 21. Role B Worker Role www.mycloudapp.net Count: 2 Update Domains: 2 Size: Medium www.mycloudapp.net Load Balancer
- 22. Fault Domain Fault Domain Rack Rack Web Role Web Role U/G Domain #1 U/G Domain #2 Worker Role Worker Role U/G Domain #1 U/G Domain #2
- 24. Front- Middle End-1 End-2 Tier-3 Tier-1 Tier-2 Front- Front- End-1 End-2 Middle Middle Middle Tier-1 Tier-2 Tier-3 Update Update Update Domain 1 Domain 2 Domain 3
- 25. Production VIP – VIP1 Staging VIP – VIP2 <dnsname>.cloudapp.net <guid>.cloudapp.net Port Port Port Port Port Port 80 3389 3390 80 3389 3390 Role A Role B Role A’ Role B’ Deployment A Deployment A’
- 27. Tamanho da Largura de CPU Memória Local Storage Instância Banda Extra Small 1.0 GHz 768 MB 20 GB 5 Mbps Small 1.6 GHz 1.75 GB 225 GB 100 Mbps Medium 2 x 1.6 GHz 3.5 GB 490 GB 200 Mbps Large 4 x 1.6 GHz 7 GB 1,000 GB 400 Mbps Extra large 8 x 1.6 GHz 14 GB 2,040 GB 800 Mbps
- 30. ”volátil”
- 31. hora de relógio
- 34. FE FE FE Partition Lock Master Service Partition Partition Partition Partition Server Server Server Server DFS Servers
- 37. Incoming Write Request Ack FE FE FE FE FE Partition Lock Master Service Partition Partition Partition Partition Server Server Server Server DFS Servers
- 42. Três Uma Base de Dados Base de Dados Físicas Lógica Primary Secondary DB 1 Secondary 2
- 44. Client Layer PHP ASP.NET WCF Data Services OBDC ADO.NET Tabular Data Stream (TDS)
- 45. TDS Services Layer Sessão Gateway TDS
- 46. Platform Layer Node 14 SQL Instance SQL DB User User User User DB1 DB2 DB3 DB4 SQL Azure Fabric Node 15 SQL Instance SQL DB User User User User DB1 DB2 DB3 DB4 SQL Azure Fabric
- 47. Apps use standard SQL client Application libraries: ODBC, ADO.Net, PHP, … Internet Load balancer forwards ‘sticky’ TDS (tcp) LB sessions to TDS protocol tier TDS (tcp) Gateway Gateway Gateway Gateway Gateway Gateway TDS (tcp) SQL SQL SQL SQL SQL SQL Scalability and Availability: Fabric, Failover, Replication, and Load balancing
- 50. %d
- 51. 131075 8 7 6 5 4 3 2 1 0
- 53. select sum(reserved_page_count)*8.0/1024 AS [Storage_in_MB] from sys.dm_db_partition_stats
- 54. select highest_cpu_queries.total_worker_time, q.text AS [Query_Text], highest_cpu_queries.plan_handle from (select top 50 qs.plan_handle, qs.total_worker_time from sys.dm_exec_query_stats qs order by qs.total_worker_time desc) as highest_cpu_queries cross apply sys.dm_exec_sql_text(plan_handle) as q order by highest_cpu_queries.total_worker_time desc
- 55. select top 25 (total_logical_reads/execution_count) as avg_logical_reads, (total_logical_writes/execution_count) as avg_logical_writes, (total_physical_reads/execution_count) as avg_phys_reads, Execution_count, sql_handle, plan_handle from sys.dm_exec_query_stats order by (total_logical_reads + total_logical_writes) Desc
- 64. Role Instance Diagnostic Role Monitor Local directory storage
- 66. Poll Interval Role Instance Diagnostic Role Monitor Local directory storage
- 68. North Europe North Central US West Europe South Central US East Asia Southeast Asia Hosting locations within 100ms of the Regional hosting locations customer At least one hosting location can be reached within 100ms, but not two 200ms Latency from 2 regional hosting locations No points to test from or greater than 200ms latency
- 69. SQL Azure
- 70. SQL Azure Blog Post: Testing Client Latency to SQL Azure http://blogs.msdn.com/b/sqlazure/archive/2010/05/27/1001 6392.aspx
- 71. FromTo (ms) North-central US South-central US North Europe West Europe East Asia South-East Asia North-central US 4.2 35.3 97 103.6 190.9 219.7 South-central US 37.8 2.3 111.2 117.5 190 218.6 North Europe 99.8 111.8 2 20.9 283.3 312.3 West Europe 107.5 118.6 21.1 2.3 291.8 320.8 East Asia 194.5 190.8 284.2 291.7 1.6 32.6 South-East Asia 223.1 219.2 312.9 320.1 32.2 1.9
Notes de l'éditeur
- Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaking Points:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure Platform best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
- Speaking Points:At PDC10 in just over a month, we will introduce several new services including: Caching and Reporting. We will also have a new CTP for the Data Sync Service and Project Dallas will be finally available. Let’s drill into these services in a bit more detail.--Speaking Points:I suspect most if not all of you in this room are familiar with the Windows Azure Platform today.Today the platform consists of a set of foundational services SQL Azure relational databaseAppFabric provides services that can be used by any apps – hosted in Windows Azure, on-premises, or hosted in another environment. Questions:How many of you are building applications for Windows Azure?How many are using SQL Azure?How many are using the Access Control service today? The Service Bus?Notes:Windows Azure StoryWe are building an open platform to run your applications in the cloud. Your apps are .NET, Java, PHP, etc. We love everyone.We are going to help you migrate your existing apps to the cloud. The cloud platform is the future. Enables scale, self-service, lowers friction, etc. We provide the best cloud platform for building new apps. (aka n-tier, web services, etc.)
- Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later)Explain at a high level how SQL Azure worksSpeaker NotesDesign Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low frictionSQL Azure is a high availability databaseAlways three transaction consistent replicas of the databaseOne primary replica; two slave replicasFailure of a replica will result in another replica being spun up immediately by the fabricFailure of the primary replica means a slave replica will become the primary and a new slave will spin upMinimal down timeTypically just a few dropped connectionsEasy to code for the failover scenario- if you are ding god connection management and error handling will be fineClustered index required on all tables to allow replicationNotesUseful article from SQL Azure teamhttp://msdn.microsoft.com/en-us/magazine/ee321567.aspx