Leveraging a Virtualized Data Center to Improve Business Agility – Conclusion Read Part 1, Part 2… Virtualized Data Center – Keeping it Simple Early designs of cloud computing focused on blades with an independent Storage Area Network (SAN) architecture. This blueprint consolidated the CPU and memory into dense blade server configurations connected via several high-speed networks (typically a combination of Fibre Channel and 10GB) to large Storage Area Networks. This has been a typical blueprint delivered by traditional off the shelf pre-built virtualization infrastructure, especially in the enterprise in private cloud configurations. More recently, hardware vendors have been shipping modular
persistent storage
Microsoft Windows Azure Part II Continued from Part 1 Storage: The ability to execute the code is the fundamental requirement; applications need persistent storage to hold the code information when they are not running. As we saw in AWS, S3 or Simple Storage Service, Windows Azure has storage service. Also, Microsoft has another cloud service called SQL Azure which we will take it up later. The simple way to store in Windows Azure is to use BLOBS. A separate storage account needs to be created. In this account data is stored in containers. A single account can contain many containers
