Azure.application development.nhut.nguyen

Editor's Notes

• #5: Slide Objectives: Explain the three established industry terms for cloud services Speaker Notes: 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.
• #9: Speaking Points: The second thing that I want to help you understand… neat thing that we’re doing with Windows Azure now is making it possible for you to mount durable drives to your virtual machine. We’re trying to do it in way that it is very reliable, consistent, and delivers a high performance. One of the things that’s different about how we enabled it is that when you mount a drive either in the portal or in the command line we are backing the disk with the Windows Azure Storage system that we’re running in the cloud today There are a couple nice characteristics about the storage system. Replication One is that we triple replicate the content within the data center. If a disk ever goes bad that you data is on then we have two other copies of the data that we can work with and we do not have any interruption of service We can then spin up a new replica once we detect a disk is bad From your VMs perspective you never know that an issue actually occurred [Transit to next slide] So you get much more reliability and an always on experience even when hardware fails One of the things that we provide which is a little different with Windows Azure is a really powerful storage architecture When we booted up our Virtual Machine and you saw all of the disks attached to it, the disks were not actually disks. They were virtual disks on top of our Windows Azure Storage system. We have redundancy built in for you. We can also load balance our reads and writes to the drives, so we can provide more predictable performance. On top of these physical drives that we use for blob storage we also have a set of SSD cache of drives. The benefit is that you are reading and writing through an SSD drive and then back to the physical disk.
• #12: Speaking Points: This is designed to give you very reliable performance and hopefully it ensures that it is always on
• #13: Speaking Points: The third aspect of Windows Azure Virtual Machines that is important to understand is …. Another thing that is nice about the Windows Azure Storage solution is that we have support for Continuous storage geo-replication What this means is that whenever you save something in the storage system, in the background we can automatically replicate the data to another datacenter We guarantee that these data centers are several hundred miles (500) apart so that in the case of a natural disaster or a complete data center failure you can be ensured that a copy of your data exists somewhere else. You don’t have to set anything up to enable it. It’s automatically enabled by default. You can turn it off if there are policy reasons why you wouldn’t want it enabled. The end result is that you can deliver more robust solutions with even greater integrity
• #15: Speaking Points: The third aspect of Windows Azure Virtual Machines that is important to understand is …. Another thing that is nice about the Windows Azure Storage solution is that we have support for Continuous storage geo-replication What this means is that whenever you save something in the storage system, in the background we can automatically replicate the data to another datacenter We guarantee that these data centers are several hundred miles (500) apart so that in the case of a natural disaster or a complete data center failure you can be ensured that a copy of your data exists somewhere else. You don’t have to set anything up to enable it. It’s automatically enabled by default. You can turn it off if there are policy reasons why you wouldn’t want it enabled. The end result is that you can deliver more robust solutions with even greater integrity
• #16: Speaking Points: The third aspect of Windows Azure Virtual Machines that is important to understand is …. Another thing that is nice about the Windows Azure Storage solution is that we have support for Continuous storage geo-replication What this means is that whenever you save something in the storage system, in the background we can automatically replicate the data to another datacenter We guarantee that these data centers are several hundred miles (500) apart so that in the case of a natural disaster or a complete data center failure you can be ensured that a copy of your data exists somewhere else. You don’t have to set anything up to enable it. It’s automatically enabled by default. You can turn it off if there are policy reasons why you wouldn’t want it enabled. The end result is that you can deliver more robust solutions with even greater integrity
• #17: Speaking Points: The third aspect of Windows Azure Virtual Machines that is important to understand is …. Another thing that is nice about the Windows Azure Storage solution is that we have support for Continuous storage geo-replication What this means is that whenever you save something in the storage system, in the background we can automatically replicate the data to another datacenter We guarantee that these data centers are several hundred miles (500) apart so that in the case of a natural disaster or a complete data center failure you can be ensured that a copy of your data exists somewhere else. You don’t have to set anything up to enable it. It’s automatically enabled by default. You can turn it off if there are policy reasons why you wouldn’t want it enabled. The end result is that you can deliver more robust solutions with even greater integrity
• #19: Speaking Points: Transition Virtual machines provide a very flexible compute model. Another compute service available in Windows Azure is called Windows Azure Web Sites. Definition: Windows Azure Web Sites there is a managed service that you can use to run web sites and web APIs. Enable you to quickly stand up web applications and web sites on the internet Auto-managed environment Just say that you want a web, here’s the DNS, copy the content, and we do the rest You don’t have to worry or think about VMs, servers, or infrastructure. You can simply focus on building and deploying HTTP based applications. Enables you to build web sites using ASP.NET, Node.js, PHP, and now with an update a few weeks ago – Python Allows you to use any tool and any operating system to build these sites including Windows, OS X, and Linux. Enables a very fast deployment model. You can literally deploy in seconds. You can easily deploy these sites using the tools and infrastructure you know. We support several flexible deployment options including FTP, GIT, and Team Foundation Services What is nice about this offering is that not only does it enable to very quickly get going, but it also allows you to start with a free offer in a shared environment. Pricing starts at free.. Perpetually free and then you can scale up as you need more capability You can then scale up these sites using reserved instances for higher performance and isolation and scale out these sites as your web site becomes successful and you have increased load.
• #20: Speaking Points: Just to recap When I’m running shared, multiple web sites from multiple customers are use the same virtual machine instances
• #21: Speaking Points: In shared mode the web sites can be scaled out to run on multiple shared instances, In this case Windows Azure provides load balancing of incoming requests resulting in better response time and performance for your application and higher availability
• #22: Speaking Points: If we really need to scale our application or we want to isolate our application, perhaps to use more memory, we can switch our app to reserved mode In this case Windows Azure will use an instance out of the pool of available instances, deploy your site, and continue to serve up requests
• #23: Speaking Points: Just like with shared mode, we can also scale out with reserved mode, in which case the machine instances are registered with the load balancer for your web application. This can result in better response time, performance, and availability for your web application.
• #24: Speaking Points: What’s also cool is that you can have multiple sites in a reserved instance. So if you have three or four sites as I had in the demo, they can all run in my reserved instance, so I can be more efficient with using the resources. This is great if you want to run multiple sites for others or sites you want to run isolated
• #28: It gets features a lot before the boxed product receives them.