No comments posted yet


Slide 3

Slide objectives: Explain what the cloud is in relationship to on-premises servers and hosted severs. Speaking Points: To put the cloud in perspective, let’s first think about the available options for deploying and running your application today. Today, there are a few established approaches for deploying and running applications. Server On one side you have on-premises servers or a self-hosted model. With on-premises servers, you bring your own machines, connectivity, software, and in some cases software licenses. You have complete control of the environment, the software stack, the hardware, etc. However, you also have complete responsibility. Your organization must have the skills and expertise to operate and manage the environment and software. You must take on the responsibility of patching the environment, replacing hardware, etc. These days, very few people want to be in this business. However, on-premises servers are not going away anytime soon. In some cases organizations have to maintain solutions running in an on-premises environment due to regulatory, data, or privacy requirements. Hosted Servers An established alternative to the on-premises model is with a hosted environment. With hosted servers, you are effectively renting capacity – including machines, connectivity, and in some cases software. With this model, you have less control then when you’re managing your own servers. For instance, you can’t walk up to a machine, and plug in an external drive to load data. Or easily make hardware or software adjustments to optimize for performance. However, you also have fewer responsibilities when it comes to operating, updating, patching, and managing the environment. What is generally much more attractive about a hosted model is the cost model. The upfront capital costs can be much lower then building out your own infrastructure. However, one of the downsides is that you generally pay for the fixed capacity on a monthly basis – even if your application is idle. Cloud What we are starting to see in the industry is the emergency of the cloud as a platform for building and running applications. So what is the cloud and how does it relate to these established options for running your apps? A cloud platform is designed as a shared, multi-tenant infrastructure. Cloud platforms utilize virtualization to: share hardware resources, provide isolation of applications or tenants, and also to provide a more dynamic infrastructure. Ability to scale out your application over multiple server instances. Because it is a shared infrastructure, there is even less control compared to a hosted environment. As this is an emerging space, there is a wide range of different types of cloud solutions. Some of the solutions focus purely on providing virtualized infrastructure. Servers you can remote into. However, many cloud platforms are starting to focus on raising the level of abstraction – so you can focus on building and deploying applications rather than remoting into machines and maintaining or patching servers. Old: Level of abstraction varies greatly today with the solutions in the market Within the cloud, there are things that are delivered as an infrastructure Services – services provided by the infrastructure and services you would consume programmatically Finally, one of the primary reasons why organizations ranging from startups, independent software vendors, and large enterprises are starting to investigate the cloud is the pricing model. With a cloud platform, you can expect a pay as you go pricing model – where you pay for what you use. [build arrow] I believe it’s important to understand that the cloud is part of a continuum. It is one of potential approaches that you can begin to use to deploy and run your applications. However, it’s important to understand that the cloud is not the silver bullet. It is not the perfect solution for every application. Notes: We view cloud as scale out, automated service management, high availability and multi-tenant But cloud has other considerations: location, infrastructure, business model, ownership and management

Slide 39

Slide objectives: Define and enumerate the .NET Services. Emphasis that we are using the Windows Communication Foundation and Windows Workflow Foundation as programming models for .NET Services. Speaking 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 these .NET Services. Some of you maybe familiar with previous codenames such as BizTalk 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 .NET Services really comes in. There are currently three .NET Services: the Service Bus, the Access Control Service, and the Workflow Service Service 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. Workflow Service: The workflow service provides a shared execution environment for running declarative workflows. These workflows are really focused on orchestrating messages across the service bus. So you can imagine the scenario where you might need to publish a few messages on the bus and wait for responses. We want to enable you to model these patterns declaratively and execute these orchestrations in the cloud. In the case of all of these services, we are extending the programming models and tools that are available in the .NET Framework today. Specifically, the Service Bus is delivered as a set of extensions to WCF – in the form of new bindings that you can configure. The Workflow Service, as another example, uses Windows Workflow Foundation and the WF designer built into Visual Studio to design the workflows that interact with the service bus. Notes: Windows Azure has the .NET Framework built into it so that you 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 .NET 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. Access control is a key thing, the need to have federated access, federated identity providers, identity authorities that exist in a heterogeneous way. Many enterprises have their own identity provider, many of them are Active Directory, there are other key identity providers out there. Access control provides a way of enabling federation across these different identity providers both on premises and then into the cloud. Work flow is a key mechanism used by many applications. Having work flow that scales out across hundreds of servers to meet the needs, the demanding needs of demanding business applications is critical, and what we've done is we've taken the .NET work flow services that are so familiar to you on the on-premises Windows systems, and taken those same services and put them into the cloud in Windows Azure and .NET services to allow you to write work flows that span from the on-premises system into the cloud environment.

