1.Wisconsin .NET Users Group
Sept 2009

2. 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/
3. Cloud-Addressable Challenges
Facing Todays 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 limitreal estate, capacity, cooling and power
Matching capacity to demand
Maintaining security while increasing access and transparencywithin 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
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
5. 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
6. It has happened before
7. 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
8. 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
9. Introducing Windows AzureDelivering the Reality of Cloud Computing
Windows Azure delivers Cloud computing for the enterprise
Its the transformation of our software, its
the transformation of our strategy and our offerings across the board to fundamentally embrace services.
Ray Ozzie
Chief Software Architect
Microsoft
10. 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
11. NEXT UP:
Windows Azure Architecture
12. From Managing Resources to Providing Abstraction
BUSINESSES
CONSUMERS
INTERNET
13. 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.
14. Windows Azure
The Fabric Controller automates load balancing and computes resource scaling
Security and Control Featuresinclude 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.
15. Fabric Controller
Interacts with a Fabric Agent on each machine
Monitors every VM, application and instance
Performs load balancing, check pointing and recovery
16. 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
17. 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
18. 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 applicationmanaged 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
19. 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
20. Services Management in Windows Azure
GOAL:
AUTOMATED APPLICATION MANAGEMENT AND CONTROL
Fabric
The Fabric Controller automates service management
21. 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
22. Windows Azure Skill Transfer
23. Providing Security with Windows Azure
PHYSICAL:

Microsoft data centers with modern and current security processes

24. Redundant power supplies from separate providers, battery and diesel backup generators, climate control, and fire prevention and suppressionCONTINUITY:

Multiple data centers in different geographies

25. Users can choose single location or geo-distributed data centers 26. Storage data is replicated multiple times 27. Fabric is designed to be backed up and restored from checkpointsCOMPLIANCE & CERTIFICATION:

Microsoft is committed to complying with all local laws

28. Industry certification is a core part ofthe Windows Azure roadmap 29. Customers are ultimately responsible for the security and compliance of their services or applicationsWindows Azure is a platformLOGICAL:

Storage encryption and authentication

30. HTTPS 31. Optimized for Cloud access with no admin access to guests or applications 32. Applications and users not allowed to update the underlying environment