Moving wf applications to the cloud

Cai Zonghe / NCS Pte Ltdt: @caizonghee: caizonghe@gmail.comw: studiohub.wordpress.com

 Introduction to WF Context of WF in Azure Migration/development options Quick Dive Demo (Basic WF) Quick Dive Demo (Advanced WF) Partial Demo (Azure Composite Application)

 Long running processes ◦ Seconds / Minutes / Days / Months / Years ◦ System / Human ◦ Unreliable external world  Systems fail  People forget Complex processes ◦ Declarative representation of a process ◦ Easy to validate ◦ Increase maintainability

 Versions: ◦ .Net 3.0 / 3.5 – Sequence / State Machines ◦ .Net 4.0 – Sequence / Flowchart ◦ .Net 4.0 Update 1 – State Machines ◦ .Net 4.5 (Upcoming) – Contract First WF / Version Handling / C# Support Hosting ◦ Self Host – Windows Service / Exe ◦ IIS / WAS – [Windows Workflow Service Application]

 Handled by Batchjobs on premise ◦ Mainframe concept, batch window / duration ◦ “Free” ◦ BJ mapped to worker roles in Azure  Not feasible to spin up workers / effective polling  Responsible for framework level stuff  Multi-threading, lock management, etc  Recovery from errors  Monitoring

 WF is built to be used by multiple systems ◦ Simple process workflow / complex business processes ◦ Resource queuing / lock mangement etc ◦ Recovery from errors ◦ Monitoring (with AppFabric) Azure provides elastic scale Azure AppFabric Composite Application ◦ Monitoring ◦ Recovery

 Prerequisites ◦ Microsoft .Net 4.0 ◦ Microsoft .Net 4.0 Update 1 ◦ Azure SDK 1.6 (Nov) ◦ Azure AppFabric Tools (June CTP) ◦ Azure / AzureSQL / CompApp Accounts ◦ Persistence scripts  <WinDir>Microsoft.NETFrameworkv4.0.30319SQL en

 Current State ◦ On-Premise WF Application with on-premise DB  .Net 4.0 Sequence WF  .Net 4.0 Update 1 State Machine WF  Requires WF Persistence  Requires Custom Property Persistance  References external WCF / Web services  Requires ability to suspend/resume/terminate running workflows

 Cloud Option ◦ On-Premise WF Application with Azure SQL DB  Run Schema.sql (Run this to clear DB for dev purpose)  Run Logic.sql  - High Overhead to configure Firewalls / Security / Network  - High Latency

 Cloud Option ◦ Azure Web Role hosting WF Application

 Cloud Option ◦ Azure Web Accelerator Project  Using Web Deploy  X Unable to publish endpoint [ WIP ]

 Cloud Option ◦ Azure AppFabric Composite Application  Different approach to looking at application  No more handling ServiceModel Client configuration for endpoints  Uses a service locator pattern to register and resolve deployed applications  Applications can be dynamically redeployed to scale  Provides representation of how the various components work together.

 Cloud Option ◦ Azure AppFabric Composite Application  X CTP only  X Only if you can get an account  X A lot of configurations for Workflow

 Quick Dive Demo (Basic WF) ◦ Web App to place order via WF service ◦ WF Service records order ◦ WF Service checks inventory ◦ WF Service calls payment service ◦ WF Service calls shipping service ◦ WF Service waits for shipping update ◦ WF Service completes when item delivered

 Quick Dive Demo (Advanced WF) ◦ How WF persistence is done ◦ How WF custom property persistence is done ◦ How to recover from WF errors

 Partial Demo (Azure Composite Application)

Moving wf applications to the cloud

by Zonghe Cai on Nov 29, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Moving wf applications to the cloud — Presentation Transcript