Slide 44

Speaking Points: Let’s spend a couple minutes reviewing the high-level roadmap for Azure. Fall 2008 At the Professional Developers Conference in October last year we announced the Azure Services Platform.  We also released the very first CTP version of the SDKs, Tools, and services. These are CTP versions that are designed to allow you to build prototype applications. The CTP versions for the services are designed for developer use and we will not be charging for access to the services. Spring 2009 This spring, starting today with the Mix conference we are announcing several new features for Windows Azure including: Full trust support – which also enables native code support Fast CGI support – which will enable PHP applications Over the next few weeks we will also be rolling out Windows Azure into a couple data centers in North America and enabling you to select where you are using compute or storage. This week at Mix we will also change the Live Framework and .NET services to be an open CTP. This means that you will no longer need invitation tokens to access these services. Finally, in a few weeks we will start a limited, invitation only CTP for SQL Data Services. Existing SDS users will be giving priority access to the new service. Summer 2009 We anticipate providing specific pricing and SLA information later this summer. At the same time, SDS will move to being a public CTP – where a broader set of developers will have access. Fall 2009 Finally, our plans are to make the Azure Services Platform commercially available for the first time later this fall. The timeframe for commercial availability is primarily dependent on the feedback we receive over the next few months as developers – as you – begin to work with the services, SDKs, and Tools. We are currently aiming for Fall 2009 for commercial availability. By commercial availability, I mean that you could go live with an application that uses the Azure Services Platform and we will have SLAs for the services and start charging for their usage. In addition, we anticipate that we will have additional data centers online outside the US. Notes: Here is more detail if needed:     Fast CGI We will integrate IIS support for FastCGI which will allow customers to host websites built with most languages including PHP, Ruby, etc provided they include the relevant runtimes for these languages in the service package.  While this update will enable customers to deploy applications built with most programming languages, we are not explicitly including support for any particular language beyond ASP.NET in this update.   Full Trust Applications will run in full trust which will allow managed code to PInvoke native code, and invoke full trust modules such as the full WCF stack.  At this time, Windows Azure applications will continue to run in user mode, there will be no admin access in the VM.   Geo location At MIX, Windows Azure will be running in two locations in United States, US West and US MidWest.  Customers can specify a location for each of their compute apps or storage accounts, or leave it unspecified. Customers will also be able to group sets of compute applications and/or storage accounts. Once grouped they will be stored in the same cluster.   Are we committing to putting SQL Server within Windows Azure?   My impression was that this was an engineering discussion at this point, rather than a commitment? It is a commitment by PDC ’09. When do we expect to provide the “Raw” mode? Not in the plan for PDC ’09, we are in the early stages of developing the roadmap beyond this. When will we have a single, consolidated portal for managing the services and viewing usage and billing? By PDC ’09 we will have a billing and analytics story for Windows Azure. At this point we have not had any conversations regarding a single portal. Regarding what “refresh on a regular basis” means, our current POR is to release new features when they are ready.  

Slide 1

Microsoft Developer User Group - Hyderabad Windows Azure Platform Overview “ Sharing is our Passion “

Slide 2

Windows Azure Platform Overview Nithin Mohan T K Technology Specialist / Member Microsoft Developer UG – Hyderabad Blog… Mail…

Slide 3

Platform Continuum

Slide 4

Windows Azure Platform Compute: Virtualized compute environment based on Windows Server Storage: Durable, scalable, & available storage Management: Automated, model-driven management of the service Role : Operating System as a Service Database: Relational processing for structured/unstructured data Role : Relational Database as A Service Service Bus: General purpose application bus Access Control: Rules-driven, claims-based access control

