Cloud Deployment Strategies

By admin123
Deployment Strategies & Release Models
Lesson 2 · Rollout

Deployment Strategies & Release Models

Getting cloud services running is only half the job — getting new versions out to users without breaking anything is the other half. From aligning with business goals to choosing how traffic shifts to a new release.

2.15

Deployment Strategies

The most successful cloud deployments align with business goals — gathered and documented before migration, with the whole organization involved in planning. Users and the business itself tend to care about different things.

Familiar, simple interface
Functionality
Support
Performance & reliability
Cost (CapEx / OpEx)
Integration
Compliance
Support
Scalability
Both groups list security as a shared concern.

Cloud-first

All new applications and services must at least be considered for cloud hosting before anything else is decided.

Cloud-only

A different (and mistaken) idea — not every service is a cloud candidate. Legacy applications especially may not fit.

Tap — don't confuse these two
2.16

Separate IT Environments

Production stays isolated from development through a chain of environments, each needing a different level of resources. Tap a stage to see what happens there.

Development
PaaS + IaaS
→
Staging / QA
IaaS
→
Production
Live traffic
Development — where programmers code, detect bugs, manage versions, and implement code-level security. Often combines PaaS for the actual development work with IaaS for testing.
2.17 – 2.21

Application Release Models

Four common strategies control how a new release actually reaches users. Pick one, then run the deploy to see how traffic shifts from the old version to the new one.

Blue-Green Deployment
Two identical environments exist — only one serves production at a time. The idle one stages the next release. After QA passes, all traffic switches at once, aiming for zero downtime with a hot standby ready for instant rollback.
● OLD VERSION100% / 0%NEW VERSION ●
Idle — click run to simulate this release strategy.
§ 2.15–2.21 · Deployment Strategies & Release Models