Put your existing application on Windows Azure Maarten Balliauw Technical Consultant
About me Maarten Balliauw Antwerp, Belgium Focus on web ASP.NET, ASP.NET MVC, PHP, Azure, VSTS, … MVP ASP.NET
Agenda Windows Azure An existing application with some problems Windows Azure SQL Azure Blob storage AppFabric service bus What to remember? Resources Q&A
Windows Azure
Definition of cloud (NIST) On-demand self service Standardized access Location independant resource pooling Rapid elasticity Pay per use
IT as a Service Private(On-Premise)Infrastructure (as a Service) Platform Storage Server HW Networking Servers Databases Virtualization Runtimes Applications Security & Integration Storage Server HW Networking Servers Databases Virtualization Runtimes Applications Security & Integration Storage Server HW Networking Servers Databases Virtualization Runtimes Applications Security & Integration You manage Managed by vendor You manage
The Windows Azure Platform Windows Azure SQL Azure Windows Azure platform AppFabric Microsoft Codename “Dallas” Microsoft Codename “Sydney”
Windows Azure Flexible application hosting Lights-out service management Provide code & service model, hit ENTER Storage at massive scale Blobs, tables, queues
Windows Azure
Storage options Blobs, tables, queues Windows Azure Drive (a.k.a. XDrive) Virtual NTFS volume that can be mounted.vhd format Use existing NTFS API’s Easier migration Stored on blob storage provides quick mount/unmount in other VM
SQL Azure Relational database as a service Highly available, automatically maintained Extension of the SQL Server Data Platform
SQL Azure Relational database, provided as a service Highly symmetrical development and tooling experience (use TDS protocol and T-SQL) Highly scaled out, on commodity hardware Built on the SQL Server technology foundation High availability, DB provisioning, and DB management are provided by the service
Windows Azure AppFabric Secure connections between services Across organizational boundaries Claims-based access control
Service Bus Overview
Windows Azure AppFabric - Service Bus Securely connect applications Over the internet Across any network topology (= across firewalls!) 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
Microsoft Codename “Dallas” Content brokerage and discovery platform Available as a CTP
Microsoft Codename “Sydney” - Connectivity
An existing application
Time Tracker Originated from the ASP.NET starter kit Small modifications: List of projects from internal billing system Time registration can have an attachment
TimeTracker – On-premise
Time Tracker There are some problems with it... Running on 2 web servers that are > 2 years old, nearing EOL Looking to buy new hardware Looking to deploy the application in a cloud Spikes near the end of each month, reducing performance Looking to buy additional hardware Looking to deploy the application in the cloud They do have this “seamless scaling” thing, right?
Workload Patterns Optimal for Cloud Usage Compute Time Average Inactivity Period “On and Off “ On & off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome Compute Time “Unpredictable Bursting“ Average Usage Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases Average Usage Compute Time “Growing Fast“ Successful services needs to grow/scale Keeping up w/ growth is big IT challenge Complex lead time for deployment Compute Time Average Usage “Predictable Bursting“ Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity
Challenges Security? Forms based Claims based (AppFabric access control service) Availability & scalability out-of-the-box Still keep session state in mind Specify “upgrade domains” Logging & tracing System.Diagnostics.Trace Performance counters All stored on blob storage, not real-time! Operating system Windows Azure Cloud OS 1.0 – 1.1 – x.x See MSDN for patches and hotfixes in each OS version New cost model Pay-per-use Allow for scale-up and scale-down
Moving an application to the cloud Assess application Is it suitable?Is it suitable? Architecture?Architecture? Functionals?Functionals? Non- functionals?Non- functionals? Are there good reasons?Are there good reasons?Incompatible Most applications are not 100% compatibleMost applications are not 100% compatibleCloud It runs!It runs! Cloud optimized It runs!It runs! Many instancesMany instances Auto-scalingAuto-scaling ReliableReliable Cost-effectiveCost-effective MonitoredMonitored Self-awareSelf-aware refactoring
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
Support deployment on Windows Azure Convert the TimeTracker solution to a Cloud Service solution Make sure it can be packaged for deployment Make sure it runs on Development Fabric Requirements: IIS7 Visual Studio Windows Azure Tools for Microsoft Visual Studio Windows Azure SDK (shipped with the above)
Windows Azure Tools for Microsoft Visual Studio Get them on
Converting the TimeTracker solution
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
Store data in SQL Azure There is a database on-premise in SQL Server Schema should be migrated Data should be migrated Requirements: Native SQL client SQL Management Studio
Migrating schema and data SQL Azure Migration Wizard SQL Azure Data Sync Tool for SQL Server SQL Server Management Studio 2008 R2 November Community Technology Preview
Migrating data to SQL Azure Synchronizing SQL and SQL Azure
ASP.NET Membership & Roles Will not work out of the box! Some incompatible SQL Updated scripts and aspnet_regqslazure.exe
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
Store attachments on blob storage Attachments currently stored on the web server Windows Azure server storage not guaranteed to survive There’s an option for that......but it will still fail in some situations Ideal candidate: blob storage Requirements: Windows Azure SDK A tool to browse storage and see if it works
Tools to see if it works CloudBerryLab Explorer Azure Storage Explorer Online Visual Studio 2010 tools
Storing attachments on Windows Azure blob storage
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
Connect with the billing system List of projects comes from on-premise billing system TimeTracker will be in the cloud Requirements: Expose the billing system to the Internet Connect to it
Service Bus Overview
Connect with the billing system List of projects comes from on-premise billing system TimeTracker will be in the cloud Communication will happen over the AppFabric service bus Requirements: Visual Studio AppFabric SDK
Using AppFabric service bus
Another option… Billing system WCF configuration was changed If that’s not possible: PortBridge to the rescue!
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
Package up the application Deploy the thing Requirements: Windows Azure SDK A web browser
Windows Azure Platform Benefits for MSDN Subscribers MSDN Subscriber Benefits 750 Hours 8 Months 10 GB Storage SQL Azure Web Edition Details at
Deploying TimeTracker
TimeTracker on steroids! Our company decided to go for Windows Azure New migration track started Learn about Windows Azure Support deployment on Windows Azure Store data in SQL Azure Store attachments on blob storage Somehow connect with the billing system to get a list of project names Deploy
What to remember? Windows Azure is Operating system (computing & storage) SQL Azure AppFabric Your application and skills Hybrid applications are possible It’s not that hard to do
Resources Websites Windows Azure Local MSDN Local TechNet Blogs Steve Marx Clemens Vasters Simon Guest My blog Videos and presentations PDC RealDolmen blogs is running on Azure!
Questions? Possibly Answers
THANK YOU! Maarten Balliauw