Slide 5

It is an operating system for the cloud It is designed for utility computing It has four primary features: Automated service management A powerful service hosting environment Scalable, available cloud storage A rich, familiar developer experience What Is Windows Azure?

Slide 6

Investing in the Cloud OS Vendor Investments Vendors investing heavily in multi-site datacenters

Slide 7

Investing in the Cloud OS Microsoft Data Center (Chicago, IL) $500m investment, 500,000 sq ft, container based

Slide 8

A set of connected servers On which developers can: Install and run services Store and retrieve data The Cloud is…

Slide 9

It is an operating system for the cloud It is designed for utility computing It has four primary features: Service management Compute Storage Developer experience Windows Azure is…

Slide 10

Select your hardware, wire it all together Find some device drivers Write a file system Write a job scheduler Write an application installer … This would be a complete waste of time! Imagine Building A Desktop Application In This Way:

Slide 11

But This Is What Every Cloud Service Developer Has To Do Today! Datacenter

Slide 12

An application execution environment that abstracts away the hardware A shared file system with access control Resource allocation from a shared pool Support for powerful programming environments Inter-operability with other systems What's The Answer On The Desktop? An operating system:

Slide 13

What's Missing In The Cloud? An operating system for the cloud: …. Service 1 Service 2 Service N Service 3 ……

Slide 14

The same facilities that a desktop OS provides, but on a set of connected servers: Abstract execution environment Shared file system Resource allocation Programming environments And more: Utility computing 24/7 operation Pay for what you use Simpler, transparent administration What Should The Cloud OS Provide?

Slide 16

Automated service management You define the rules and provide your code The platform follows the rules: deploys, monitors, and manages your service A powerful service hosting environment All of the hardware: servers; load balancers; … Virtualized and direct execution Scalable, available cloud storage Blobs, tables, queues, … A rich, familiar developer experience How Is The Cloud OS Manifested?

Slide 17

Windows Azure Web Portal (API) LB LB DNS Your Service

Slide 18

Service Deployment Your Service Web Portal (API) Service Model Service Service DNS config

Slide 19

Deployment Later will Discuss it on Windows Azure Session

Slide 20

Service Scaling Your Service Web Portal (API) Service Service Service Model Service Service Service Service Service

Slide 21

Service Monitoring & Recovery Your Service Web Portal (API) Service Service Service Model ! Service

Slide 22

Roles Windows Server 2008 x64 IIS 7 ASP.NET 3.5 SP1 FastCGI – PHP Native Code Full Trust User Mode Windows Server 2008 x64 .NET Start Native Code User Mode Web Role Worker Role

Slide 23

Bid Now Service Service Models & Roles Web B (port 8081) Worker X Worker Y Worker Z Web A (port 80) Main Web 100 instances Admin 2 instances Image Resize 2 instances Auction Processing 25 instances Notifications 10 instances

Slide 24

Storage Table Entity Data Store Partitioned by key Unlimited keys Not a RDBMS Blob Blob Storage Partitioned by container Unlimited containers Queue Simple Queue Read at least once Delete to remove message, otherwise is returned to queue Partitioned by Queue Name

Slide 25

Partitions Partition = Table Partition or Container Not just about size More Partitions = More Nodes

Slide 26

Developer Experience Later will discuss on .NET Services

Slide 27

Pricing Compute $0.12 / CPU hour (or part thereof) ~ 1.7 GHz, 2GB Ram, Single Core $2.88 / Day $86.4 / 30 days (billing period) 2 instances = $172.80 / month Storage $0.15 / GB/Month Bandwidth $0.10 /GB inbound $0.15 /GB outbound

Slide 28

SQL Azure Initial Services Database – Core SQL Server database capabilities Future Services Data Sync – Enables the sync framework Additional SQL Server capabilities available as a service: Business Intelligence and Reporting New services: Reference Data and Secure Data Hub Database Reference Data Business Intelligence Reporting Data Sync

Slide 29

SQL Azure Deployment Web Portal (API) SQL Azure TDS DB Script

Slide 30

SQL Azure Accessing databases Web Portal (API) SQL Azure TDS Your App Change Connection String

