Wisconsin .NET UG - Windows Azure
Upcoming SlideShare
Loading in...5
×
 

Wisconsin .NET UG - Windows Azure

on

  • 2,947 views

Presentation given to the Wisconsin .NET Users Group on Windows Azure and SQL Azure.

Presentation given to the Wisconsin .NET Users Group on Windows Azure and SQL Azure.

Statistics

Views

Total Views
2,947
Views on SlideShare
2,801
Embed Views
146

Actions

Likes
0
Downloads
68
Comments
0

8 Embeds 146

http://blog.wadewegner.com 93
http://www.wadewegner.com 40
http://www.linkedin.com 4
http://www.slideshare.net 3
http://www.docshut.com 3
http://www.architectingwith.net 1
http://cc.bingj.com 1
http://www.zoominfo.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Wisconsin .NET UG - Windows Azure Wisconsin .NET UG - Windows Azure Presentation Transcript

    • Wisconsin .NET Users Group
      Sept 2009
    • Who Are We?
      Joseph Paradi
      Innovation Lead, Accenture
      joseph.a.paradi@accenture.com
      Wade Wegner
      Architect Evangelist, Microsoft
      wade.wegner@microsoft.com
      http://blog.wadewegner.com/
    • Cloud-Addressable Challenges
      Facing Today’s Enterprise
      1
      1
      5
      Infrastructure costs are fixed and ongoing, and distract from the mission of reducing business process friction
      Leveraging past investments to provide future value
      Many data centers at limit—real estate, capacity, cooling and power
      Matching capacity to demand
      Maintaining security while increasing access and transparency—within and outside the organization
      2
      6
      Security, access, and transparency across the value chain: suppliers, partners, etc.
      3
      7
      Lack of a common platform
      4
    • And in a non-Cloud view, there are inefficiencies in addressing those issues
      Allocated IT-capacities
      Load Forecast
      “Under-supply“ of capacities
      “Waste“ of capacities
      Fixed cost of IT-capacities
      IT CAPACITY
      Barrier for
      innovations
      ActualLoad
      TIME
    • However, in a Cloud View
      Load Forecast
      Allocated IT capacities
      No “under-supply“
      IT CAPACITY
      Reduction of “over-supply“
      Possible reduction of IT-capacities in case of reduced load
      Reduction of initial investments
      ActualLoad
      Time
    • It has happened before
    • 5 key differences between legacy and cloud computing
      Scale
      Automated Service Management
      High Availability
      Multi-Tenancy
      Considerations
      Off Premises
      On Premises
      Location
      Homogeneous
      Heterogeneous
      Infrastructure
      CapEx
      OpEx
      Business model
      Own
      Lease/Rent
      Ownership
      Self
      Third Party
      Management
    • Introducing the Windows Azure platform
      Web and Clouds
      Developer Experience
      Third party Cloud
      Web applications
      Use existing skills and tools.
      Compute
      Storage
      Management
      Management
      Relational data
      Connectivity
      Access control
      On-premises
      LOB Applications
      Composite applications
    • Introducing Windows AzureDelivering the Reality of Cloud Computing
      Windows Azure delivers Cloud computing for the enterprise
      “It’s the transformation of our software, it’s
      the transformation of our strategy and our offerings across the board to fundamentally embrace services.”
      –Ray Ozzie
      Chief Software Architect
      Microsoft
    • Comprehensive SLAs
      Dependable performance
      Years of Microsoft Experience
      Faster time to market
      Speedier development
      Simpler deployment
      Efficiency
      Manage resources withless cost and effort
      Focus
      Concentrate on delivering solutions, not infrastructure
      Trust
      Rely on a solid development platform
      Agility
      Respond rapidly to changing needs
      Rapid monetization
      Scalability without complexity
      Fewer operational hurdles
      On-demand computing
      Elimination of idle IT capacity
      Lower TCO
      Why Windows Azure
    • NEXT UP:
      Windows Azure Architecture
    • From Managing Resources to Providing Abstraction
      BUSINESSES
      CONSUMERS
      INTERNET
    • Defining Windows Azure Architecture
      Fabric
      Fabric controller
      Compute
      Storage
      The Fabric Controller communicates with every server within the Fabric. It manages Windows Azure, monitors every application, decides where new applications should run – optimizing hardware utilization.
    • Windows Azure
      The Fabric Controller automates load balancing and computes resource scaling
      Security and Control Features include storage encryption, access authentication, and over-the-wire encryption using HTTPS. Industry certification is part of the Windows Azure roadmap.
      Computation provides application scalability. Developers can build a combination of web and worker roles. Those roles can be replicated as needed to scale the applications and computational processing power.
      Storage Services allow customers to scale to store large amounts of data – in any format – for any length of time, only paying for what they use or store.
      Geographically distributed, state-of-the-art data centers host your applications and data, internet-accessible from everywhere you choose to allow.
    • Fabric Controller
      Interacts with a “Fabric Agent” on each machine
      Monitors every VM, application and instance
      Performs load balancing, check pointing and recovery
    • Compute in Windows Azure
      GOAL:
      SCALABILITY
      Two instance types: Web Role & Worker Role
      Windows Azure applications are built with
      web role instances, worker role instances,
      or a combination of both.
      Scale out by replicating worker instances as needed.
      Allow applications to scale
      user and compute processing independently.
      Each instance runs on its own VM (virtual machine), replicated as needed
    • Defining the Web and Worker Roles
      WEB ROLE
      WORKER ROLE
      Interacts with end-user
      or web services
      Handles incoming
      HTTP/HTTPS requests
      Develop with Microsoft and
      non-Microsoft tools:
      ASP.NET, WCF, other .NET tools
      Java, PHP, etc.
      Does not accept
      incoming requests
      Initiates their own requests
      for data or tasks from
      the queue
      Similar to a "batch job"
      or Windows service
    • Storage in Windows Azure
      GOAL:
      SCALABLE, DURABLE STORAGE
      Tables: simply structured data, accessed using ADO.NET Data Services
      Queues: serially accessed messages or requests, allowing web-roles and worker-roles to interact
      Blobs: large, unstructured data (audio, video, etc)
      Windows Azure storage is an application managed by the Fabric Controller
      Windows Azure applications can use native storage or SQL Azure
      Application state is kept in storage services, so worker roles can replicate as needed
    • Blobs, Tables and Queues
      BLOBS:
      Provide a simple interface for storing named files along with file metadata
      QUEUES:
      Provide reliable storage and delivery of messages for
      an application
      TABLES:
      Provide structured storage. A Table is a set of entities which contain a set of properties
    • Services Management in Windows Azure
      GOAL:
      AUTOMATED APPLICATION MANAGEMENT AND CONTROL
      Fabric
      The Fabric Controller automates service management
    • Developing Applications for Windows Azure
      FAMILIAR DEVELOPER EXPERIENCE
      DESIGNED FOR INTEROPERABILITY
      PROVEN MICROSOFT TECHNOLOGIES
      Development: Visual Studio integration, offline Cloud simulation
      Maintenance: Local debugging, APIs for logging
      Management: APIs for configuration management
      SOAP and REST protocols
      XML file formats
      Commitment to support Java, PHP, Python and other popular programming languages
      Visual Studio, ASP.NET, SQL Azure integration
      Windows Azure integration
    • Windows Azure Skill Transfer
    • Providing Security with Windows Azure
      PHYSICAL:
      • Microsoft data centers with modern and current security processes
      • Redundant power supplies from separate providers, battery and diesel backup generators, climate control, and fire prevention and suppression
      CONTINUITY:
      • Multiple data centers in different geographies
      • Users can choose single location or geo-distributed data centers
      • Storage data is replicated multiple times
      • Fabric is designed to be backed up and restored from checkpoints
      COMPLIANCE & CERTIFICATION:
      • Microsoft is committed to complying with all local laws
      • Industry certification is a core part of the Windows Azure roadmap
      • Customers are ultimately responsible for the security and compliance of their services or applications–Windows Azure is a platform
      LOGICAL:
      • Storage encryption and authentication
      • HTTPS
      • Optimized for Cloud access with no admin access to guests or applications
      • Applications and users not allowed to update the underlying environment
    • Building Solutions with the
      Windows Azure Platform
      SQL Azure: Scalable, relational, Cloud-enabled database services
      .NET Services: Framework for access control and communication between Cloud-aware applications
    • NEXT UP:
      SQL Azure Architecture
    • Benefits of SQL Azure database
      SQL Azure Database delivers the value of hosted relational database with the differentiated benefits of a managed database as a utility
      Hosted RDBMS
      Managed RDBMS
      • SQL query processor
      • Familiar relational model (DDL, DML, Indexes…)
      • Transactions
      • Ecosystem of familiar development and management tools
      • Low-friction provisioning
      • High scale
      • Multi-tenant
      • Self-management
      • Automatic HA and DR
    • SQL Azure Database Product Architecture overview
      SQL Azure Database combines the bestof simple storage and hosted RDBMS
      BrowserApplication
      Application
      Application
      ODBC, OLEDB, ADO.Net PHP, Ruby, …
      • Flexible access to data in the cloud
      • Create client applications that access data in the cloud via TDS – just like on-premise SQL Server
      • Create cloud-based Web applications in Azure that use standard SQLClient libraries with ADO.NET
      • Create cloud-based REST data interfaces in Azure with ADO.NET Data Services and the Entity Framework
      • Low friction data storage provisioning
      • Web interface for simple, database provisioning
      • Scale seamlessly as needed
      • Self-managing data center
      • Automated maintenance
      • Built in high-availability and data recoverability
      REST Client
      SQL Client*
      Cloud
      REST (Astoria)
      ADO.Net +EF
      HTTP+REST
      HTTP
      TDS
      Windows Azure
      Web App
      SQL Client*
      Data Center
      TDS + TSQL Model
      SQL Azure
      * Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, …
    • Data Platform Design
      Account
      • Goal: A storage platform built for extreme scale and low cost
      • Architecture:
      • An Azure account provides access to SQL Azure
      • Each account can have one or more logical server
      • Implemented as multiple physical servers within a given geo-location
      • Each logical server can contain one or more logical database
      • Implemented as replicated partitioned data across multiple physical databases
      • Azure wide
      • Billing instrument
      Has one or more
      Server
      • Database metadata
      • Unit of authorization
      • Unit of geo-location
      Has one or more
      Database
      • Unit of consistency
      • Contains Users, Tables, Views, etc…
    • Logical User Databases
      • Uses shared infrastructure at SQL database and below
      • Each user database is replicated to one or more servers (configurable based on SLA)
      • Client requests are routed to current “primary server” for read and write operations (based on SQL session)
      • Security, lockdown and isolation enforced in SQL tier
      • Highly scalable and state-of-the-art HA technology
      • Automatic failure detection; client request re-routed to new primary on failure
      • High SLA guarantee using logical replication (hot standby replicas)
      • Automatic management, self-healing and load balancing across shared resource pool
      • SQL Azure Database provides provisioning, metering and billing infrastructure
      Machine 5
      Machine 6
      Machine 4
      SQL Instance
      SQL Instance
      SQL Instance
      SQL DB
      SQL DB
      SQL DB
      UserDB1
      UserDB2
      UserDB3
      UserDB4
      UserDB1
      UserDB2
      UserDB3
      UserDB4
      UserDB1
      UserDB2
      UserDB3
      UserDB4
      SQL Azure Database Provisioning (databases, accounts, roles, …, Metering, and Billing
      Scalability and Availability: Fabric, Failover, Replication, and Load balancing
      DBA role will change to focus on policy/logical management
      Scalability and Availability: Fabric, Failover, Replication, and Load balancing
    • Security and Connection Models
      Security
      • Uses regular SQL security model
      • Authenticate logins, map to users and roles
      • Authorize users and roles to SQL objects
      • Supports standard SQL logins
      • Logins are username + password strings
      • Service enforces use of SSL to secure credentials
      • Future support for AD Federation, WLID, etc as alternate authentication protocols
      Connections
      • Connect using common client libraries
      • ADO.NET, OLE DB, ODBC, etc.
      • Clients connect to a database directly
      • Cannot hop across DBs
      • Large surface of SQL supported within the database boundary
      • Future work will relax many of these constraints
    • Provisioning Model
      • Account and server provisioning
      • Portal and API based access
      • Ex: enumerate my servers, show server usage metrics, etc
      • Each account has one or more servers
      • Ex: srv123.data.database.windows.net
      • Each server has a virtual master database
      • Has subset of SQL Server master DB interface
      • Each server has one or more SQL logins
      • System creates sysadmin login on “server creation”
      • Databases created using “CREATE DATABASE”
      • Can be called by sysadmin or anyone with create DB permission
      *
      *
    • Compatibility with SQL Server
      • SQL Server has many patterns for accomplishing tasks
      • SQL Azure supports a subset of SQL Server patterns
      • Focus on logical and policy based administration
      • Patterns work in both SQL Azure & SQL Server
      • Enables migration of on-premise application to/from SQL Azure
      • SQL Azure Database is a multi-tenant service
      • Throttling and load balancing policies
      • Examples: limit on DB size, duration of transaction, …
      V1 Goal: Address the needs of 95% or more web and departmental applications
      In Scope for v1
      Out of Scope for v1
      • CLR
      • Service Broker
      • Distributed Transactions
      • Distributed Query
      • Spatial
      • All server level DDL
      • All physical DDL and physical catalog views
      • Create/Alter/Drop on Database/Index/View
      • Stored Procedures (Transact-SQL)
      • Triggers
      • Constraints
      • Table variables, session temp tables (#t)
      • + lots of others
    • SQL Azure Database Customer Scenarios
      Departmental Applications
      Web Applications
      Departmental workgroup applications with low concurrency and cyclical usage patterns
      Small customers or start ups with Web applications of all scale that have simple RDBMS needs
      Data Hubs
      ISV/SaaS Offerings
      Secure data hubs that consolidate multiple data sources and enable access from multiple locations and devices
      Traditional ISVs extending offering or selling software hosted in the cloud (including SaaS ISVs)
    • SQL Data Services Roadmap
      Internal Adoption
      Invitation SQL Azure CTP
      Commercial Availability
      Invitation Azure CTP
      MIX 2009
      WWPC 2009
      TechEd 2009
      PDC
      2009
      Mar 09
      May 09
      Jul 09
      Nov 09
      Sep 09
      Apr 09
      Jun 09
      Aug 09
      Oct 09
    • Key Takeaways
      • SQL Azure Database is real and in production with Microsoft enterprise services
      • We are accelerating delivery of relational database service – PDC ‘09
      • Ecosystem of tools; existing skills and knowledge
      • Majority of web and workgroup apps work as-is
      • Support for open source client libraries
      • Integration between on/off-premises: Extending SQL data platform to the cloud
      • Relational database is key capability of the Windows Azure Platform
      • Zero-friction integration with Windows Azure
      • Enables compelling scenarios on the Azure platform
      • SQL Azure design and architecture supports a wide range of scenarios
      • SQL Azure Database platform investments deliver proven value on top of SQL engine
      • From very cheap and highly-consolidated to still inexpensive and highly-isolated
    • Software + Services Architecture
      “When you combine the ever-growing power of devices and the increasing ubiquity of the Web, you come up with a sum that is greater than its parts.”
      —RAY OZZIE
      THREE CORE PRINCIPLES:
      Experiences should span beyond a single device
      Infrastructure and solutions should extend from the server to the Cloud
      Tightly coupled systems should give way to federations of cooperating systems and loosely coupled compositions
    • NEXT UP:
      Pricing
    • Consumption
      Subscription
      Volume licensing
      “Value for a commitment”
      “Coordinated purchasing”
      “Pay as you go and grow”
      Planned for post PDC
      Select offers at PDC
      Available at PDC launch
      • Discounts for commitment
      • Plans for paymentpredictability
      • Unified purchasing through EA
      • Introduction to volumediscount
      • Low barrier to entry and flexibility
      • Optimized for Cloudelasticity
      Windows Azure Purchasing Models
    • Windows Azure Pricing Meters
      COMPUTE
      STORAGE
      BANDWIDTH
      Virtual Machine instances
      Load balancers, routers, etc.
      Relational DB instances
      Automated service management
      • Fabric controller operations (deploy/upgrade/delete/scale)
      • Load balancer programming
      Blob Storage
      Table Storage
      Multiple replicas
      Ingress/Egress (to/from internet only)
      PRICE
      $0.12 / hour
      PRICE
      $0.15 / GB stored / month
      Storage transactions: $0.01 / 10k
      PRICE
      Bandwidth: $0.10 IN; $0.15 OUT; / GB
    • Windows Azure Platform Service Guarantee
      Storage servicewill be available/ reachable (connectivity)
      Your storage requests willbe processed successfully
      .NET Service Bus endpoint willhave external connectivity
      Message operation requests willbe processed successfully
      Serviceavailability
      Storage availability
      Database availability
      Role instance monitoring and restart
      Compute connectivity
      Your service is connected and reachable via web
      Internet facing roles will have external connectivity
      Database is connected to the internet gateway
      Availability monitoring every 5-minute interval
      All runningroles will be continuously monitored
      If role is unhealthy, we will detect and initiate corrective state
      Automated Systems Management
      >99.9%
      >99.95%
      >99.9%
      >99.9%
    • Windows Azure Platform Roadmap
      Rich Service Templates
      Multiple Geo Locations
      Multiple Languages
      Full Trust
      Active Directory and Web ID
      Relational & Virtualized Database
      Auto DB Management
      Simple Service Templates
      One Geo
      ASP.NET
      Medium Trust
      Automated service management
      Service Bus, Access Control
      Admin Mode/VM Deployment
      Geo Replication
      Systems Center Integration
      Enterprise ID Federation
      Distributed Queries & CLR
      Analytics & reporting
      Data Synch (DataHub)
      CTP
      Future
      Commercial release
    • Technology
      innovation
      Partner
      ecosystem
      Power
      of choice
      Developer
      Why Microsoft
      “IDC sees the launch of Windows Azure and Windows Azure platform as a first step in a long evolutionary path that customers will take moving them from today’s self-hosted IT to consuming a hybrid of both internally and externally hosted services, and if so desired, could eventually support a fully outsourced model.”
      —IDC Insight, Microsoft Unveils Cloud Services Strategy and the Windows Azure platform:
      Managing Customer Expectations and Competitive Pressures as Solution Evolves Is Key, Nov 2008, Doc #215034
    • NEXT STEPS
      Sign up for Windows Azure and SQL Azure:
      http://www.windowsazure.com
      http://msdn.microsoft.com/en-us/sqlserver/dataservices/
      Take a look at:
      Windows Azure & SQL Azure access
      Developer tools
      White papers
      Sample applications