Windows AzureでのスケーラブルなJavaアプリケーション構築 (JavaOne Tokyo 2012)
•Télécharger en tant que PPTX, PDF•
1 j'aime•1,098 vues
Windows AzureでのスケーラブルなJavaアプリケーション構築 JavaOne Tokyo 2012 (2012/04/04-05) http://www.oracle.com/javaone/jp-ja/ BoF1-02 2012/04/04 17:00-18:00 六本木アカデミーヒルズ49 [カンファレンスルーム2] 「Windows AzureでのスケーラブルなJavaアプリケーション構築」 #jt12_b102 概要 Windows Azureは、迅速なアプリケーションの構築、デプロイ、管理を可能にする、オープンで柔軟性のあるクラウド プラットフォームです。Windows Azureでは、アプリケーション構築のために多様な言語、フレームワーク、ツールを利用可能です。Javaクライアント ライブラリや、Windows Azure上で主要なJavaアプリケーション サーバーの稼働を可能にするEclipseプラグインなど、Windows AzureはJavaを強力にサポートしています。本セッションでは、Windows AzureにおけるスケーラブルなJavaアプリケーション構築について取り上げます。 講演者情報 日本マイクロソフト株式会社 デベロッパー&プラットフォーム統括本部 Windows Azure デベロッパー エバンジェリスト 佐藤 直生 氏 https://oj-events.jp/public/session/view/174
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (19)
Plus de Naoki (Neo) SATO
Plus de Naoki (Neo) SATO (20)
Windows AzureでのスケーラブルなJavaアプリケーション構築 (JavaOne Tokyo 2012)
- 11. コンピュー データ ストレージ ティング ベース サービス アクセス レポー CDN バス キャッシュ VM ティング 制御 11
- 12. データセンター
- 15. Power on & Power on & Configure Configure virtual server virtual server
- 23. シナリオ
- 27. <dependency> <groupId>com.microsoft.windowsazure</groupId> <artifactId>microsoft-windowsazure-api</artifactId> <version>0.2.0</version> </dependency>
- 60. 世界初！商用Javaアプリケーション実行基盤 Windows Azure Platformで世界初！(注)商用Java実行基盤 Windows Azure上でJavaアプリケーションが動作 (注）2011年8月1日時点弊社調べ Java標準ツールで業務システムを短期間で構築 業務負荷に応じたシステム運用 使い慣れたツール（Eclipse）で FGCP/A5 A5へ配備可能 流用 インスタンス インスタンス 既存アプリケーション 追加・削除 Javaアプリケーション Javaアプリ実行基盤 プラグイン インスタンス Javaアプリケーション Javaアプリ実行基盤 新規作成 新規アプリケーション 今までと同様に 開発・運用者 アプリケーション開発・修正が可能 エンドユーザー 60 Copyright 2011 FUJITSU LIMITED
Notes de l'éditeur
- Slide Objectives:Explain how Microsoft thinks of the cloudSpeaking Points:There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc.Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices.The cloud can help deliver IT as a standardized service…freeing you up to focus on your business
- Speaking Points:There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service.Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform.Notes:There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS. ----Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaking Points:With this in mind, it’s important to understand how to talk about our Cloud Services offerings.There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
- 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 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.
- First introduced the platform 3 years ago at the 2008 Professional Developers Conference.Three key principles…
- Windows Azure lets developers choose the framework and tools they want, with first-class support of .NET, Java, PHP and Node.js. Windows Azure consists of a set of foundational services - let’s take a quick tour, starting with 3 core services: Compute, Storage, DatabaseCompute:Windows Azure offers highly-available Compute capacity that enables you to run application code in the cloud and allows you to quickly scale your applications up or down to meet your customer needs. Each Compute instance is a virtual machine that isolates your application from other customers. Once Compute resources are assigned to your application, Windows Azure automatically handles network load balancing and failover to provide continuous availabilityStorage:The design point is for the cloud is availability of storage, there are 3 replicas of data, and we implement guaranteed consistency. In the future there will be some transaction support and this is why we use guaranteed consistency.There are 4 types of storageTables = Key value storeQueues = a simple queuing mechanismBlobs = Binary file storage in the cloudDrives = A mechanism that allows a VHD in a blob to be mounted as an NTFS drive into a Compute roleAuthenticated access and triple replication to help keep your data safe Easy access to data with simple REST interfaces, available remotely and from the data centerDatabase:Simple to provision- create a logical server in the Portal, execute a create DB Command to create a new databaseCan add and remove DBs easily from application to scale up and downNo need to install or patch software or other physical administrationAutomatic high availability and fault toleranceSupport for T-SQL based familiar relational database modelBeyond these 3 core services, Windows Azure offers a growing set of additional services to help you bring your application, and your business, to the next level.CDN:The Windows Azure CDN provides edge nodes around the world, providing better performance and user experience for users who are farther from the source of the content stored in the Windows Azure Blob service. Windows Azure Customers have control over how long data is cached.Windows Azure CDN has 20 locations globally (United States, Europe, Asia, Australia and South America) and continues to expandService Bus:The Service Bus is designed to provide a general purpose application bus, available on the internet at internet scale. Fundamentally, the .NET Service Bus is about connecting applications across network and application boundaries and making key message exchange patterns such as publish and subscribe messaging very simple.Access Control:The Access Control service is designed to provide rules-driven, claims-based access control for applications. Essentially, this allows you to define authorization rules for your applications using the claims-based approach that we are adopting within many Microsoft products and technologies and that is becoming adopted throughout the industry.Caching:Caching provides a distributed, in-memory, application cache service for Windows Azure applications. Instead of relying on slower disk-based storage, applications gain high- speed access and scale to data that is kept in-memory. VMs:Transfer your existing apps easily to Windows Azure without modificationDeploy durable virtual machines on Windows or Linux (customer uploads Linux image) (Linux VM - CTP Spring 2012)Reporting:SQL Server Reporting provided as a service Reports authored using existing tools (BIDS) Reports can include rich Data Visualizations (Maps, Charts, Tablix) and exported to variety of formats Traffic ManagerImproves app performance and resiliency by automatically routing traffic to the nearest deployed datacenter and provides seemless failover in the event of a failoverNetworkingWindows Azure offers multiple levels of connectivity through Windows Azure Connect and Project Brooklyn
- What does it take to do this successfully. Well, you can’t head-fake your way into building these cloud platforms and services, this isn’t a game of basketball. It takes a blend of expertise and the right investments to pull this off. NO OTHER company can match Microsoft today in our experience on running and building services. We know what it takes to do this, because we’ve been running services at Internet scale for years – from MSN in 1995, to Hotmail, Windows Live, and Bing, today. For example, we handle:9.9 billion messages a day via Windows Live Messenger600 million unique users every month on Windows Live & MSN1 Petabyte+ of updates served every month by Windows Update to millions of servers and hundreds of millions of PCs worldwide5M LiveMeeting conference minutes per yearForefront for Exchange filters 1B emails per monthTo support this and our business cloud services, we’ve made and continue to make significant investments in our datacenter infrastructure that our cloud services run on – resulting in a number of advantages: financially backed SLAs, a standard cost operating model, industry-leading modular datacenter models, a consumption-based chargeback model, and the ability to achieve global targets like a Power Usage Effectiveness (PUE) of 1.25. This is all alongside our full commitment in the engineering discipline and the operations discipline around delivering the cloud. Deeper Details on Microsoft Global Foundation Services (GFS) Infrastructure Services Operations – Microsoft Global Foundation Services (GFS) manages our global network of data centers and provides 1) Physical and Site Security 2)Critical Environments Support (Power, Water, Redundancy) and 3) Technical Support (Racks, Servers, Switches) with a focus on operational excellence to deliver lowest cost and highest service delivery globally.Data Center Innovation – GFS continues to deliver effective and efficient DC and infrastructure designs that deliver the most value to our internal customers. Today this means our IT Pre-Assembled Components (ITPACs) for our future modular data centers will provide a lower cost CAPEX per Mega Watt, enhanced speed to market, and reduction in OPEX. ITPACs are a game changer.Global Capacity – When choosing future datacenter sites, we take into account over 35 weighted criteria, including close proximity to an ample and stable power source and fiber optic networks, affordable pool of skilled labor, affordable energy rates, taxes, and capacity capabilities needed for our local, regional and global customers to determine the long-term viability of each site. Utility pricing – this is how GFS charges its customers by consumptions units and Consumption statementsare issued every 30 days to customers for: Compute (VM / hour), Storage ($ per GB), Network (traffic), Incidents (tickets)SOC/NOC – GFS manages the Microsoft Operations Center (MOC) that is a Tier 1 federated Ops center with failover in Redmond, India and California to ensure business continuity 24 x 7 x 365. The MOC is focused on delivering a comprehensive incident management and service support, with world class quality of service for 200 + property groups supporting incident management in a highly cost efficient model. They process more than 150K tickets a month supporting incidents, change management, release management and problem management. They are the first line of operational support for our cloud properties. Turnkey operations take a service from on-boarding to tooling through support. MOC supports non-windows environment. MOC uses MS Change as a primary change management tool (most universally recognized change management tool)Consumption Reporting: New Cost Model focuses on measuring and forecasting capacity utilization, cost driver transparency and accountability, and investment optimization and is aligned with ‘Improve Cost’ strategic theme. Key measurements: $/kW, $/Mbps, $/Incident, $/Server to provide transparent, accurate volume & rate insight by cost pool aligned to native cost. Standard rates by region, where applicable, provide greater predictability for BGs’ online COGSHardware Services – GFS provisions hardware via various standards programs such as containers, ITPACs and the Azure and MACH server programs.
- Slide ObjectiveUnderstand that Microsoft has a long history in running data centres and online applications. Bing, Live, Hotmail etc….Understand the huge amount of innovation going on at the data center levelSpeaking Points:Microsoft is one of the largest operators of datacenters in the worldYears of ExperienceLarge scale trustworthy environmentsDriving for cost and environmental efficientlyWindows Azure runs in 3 regions and 6 datacenters todayData center innovation is driving improved reliability and efficiencyPUE = Power Usage Effectiveness = Total Facility power/IT Systems Power = Indication of efficiency of DCUnder 1.8 is very good, modern cloud DCs approaching 1.2Multi-billion dollar datacenter investment700,000+ square foot Chicago and the 300,000+ square foot Dublin, Ireland data centersMicrosoft cloud services provide the reliability and security you expect for your business: 99.9% uptime SLA, 24/7 support. Microsoft understands the needs of businesses with respect to security, data privacy, compliance and risk management, and identity and access control. Microsoft datacenters are ISO 27001:2005 accredited, with SAS 70 Type I and Type II attestations.Notes:http://www.globalfoundationservices.com/http://blogs.msdn.com/the_power_of_software/archive/2008/06/20/microsoft-s-pue-experience-years-of-experience-reams-of-data.aspxhttp://blogs.msdn.com/the_power_of_software/archive/2008/06/27/part-2-why-is-energy-efficiency-important.aspx
- Speaking Points:3 core services: Compute, Storage, DatabaseLet’s take a look at the platform starting with the core services.Compute:Scalable environment for running codeEnables .NET, C++, PHP, Ruby, Python, …Automated service managementStorage:Scalable and highly available cloud storageBlobs, Tables, Queues, DrivesREST APIs and several client librariesDatabase:SQL Relational DatabaseFamiliar programming model & tools--Speaking Points:I suspect most if not all of you in this room are familiar with the Windows Azure today.Today the platform consists of a set of foundational services SQL Azure relational databaseWindows Azure 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 Objectives:Introduce Windows Azure Storage and some of the key features/capabilities of the storage serviceSpeaking Points:The design point is for the cloud is availability of storage, there are 3 replicas of data, and we implement guaranteed consistency. In the future there will be some transaction support and this is why we use guaranteed consistency.There are 4 types of storageTables = Key value storeQueues = a simple queuing mechanismBlobs = Binary file storage in the cloudDrives = A mechanism that allows a VHD in a blob to be mounted as an NTFS drive into a Compute roleBlobs, tables, and queues hosted in the cloud, close to your computation Authenticated access and triple replication to help keep your data safe Easy access to data with simple REST interfaces, available remotely and from the data center Access is via a storage account – you can have multiple storage accounts per live id.Although the native API is REST web service, there is a .NET storage client in the SDK that. This makes working with storage much easier from .NET
- Slide Objectives:Understand the key differentiators of SQL AzureUnderstand where a user has control and where the cloud runs thingsSpeaking Points:SQL Azure provides highly available SQL Server.Appears to be a SQL Server to the client.In reality is 3 transitionally consistent copies of the database that are fronted by a Gateway that appears to be a SQL serverSimple to provision- create a logical server in the Portal, execute a create DB Command to create a new databaseCan add and remove DBs easily from application to scale up and downCustomers look after logical optimizations like indexesSQL Azure manages the physical databaseNo need to install or patch software or other physical administrationAutomatic high availability and fault toleranceSimple provisioning and deployment of multiple databasesScale databases up or down based on business needsMulti-tenantIntegration with SQL Server and tooling including Visual StudioSupport for T-SQL based familiar relational database modelNoteshttp://www.microsoft.com/windowsazure/sqlazure/http://msdn.microsoft.com/en-us/windowsazure/sqlazure/default.aspx
- Slide Objectives:Understand the key differentiators of SQL AzureUnderstand where a user has control and where the cloud runs thingsSpeaking Points:SQL Azure provides highly available SQL Server.Appears to be a SQL Server to the client.In reality is 3 transitionally consistent copies of the database that are fronted by a Gateway that appears to be a SQL serverSimple to provision- create a logical server in the Portal, execute a create DB Command to create a new databaseCan add and remove DBs easily from application to scale up and downCustomers look after logical optimizations like indexesSQL Azure manages the physical databaseNo need to install or patch software or other physical administrationAutomatic high availability and fault toleranceSimple provisioning and deployment of multiple databasesScale databases up or down based on business needsMulti-tenantIntegration with SQL Server and tooling including Visual StudioSupport for T-SQL based familiar relational database modelNoteshttp://www.microsoft.com/windowsazure/sqlazure/http://msdn.microsoft.com/en-us/windowsazure/sqlazure/default.aspx
- Speaking Points:Building Block Services for developing connected applicationsYou could write code and build any of these services yourself…but you wouldn’t want to…Slide Objectives: Define and enumerate the Windows Azure ServicesSpeaking Points: Much in the same way that SQL Services is about extending SQL Server to the cloud, we are also extending key .NET capabilities to the cloud as services.We call this the Windows Azure Services. These services are really key components you would need for building distributed, connected applications. When we talk about connecting to your existing on-premises applications and enabling the composition of hybrid (Cloud + on-premises) applications – that is where these services really comes in.There are currently three services: Caching, Service Bus & the Access Control ServiceService Bus:The Service Bus is designed to provide a general purpose application bus, available on the internet at internet scale. You can really thin of the Service Bus as being similar to an Enterprise Service Bus that many enterprise organizations have today. However, we believe that when providing a Service Bus as a programmable service on the internet, there are a wider range of scenarios for many more types of organizations.Fundamentally, the .NET Service Bus is about connecting applications across network and application boundaries and making key message exchange patterns such as publish and subscribe messaging very simple.Access Control:The Access Control service is designed to provide rules-driven, claims-based access control for applications. Essentially, this allows you to define authorization rules for your applications using the claims-based approach that we are adopting within many Microsoft products and technologies and that is becoming adopted in the industry.Notes: Windows Azure has the .NET Framework built into it so thatyou can use those services within your application.But just like your application must be designed to scale out, the services that we have built into Windows over time in .NET also need to be designed and built in a way that can scale out naturally. We want to create services for you, and that's the purpose of these services, creating a pool of resources available to you to take advantage of and do things within your application very simply. So we're including a built-in, scale-out implementation of a service bus. The service bus lets you connect your on-premises systems securely into the cloud, into the Azure environment, while allowing your data and your information to traverse firewalls, solving a problem that is a bane of many application developments.
- Speaking Points:PerformanceDirects the user to the “best”/”closest” deploymentExample: Direct the user to the “best” deployment between US South and West EuropeFailoverOne deployment is primaryTraffic is redirected to another deployment if the primary goes downExample: All traffic is directed to US North; if it goes down, send all traffic to US SouthNotes:Traffic Manager monitors hosted services by executing periodic HTTP GET requests to an endpoint that you specify when creating a policy. In the simplest case, this endpoint can be the URL to a file served by the application. Traffic Manager considers the service to be available if its monitoring endpoint responds with an HTTP status code of 200 OK within 5 seconds.The Health Monitor Timeout provides an estimate of how long it takes Traffic Manager to become aware of the change.When a hosted service is disabled, its monitoring endpoint stops sending responses to simulate a failure. Traffic Manager performs a check of this endpoint at 30-second intervals and if it fails to receive a response to three consecutive polls, it considers the service as unavailable. Thus, it could take as much as 120 seconds for the service to failover.After you disable a service, a timer on the page starts showing the elapsed time since the status of the service changed, providing an estimate of how long it takes the Traffic Manager to become aware of the failure.Disabling a hosted service in a Traffic Manager policy can be useful for temporarily removing a malfunctioning service or during maintenance tasks.Example: all users from US -> US North, all users from Asia -> US North, all users from Europe ‑> West EuropeRatioSends traffic to different deployments based on fixed ratio (N/M)Example: Direct 20% of user traffic to US South and 80% to US North.
- Slide Objectives:Understand basic concept of a CDNUnderstand at a high level how Windows Azure CDN worksSpeaking Points:The Windows Azure CDN provides edge nodes around the worldData stored in CDN enabled storage accounts is retrieved from the origin storage container and cached at each edge node in a lazy load fashionWindows Azure Customers have control over how long data is cached for.Windows Azure CDN has 20 locations globally (United States, Europe, Asia, Australia and South America) and continues to expandThe benefit of using a CDN is better performance and user experience for users who are farther from the source of the content stored in the Windows Azure Blob service. Windows Azure CDN provides worldwide high-bandwidth access to serve content for popular events.Noteshttp://blogs.msdn.com/b/windowsazure/archive/2009/11/05/introducing-the-windows-azure-content-delivery-network.aspx
- Slide ObjectiveUnderstand the difference between Roles and InstancesSpeaker NotesThe Service model defines the shape of a service- the Roles it will haveendpoints it will listen onTypes of VMs that will be runAt runtime each Role will run at a given scaleSpecifically each role will be deployed onto and executed on one or more VMsA VM runs a single roleNotesNotes on the various security roles involved in running a Windows Azure accounthttp://blog.toddysm.com/2010/01/subscription-and-service-administration-in-windows-azure.html
- Slide ObjectiveUnderstand what a scale-out application looks likeSpeaking notesHigh scale applications often follow this sort of an patternInbound connectivity comes through a load balancerRequests are round robin routedLoad balancer is typically aware of the state of the web servers (i.e. are they up)There are one or more tiers or groups of stateless web or app serversBy stateless we mean that they do not hold state between client requestsStateless means that simple load balancing works – no need for sticky sessionsStateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancerA stateful or storage tierThis will generally involve some sort of scale out approach for large appsOften using partitioned databasesOften some sort of queuing mechanismApplications will often perform processing in the background. Improves response time for usersAllows load peaks to be buffered in queuesWindows Azure provides us with a Platform as a Service offering to implement these sorts of applicationsNoteshttp://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
- Slide ObjectiveUnderstand the lifecycle of a Windows Azure roleUnderstand the methods that can be overridden in RoleEntryPointUnderstand the events that are raised by role instances when their status is changingSpeaker NotesRoles will typically extend RoleEntryPointThe fabric calls RoleEntryPoint methods as it starts and stops a roleWaWorkerHost process is started.Worker Role assembly is loaded and surfed for a class that derives from RoleEntryPoint. This class is instantiated. RoleEntryPoint.OnStart() is called. RoleEntryPoint.Run() is called. If the RoleEntryPoint.Run() method exits, the RoleEntryPoint.OnStop() method is called . WaWorkerHost process is stopped. The role will recycle and startup again.As a role changes state it will raise the StatusCheck event.A status of Busy will mean the load balancer will not route requests to the instance.Notehttp://blogs.msdn.com/b/jnak/archive/2010/02/11/windows-azure-roleentrypoint-method-call-order.aspxhttp://msdn.microsoft.com/en-us/library/ee848065.aspx
- Slide ObjectiveUnderstand the 3 common patterns of worker rolesSpeaker NotesPattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue againPattern 2 Worker listens for inbound TCP requestCan implement with Raw TcpListeners or use WCF or use Hosted Web CorePattern 3 Run a 3rd party processWhen the role starts up or runs use a Process.Start() call to run a standard windows executable E.g. Running a database serverNoteshttp://blog.smarx.com/posts/build-your-own-web-role-running-hosted-web-core-in-windows-azurehttp://blog.smarx.com/posts/making-songs-swing-with-windows-azure-python-and-the-echo-nest-api
- Slide ObjectiveUnderstand how a Web Role extends the standard worker roleSpeaker NotesA web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web CoreWeb Roles run ASP.NET websites- they do this by using the IIS hostage web core. pretty much anything that will work in a standard IIS ASP.NET Web Site should work in Windows Azure. At MIX09, we additionally added support for IIS7’s FastCGI capability. As a note, any files that are part of a asp.net project on windows azure are READ ONLY! If you need to be able to change the contents of files:User Blob StorageIf its configuration, use the service model files – which can be changed at runtime.Inbound protocols are http(s) – outbound protocols are any TCP connection but NOT UDP.Noteshttp://msdn.microsoft.com/en-us/library/dd179341.aspxhttp://blogs.msdn.com/b/carlosag/archive/2008/04/14/hostyourownwebserverusingiis7.aspxhttp://blogs.iis.net/ksingla/archive/2007/12/20/ins-amp-outs-of-hostable-web-core.aspx
- Slide ObjectiveTo understand how and why to change the VM Size for a Windows Azure roleSlide NotesWhen you create your service model, you can specify the size of the virtual machine (VM) to which to deploy instances of your role, depending on its resource requirements.The size of the VM determines the number of CPU coresthe memory capacitythe local file system size allocated to a running instanceEach physical machine in Windows Azure contains 8 processor cores. You need to specify an XL instance to reserve an entire machineNetwork is shared but burstableCan burst beyond your 1/8th allocation when using a small VMMay be limited to just your allocationFor guaranteed high network throughput use an XL VMNothttp://msdn.microsoft.com/en-us/library/ee814754.aspxes