Downloaded 48 times
Uploaded byukdpe
Explaining The Cloud
The document discusses the concept of cloud computing, including definitions, types, benefits, and regulatory considerations. It emphasizes the importance of a hybrid approach that includes both software and services, while also addressing the need for offline options for users without broadband access. Additionally, it highlights Microsoft's vision for cloud infrastructure and collaboration capabilities, along with considerations for selecting cloud solutions.
More Related Content
Similar to Explaining The Cloud
![How Microsoft Secures its Online Services [WHITEPAPER]](https://cdn.slidesharecdn.com/ss_thumbnails/microsoftonlinesecurity-100122154531-phpapp01-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Explaining The Cloud
- 1. Explaining the CloudViralTarpara – Technical Evangelist - Microsoft
- 2. Questions to AskWhatis the Cloud?What are the Different Types of Cloud?Why the Cloud?Is Client/Server Dead?Regulatory and Compliance Laws ?Data Protection?Who to choose?
- 3.
- 4. What is theCloud?
- 5. Definition: CloudA modelfor enabling convenient, on-demand network access to a sharedpoolof configurable computing resources that can be rapidlyprovisioned and released with minimalmanagementeffort or service provider interaction.- Definition of Cloud Computing - NIST 2009
- 6.
- 7.
- 8. Software +Services
- 9. I see the“services”Where is the “software?”
- 10. Computing RealitiesSaaS isn’tthe silver bulletRich clients will always be neededNative clients tend to be prefferedComputational efficiency matters7 billion people without broadband
- 11.
- 12.
- 13. 3 Screens andThe Cloud
- 14.
- 15. Application ComputeStorageFabricConfigWindows AzureWindowsin the cloudAppFabricApplicationsSQL AzureWindows AzureApplicationsMobileDesktopServerOthers
- 16. Web vs WorkerRoleWorker RoleWeb RoleSystem HostIIS HostYour CodeYour Code
- 17. Common Azure PatternWorkerRoleWeb RoleQueueStorageBlobStorage
- 18. StorageStorage*QueueBlobAccountTables* New for2010 - “Drives” – durable NTFS volumes built on Blob storage
- 19.
- 20. TablesEntitiesTablesGenre = …Title = …MoviesGenre = …Title = …ActorsName = …DOB = …
- 21.
- 22.
- 23. Development Fabric andStorageLocal MachineWindows Azure Simulation Environment Development StorageDevelopment Fabric
- 24.
- 25. Windows Azure forApplication DevelopersHostedServicePortalSDKStorageDevelopRunDeploy
- 26.
- 27. Map Your InfrastructureJourneyFully managed collaboration platform with governance and pervasive access; disconnected, cross-firewall collaboration; content-centric social computing capabilities Seamless, federated collaboration across the firewall; building robust composite applications; people-centric social computing capabilitiesBasic e-mail, file shares, face-to-face meetings as Collaboration; possible ad-hoc workspaces or portals exist; possible static intranetOrg-wide collaboration infrastructure in place; possible experimentation with social computing, but not part of infrastructureIT is a more efficient cost centerIT is a strategic assetIT is a cost center IT is a business enabler
- 28.
- 29.
- 30. Which Cloud toChoose?Best ToolsBest Offline StoryBest SLAsBest Interoperability
Editor's Notes
- #4 World where a developer no longer has to worry about infrastructureWorld where a developer can use any language they wantWorld where millions of loosely and tightly coupled software components can seamlessly communicate with each other
- #5 Windows Azure runs on a large number of machines, all located in Microsoft data centers and accessible via the Internet. A common Windows Azure fabric knits this plethora of processing power into a unified whole. Windows Azure compute and storage services are built on top of this fabric. The Windows Azure compute service is based, of course, on Windows. For the initial availability of this service, a Community Technology Preview (CTP) made public in the fall of 2008, Microsoft allowed Windows Azure to run only applications built on the .NET Framework. The company has announced plans to support unmanaged code as well, i.e., applications that aren’t built on the .NET Framework, on Windows Azure in 2009. In the CTP version of Windows Azure, developers can create .NET-based software such as ASP.NET applications and Windows Communication Foundation (WCF) services. To do this, they can use C# and other .NET languages, along with traditional development tools such as Visual Studio 2008. And while many developers are likely to use this initial version of Windows Azure to create Web applications, the platform also supports background processes that run independently—it’s not solely a Web platform. Both Windows Azure applications and on-premises applications can access the Windows Azure storage service, and both do it in the same way: using a RESTful approach. The underlying data store is not Microsoft SQL Server, however. In fact, Windows Azure storage isn’t a relational system, and its query language isn’t SQL. Because it’s primarily designed to support applications built on Windows Azure, it provides simpler, more scalable kinds of storage. Accordingly, it allows storing binary large objects (blobs), provides queues for communication between components of Windows Azure applications, and even offers a form of tables with a straightforward query language. Running applications and storing their data in the cloud can have clear benefits. Rather than buying, installing, and operating its own systems, for example, an organization can rely on a cloud provider to do this for them. Also, customers pay just for the computing and storage they use, rather than maintaining a large set of servers only for peak loads. And if they’re written correctly, applications can scale easily, taking advantage of the enormous data centers that cloud providers offer. Yet achieving these benefits requires effective management. In Windows Azure, each application has a configuration file. By changing the information in this file manually or programmatically, an application’s owner can control various aspects of its behavior, such as setting the number of instances that Windows Azure should run. The Windows Azure fabric monitors the application to maintain this desired state. To let its customers create, configure, and monitor applications, Windows Azure provides a browser-accessible portal. A customer provides a Windows Live ID, then chooses whether to create a hosting account for running applications, a storage account for storing data, or both. An application is free to charge its customers in any way it likes: subscriptions, per-use fees, or anything else. Windows Azure is a general platform that can be used in various scenarios.