19
Building Apps with IaaS and PaaS Name Title Organization

Building Apps with IaaS and PaaS Name Title Organization

Embed Size (px)

Citation preview

Page 1: Building Apps with IaaS and PaaS Name Title Organization

Building Apps with IaaS and PaaS

NameTitleOrganization

Page 2: Building Apps with IaaS and PaaS Name Title Organization

Agenda

IaaS and PaaS

Application Patterns

Mixed Apps as a Migration Path

Page 3: Building Apps with IaaS and PaaS Name Title Organization

Why Mix Models?

What Value does this Provide? Unblocks Development or Migration of new applications that have dependencies on resources that require virtual machines such as Active Directory, MongoDB, MySQL, SharePoint, SQL Server, COM+, MSMQ etc…

Migration On-Ramp for Existing ApplicationsAdministrators can quickly take advantage of Windows Azure by migrating an existing application as-is using virtual machines. If desired, connecting different application models such as websites or web and worker roles provides the capability to take advantage of PaaS roles alongside IaaS roles.

Page 4: Building Apps with IaaS and PaaS Name Title Organization

Cloud Service

Windows Azure Service Model Example cloud service configuration with a single web role and a single worker role

VM1 VM2

VM5 VM6

VM9

VM3 VM4

VM7 VM8

VMn

VM1 VM2

VM5

VM3 VM4

VMn

Page 5: Building Apps with IaaS and PaaS Name Title Organization

Cloud Service 2

Mixing Virtual Machines and Stateless RolesMultiple cloud services with stateless and virtual machines

Cloud Service 1

VM1 VM2

VM5 VM6

VMn

VM1 VM1

VM1 VM2

VM5 VM6

VMn

Page 6: Building Apps with IaaS and PaaS Name Title Organization

Application Patterns

Page 7: Building Apps with IaaS and PaaS Name Title Organization

Connecting Cloud Services via VIPs

StrengthsSimplicityTenant AutonomyVIP Swap (stateless roles)Easy Local Dev/TestPersistent Service is Easily Accessible (even from other services!)

SQL Data Access Traffic

Through Public Endpoint

WeaknessesHigher LatencyLess SecureManagement/Deployment Overhead

WA Web Role

Cloud Service 1

Cloud Service 2

SQL Server

Load Balancer

80

2001-1433

Secure Endpoints with Windows Server Firewall

Load Balancer

Page 8: Building Apps with IaaS and PaaS Name Title Organization

Deployment Steps (VIP Connectivity)

Deploy Virtual Machine(s)

Use RDP to customize the new virtual machine(s) by installing software, configuring roles etc.

Build and test locally using the emulator. Testing live can be achieved by using public endpoints.

Specify instance count and other configuration details. Deploy to a separate hosted service.

Configure public endpoints to virtual machine services. ACL with firewall as appropriate.

Page 9: Building Apps with IaaS and PaaS Name Title Organization

Connecting Cloud Services with VNET

StrengthsMore SecureLow LatencyCloud App AutonomyVIP Swap (stateless roles)Advanced Connectivity Requirements

WeaknessesVNET ComplexityNo iDNS – use BYOD

Direct Access

via VNET

FrontEndSubnet

(10.0.0.0/16)

SQLSubnet (10.1.0.0/16)

Load Balancer

80

WA Web Role

Cloud Service1

Cloud Service 2

AD

SQL Mirror

AD Subnet

(10.2.0.0/16)

ContosoVNet (10.0.0.0/8)

Page 10: Building Apps with IaaS and PaaS Name Title Organization

Direct Access

via VNET

FrontEndSubnet

(10.0.0.0/16)

SQLSubnet (10.1.0.0/16)

Load Balancer

80

WA Web Role

AD

VNET Connected – Local Testing

Manage Multiple Connection Strings via Multiple Configurations

Developer Fabric

ContosoVNet (10.0.0.0/8) MyAffinityGroup

SQL Mirror

AD Subnet(10.2.0.0/16)

1433WA Developer

Fabric Developer

Cloud Service1

Cloud Service 2

Page 11: Building Apps with IaaS and PaaS Name Title Organization

VNET Connected with VPNContosoVNet (10.0.0.0/8) MyAffinityGroup

AD / DNS

VPN Tunnel

• Access on premises resources• Local Testing - allows direct connection

to Virtual Machines in the cloud

Direct Access

via VNET

FrontEndSubnet

(10.0.0.0/16)

SQLSubnet (10.1.0.0/16)

AD

Load Balancer

80

WA Web Role

SQL Mirror

On Premises

WA Developer Fabric

Developer

Cloud Service 1

Cloud Service 2

Page 12: Building Apps with IaaS and PaaS Name Title Organization

VNET Connected Deployment Steps

Deploy Virtual Machine(s). If AD is desired deploy at this stage so remaining VMs can start domain joined.

Use RDP to customize the new persistent VM(s) by installing software, configuring roles etc…

Build and test locally using the emulator. Testing live can be achieved by using public endpoints or VPN connectivity.

Specify instance count, virtual network settings and other configuration details. Deploy to a separate hosted service.

If previously opened, close public endpoints to lock down service.

Define virtual networks and subnets for hosted services to reside in.

Page 13: Building Apps with IaaS and PaaS Name Title Organization

Mixed Mode – Shared Cloud ServiceStrengthsSimplicityConnectivityiDNS

WA Web Role

Virtual Machine

Load Balance

r

80

Cloud App

Available in Fall Release

WeaknessesLack of VIP Swap

Page 14: Building Apps with IaaS and PaaS Name Title Organization

VM to VM Performance

Category Latency (Round-Trip)

Comment Network Link Details

Inter-VM within a deployment (or deployment to deployment with VNET)

0.29 msDIP

to DIP

Traffic does not flow through the

LB

Inter-VM crossing a deployment (same region)

0.88 ms VIP to VIP

Traffic flows through the LB

Page 15: Building Apps with IaaS and PaaS Name Title Organization

Tiered Migrations

Page 16: Building Apps with IaaS and PaaS Name Title Organization

Taking Advantage of PaaSTake Advantage Where You CanMany Applications could benefit from migrating to a mixed deployment. Migrating to web/worker roles or taking advantage of other Windows Azure services (storage, cache etc..)

Benefits of Web and Worker RolesSimplified Deployment and ConfigurationHealth ModelEasy High AvailabilityInstance ScalabilityOS PatchingAutomatic Firewall ConfigurationSimple Certificate DeploymentMany others

Page 17: Building Apps with IaaS and PaaS Name Title Organization

Horizontal Migration

Use Virtual Machines and VNET for Forklift Migration

Web Tier

App Tier

AD

Data Tier

Convert Web Apps to Web Roles (optional)

Web Role

Worker Roles

SQL Azure

Convert App Logic to Worker Roles (optional)Convert Data Tier to Azure SQL DB (optional)

Page 18: Building Apps with IaaS and PaaS Name Title Organization

Wrap UpConnecting IaaS and PaaSConnecting an application hosted in Windows Azure such as Web Sites or Web/Worker Roles with a Virtual Machine.

Unblocks Building Applications with DependenciesDependencies such as Active Directory, SharePoint, SQL Server, Linux, Mongo DB, COM+, MSMQ etc…

Migration On-Ramp for Existing ApplicationsMigrate application from on-premises take advantage of PaaS efficiencies without blockers on dependencies.

Page 19: Building Apps with IaaS and PaaS Name Title Organization

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.