Vlad Vinogradsky vladvino@microsoft.com http://twitter.com/vladvino
Commercially available cloud platform offering Billing starts on 02/01/2010 A set of cloud computing services Services can be used together or independently Hosted in Microsoft datacenters Currently not available for on-premise deployment For business, consumer, and internal applications www.azure.com
Reduce costs Unknown or unpredictable demand Fluctuating demand Use capabilities Large scale compute and storage Global access World wide presence Automated management Out of the box availability Risk transfer
Microsoft Global Foundation Services (GFS) Datacenters - Integration Other cloud(s) AppFabric Apps Apps Apps Apps Apps Apps Windows Azure - Database SQL Azure - Compute - Storage - Management REST HTTP XML Client Apps (desktop, portable, handheld) On-premise (Enterprise) Apps
Service Deployment Package Hosted Service (App) Config Compute Fabric Storage
Public Internet HTTP(S) Web Role (n x m) HTTP(S) TCP Worker Role (k x l) Storage
Choice of guest operating systems and role instance sizes (CPU/memory/disk) Web Role Windows Server 2008 x64.net Framework 3.5 SP1 IIS 7 ASP.NET WebForms and MVC FastCGI (e.g. PHP, Java) HTTP and/or HTTPS endpoint Full trust Native code User mode Worker Role Windows Server 2008 x64.net Framework 3.5 SP1 HTTP(S) and/or TCP endpoints Full trust.net start Native Code User Mode
No Debugging in the cloud Debug locally using Development Fabric Instrument your application using Trace, Debug DiagnosticMonitorTraceListener Use Diagnostics API to Configure and Collect Event Logs Performance Counters Trace/Debug information (logging) IIS Logs, Failed Request Logs Crash Dumps or Arbitrary files Request data on demand or scheduled Transferred into your table and/or blob storage Everything is remotely configurable
Windows Azure portal Visual Studio tools Service project and roles Service configuration Role lifecycle Monitoring
Storage Account (up to 100TB of data) Blobs data items HTTP(S) REST API Tables service state Queues service comms Designed from scratch for the cloud Scalable capacity and throughput Available - total of 3 replicas Immediate consistency Accessible directly from the Internet Does not require compute Libraries for.net, PHP, etc.
Blobs mechanism for storing named files and associated metadata Tables place for structured data, containers of entities Queues reliable storage and delivery of messages between service roles Drives durable NTFS volumes for Windows Azure services (coming soon)
Blobs are stored in Containers Also can be stored at root level Hierarchical naming Two kinds of blobs Block optimized for streaming Page optimized for random read/write access One or more Containers per account Blobs and Containers have associated Metadata Name/Value pairs (8KB total) CRUD, snapshot, copy, lease (lock) Custom domain names and CDN Private or public Container and Blob access Shared Access Signatures Granular permissions for Blobs and Containers Encoded in blob and container URLs
Table is a set of Entities (rows) Entity can be up to 1MB in size No limit on number of tables or entities Entity is a set Properties (columns) Supported types - bool, int32/64, double, string, DateTime, Guid, byte[] Maximum of 255 Properties per Entity PertitionKey, RowKey, and Timestamp are mandatory Tables are automatically partitioned based on PartitionKey values Load balancing Query efficiency vs. scalability No limit on number of partitions Entities are uniquely identified by PartitionKey + RowKey Both are strings under 1KB Determine entities sort order (lexicographical) Not a relational database No schema, constraints, relations, stored procedures, triggers, etc. Optimistic concurrency, high availability, automatic load management, in partition transactions
Queues contain Messages Message size is up to 8KB Can have associated metadata No limit on number of Queues or Messages Limit for Message expiration Provide reliable message delivery Retrieved and processed at least once Dequeue with timeout Dequeue multiple messages Polling model
Tables, Blobs, Queues Development fabric Debugging in Development Fabric Deploying to the cloud
Data Center HTTP HTTP+REST TDS Highly scaled out relational database as a service 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 Windows Azure that use standard SQL client libraries 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 Instantly available Self-managing data center Automated maintenance Built in high-availability and data recoverability Browser Application Web App SQL Client * Windows Azure Application REST Client Cloud REST (Astoria) ADO.NET +EF TDS + TSQL Model SQL Azure Application SQL Client * * Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, ODBC, OLEDB, ADO.NET PHP, Ruby,
Account Server Database Each account has zero or more servers Azure wide, provisioned in a common portal Billing instrument Each server has one or more databases Contains metadata about the databases and usage Unit of authentication Unit of geo-location Generated DNS based name Each database has standard SQL objects Unit of consistency Contains Users, Tables, Views, Indices, etc. Most granular unit of billing
Databases under 10GB in size Use a single database Same model as on premise SQL Server Databases above 10GB in size Partition data across number of databases a.k.a. sharding Use parallel fan-out queries to fetch the data Application code must be partition aware v1 guidance, best practices for scale out post-v1 potentially provide and abstraction to hide some of the complexities of partitioning
SQL Server has many patterns for accomplishing tasks SQL Azure Database supports a subset of full SQL Server patterns Focus on logical and policy based administration Patterns work in both SQL Azure Database and 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 Create/Alter/Drop on Database/Index/View Stored Procedures (Transact-SQL) Triggers Constraints Table variables Session temp tables (#t) Out of Scope for v1 CLR Service Broker Distributed Transactions Distributed Query Spatial All server level DDL All physical DDL and physical catalog views
Just change the connection string * once database is migrated Generate script wizard from SSMS currently creates unsupported DDL SQL Server Management Studio 2008 R2 has increased support for SQL Azure Migrating Databases to SQL Azure HOL in the Windows Azure Platform Training Kit
SQL Server 2008 Management Studio Query window only Get s better in R2 SQL Server Integration Services Available in Developer and Trial editions Use ADO.NET endpoint BCP (bulk copy) is supported SQL Azure Migration Wizard Open source project Microsoft Sync Framework Power Pack for SQL Azure Nov 2009 CTP
SQL Azure portal Create database Setup firewall rule Use SSMS to create database objects Sample application using SQL Azure Data migration from SQL Server to SQL Azure Data sync between SQL Server and SQL Azure
Secure Connectivity Bridge cloud services, on-premises apps, and hosted assets Build distributed apps for your business or to collaborate with partners AppFabric SERVICE BUS Connect apps & services AppFabric ACCESS CONTROL Control & secure access Across boundaries Navigate network and security boundaries, securely and simply Federate identity and access across organizations and ID providers Simplify claims-based authorization for distributed apps and web services At Cloud Scale Scale up and down as your business requires Automated service mgmt. and dynamic scale Interoperate with a variety of languages and industry standards
Federated Identity and Access Control Service Registry Application Messaging Patterns Connectivity Fabric Connectivity Fabric lets you setup a comm link across boundaries NAT / firewall traversal Mobile & intermittently connected receivers Application Messaging features provide various ways to communicate across that link Bi-directional / peer-to-peer communication Cloud buffering web integration and message buffers Service Registry makes apps and services discoverable to each other Stable URIs for services Discovery supports Atom pub,
Text XML Graphics Binary Data Streaming Receive Receive Firewall Send Exchange messages between loosely coupled, composite applications. Send Application #1 Direct Connection facilitated by Service Bus if that is best Application #2 connection mechanism.
1. Define access control rules 6. Check for claims 0. Trust exchanged; secrets, certs Your Access Control Project 2. Send token (initial claims; e.g. identity) 3. Map input claims to output claims based on access control rules 4. Return token (output claims from 3) Your App (Relying Part) 5. Send token with request User (Application)
AppFabric portal WCF relayed binding NetTcp direct binding Message buffer using client library Message buffer using plain HTTP/REST
www.azure.com main portal www.msdn.com/azure - developer portal