Slide 31

SQL Azure Later will discuss on SQL Azure

Slide 32

Database Replicas Replica 1 Replica 2 Replica 3 DB Single Database Multiple Replicas Single Primary

Slide 33

Hardware Boundary Hardware Boundary Hardware Boundary Hardware Boundary Shared Environment B C D A A B B C C D D A

Slide 34

SQL Azure Database Monitoring & Recovery Web Portal (API) SQL Azure TDS Your App !

Slide 35

Pricing WEB Edition 1 GB Database $9.99 / month Bandwidth $0.10 /GB inbound $0.15 /GB outbound Business Edition 10GB Database $99.99 / month Bandwidth $0.10 /GB inbound $0.15 /GB outbound

Slide 36

Pricing Type specified by MAXSIZE on CREATE DATABASE command or portal (post-CTP1) Cannot switch between Web and Business Editions Monthly billing period

Slide 37

Sharding Databases 1 x 10GB database 1 Instances 10 x 1GB databases 10 Instances

Slide 38

Windows Azure Platform Benefits Windows Azure High Level of Abstraction Hardware Server OS Network Infrastructure Web Server Availability Automated Service Management Scalability Instance & Partitions Developer Experience Familiar Developer Tools SQL Azure Higher Level of Abstraction Hardware Server OS Network Infrastructure Database Server Availability Automated Database Management & Replication Scalability Databases Partitioning Developer Experience Familiar SQL Environment

Slide 39

.NET Services Service Bus: General purpose application bus Across organizational boundaries Access Control: Rules-driven, claims-based access control Service Bus Access Control Extending .NET to the cloud with Internet Scale Utility Services

Slide 40

New bottle. Old wine… Service Bus Access Control

Slide 41

Service Bus Securely connect applications Over the internet Across any network topology Across organizational boundaries Primary application patterns Eventing: Notify applications and/or devices Service Remoting: Securely project on-premises services out to the cloud Tunneling: App-to-app communication with NAT/Firewall traversal

Slide 42

Access Control Provides outsourcing of claims-based access control for REST web services Key capabilities: Usable from any platform Low friction way to onboard new clients Integrates with AD FS v2 Supports WRAP / SWT Enables simple delegation Used today by Service Bus and “Dallas”

Slide 43

Pricing & SLA $0.15 / 100k “transactions” Transaction: ACS Tokens Messages on Service bus Bandwidth $0.10 /GB inbound $0.15 /GB outbound

Slide 44

Azure Services Platform Roadmap

Slide 45

Microsoft Codename “Dallas” Information Services

Slide 46

Introducing “Dallas” Content Brokerage and Discovery platform Discover, Explore, and Use any type of content (blobs, structured, real-time web services) Tap into an ecosystem of global content providers Process & analyze data Empowers developers of all sizes Built on Windows Azure and SQL Azure

Slide 47

Commercial Launch Windows Azure Platform

Slide 48

Timeline CTP with launch feature set Now Jan Feb 1 Commercial platform Paid usage

Slide 49

Business Considerations Billing Consumption-based and subscription offers SLA Support 24/7 phone support; developer forums Microsoft Pinpoint Marketplace List & discover applications and services Global availability Datacenter options in USA, Europe, and Asia

Slide 50

Business Model Consumption-based billing model Compute: Rent a VM by the hour Database: Rent a DB by the month Storage: Pay per transaction & data stored All: Pay per data transfer Various subscription offers are available

Slide 51

Global Availability Platform availability 21 countries, 10 currencies, 5 languages 41 countries and 13 currencies in Mar 2010 Datacenter locations North Central US South Central US North Europe Southeast Asia

Slide 52

Summary The Windows Azure Platform consists of Windows Azure SQL Azure Windows Azure platform AppFabric The Windows Azure Platform is designed to Host business-critical applications Lower the total cost of ownership Provide comprehensive functionality Support inter-operability

Slide 53

Call To Action Go to Redeem your CTP tokens Free usage, with quotas, thru Feb 1 Download Windows Azure Platform Training Kit from

Slide 54

Q & A

Slide 55

Visit my blog @ Thank you all Visit our website

More by this User
Most Viewed