20170209 dev day-websites_vs_cloudservices_vsservicefabric_scenarios

Editor's Notes

• #8: Slide Objectives: Explain the three scale choices on Windows Azure Web Sites. Notes: Both free and shared are the same architecture. The only difference is that free has quotas where as with shared you can use and pay for as much resources as you choose. With reserved you isolate your application to your own virtual machines that you can use and pay for whatever resources you choose.
• #9: Slide Objectives: Explain how you can start with a small site hosted for free. Notes:
• #10: Slide Objectives: Explain how you can scale your site to multiple shared instances. Notes:
• #11: Slide Objectives: Explain how you can move to reserved instances for additional scale. Notes:
• #12: Slide Objectives: Explain how you can scale up reserved instances to multiple instances as needed. Notes:
• #13: Slide Objectives: Explain how you can host multiple sites that you own on a your reserved instances. Notes:
• #15: Note: VM is separated out as IaaS offering.
• #16: Slide Objective Understand the difference between Roles and Instances Speaker Notes The Service model defines the shape of a service- the Roles it will have endpoints it will listen on Types of VMs that will be run At runtime each Role will run at a given scale Specifically each role will be deployed onto and executed on one or more VMs A VM runs a single role Notes Notes on the various security roles involved in running a Windows Azure account http://blog.toddysm.com/2010/01/subscription-and-service-administration-in-windows-azure.html
• #18: The infrastructure of each Windows Azure data center is notionally divided into multiple sections known as fault domains. These sections of the infrastructure (which are not necessarily individual servers or server racks) are designed in such a way that a failure of one fault domain is extremely unlikely to affect any other fault domain. When you deploy a service, the Windows Azure Fabric Controller automatically locates the roles in at least two different fault domains so that a failure in one domain will not affect all instances of your service.
• #19: Slide Objective Understand what a scale-out application looks like Speaking notes High scale applications often follow this sort of an pattern Inbound connectivity comes through a load balancer Requests are round robin routed Load 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 servers By stateless we mean that they do not hold state between client requests Stateless means that simple load balancing works – no need for sticky sessions Stateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancer A stateful or storage tier This will generally involve some sort of scale out approach for large apps Often using partitioned databases Often some sort of queuing mechanism Applications will often perform processing in the background. Improves response time for users Allows load peaks to be buffered in queues Windows Azure provides us with a Platform as a Service offering to implement these sorts of applications Notes http://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
• #21: Slide Objective Understand the 3 common patterns of worker roles Speaker Notes Pattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue again Pattern 2 Worker listens for inbound TCP requestCan implement with Raw TcpListeners or use WCF or use Hosted Web Core Pattern 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 server Notes http://blog.smarx.com/posts/build-your-own-web-role-running-hosted-web-core-in-windows-azure http://blog.smarx.com/posts/making-songs-swing-with-windows-azure-python-and-the-echo-nest-api
• #22: Slide Objective Understand how a Web Role extends the standard worker role Speaker Notes A web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web Core Web 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 Storage If 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. Notes http://msdn.microsoft.com/en-us/library/dd179341.aspx http://blogs.msdn.com/b/carlosag/archive/2008/04/14/hostyourownwebserverusingiis7.aspx http://blogs.iis.net/ksingla/archive/2007/12/20/ins-amp-outs-of-hostable-web-core.aspx
• #24: Slide Objective To understand how and why to change the VM Size for a Windows Azure role Slide Notes When 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 cores the memory capacity the local file system size allocated to a running instance Each physical machine in Windows Azure contains 8 processor cores. You need to specify an XL instance to reserve an entire machine Network is shared but burstable Can burst beyond your 1/8th allocation when using a small VM May be limited to just your allocation For guaranteed high network throughput use an XL VM Not http://msdn.microsoft.com/en-us/library/ee814754.aspxes