http://azure123.rocks/

Agenda• Why use the cloud to build apps?

• Virtual machines for lift-shift scenarios

• Microservices and Azure Service Fabric

• Data services in Azure

• DevOps solutions

t

Co

mp

ute

Inactivity

Period On and off

Unpredictable burstingt

Co

mp

ute

Growing fastt

Co

mp

ute

Predictable burstingt

Co

mp

ute

Your application portfolio—what does it look like?

S M T W T F S

Capacity needed (max+20%)

Save 20-30%

J F M A M J J A S O N D

Capacity needed (max+20%)

Save 60-80%

Individual applicationDev/test environment in the cloud

Application portfolioAll dev/test and production environments in the cloud

On and off (30%) Growing fast (15%) Unpredictable bursting (25%) Pred. bursting (20%) 24x7 steady

Your Data Center

SaaS(Software as

a Service)

Public Cloud Platforms

Can we STOP doingsome things?

Virtualization – there must be more..?

It’s cheaper – isn’t it..?

My DC is “constrained”..!

My Business Groups are using it..!

Physical

Virtual

?

Microsoft Enterprise Mobility + SecurityENTERPRISE MOBILITY

SAAS SOLUTIONS Microsoft Dynamics

Azure + Azure Stack + Operations Management SuiteCLOUD INFRASTRUCTURE

Visual Studio Family + Azure App ServiceDEVELOPER + APP PLATFORM

Cortana Analytics SuiteDATA + ANALYTICS

Azure IoT SuiteINTERNET OF THINGS

Microsoft Azure

Microsoft

Azure

Corporate

Network

Microsoft SQL

Server VM

Application

VM

Lift and Shift

Archive

Application

VM

Microsoft SQL Server

VM

PDF DOCX JPG VIDEO DB

Storage

key data inexpensively

Microsoft

SQL

Server

IIS

On-premises /

Hosting ServicesIIS/SQL Server Based

Web Apps

Web Apps - Take your web apps to the cloud using inexpensive App Service Web Apps

Microsoft

Azure

Non-IIS Open Source

Web Apps

Key Scenarios to get started with Azure

MySql

Key Scenarios to get started with AzureFull Dev/Test environments

Production

Staging

Dev/Test

Test branch

Master branch

Build

Visual Studio Team Services

GIT / TFS

Check

-in

Developers

Continually evolving applications

Faster delivery of features and capabilities to respond to customer expectations

Build and operate a service at scale

Why a microservicesapproach?

Plan1 Monitor + Learn

ReleaseDevelop + Test2

Development Production

4

3

• Scales by cloning the app on

multiple servers/VMs/Containers

Monolithic application approach Microservices application approach

• A microservice application

separates functionality

into separate smaller

services.

• Scales out by deploying each service

independently creating instances of these

services across servers/VMs/containers

• A monolith app contains

domain specific functionality

and is normally divided by

functional layers such as web,

business and data

App 1 App 2App 1

• Single monolithic database

• Tiers of specific technologies

State in Monolithic approach State in Microservices approach

• Graph of interconnected microservices

• State typically scoped to the microservice

• Variety of technologies used

• Remote Storage for cold data

stateless services with separate stores

statefulservices

stateless presentation services

stateless services

Azure Service FabricA platform for reliable, hyperscale, microservice-based applications

Service FabricHigh Availability

Hyper-Scale

Hybrid Operations

High Density

Microservices

Rolling Upgrades

Stateful Services

Low LatencyFast Startup &

Shutdown

Code Orchestration &

Lifecycle Management

Replication &

Failover

Simple

programming

modelsResource Management

Self-healingData Partitioning

Automated Rollback

Health

Monitoring

Placement

Constraints

Azure Private cloud Other clouds

Azure Cloud Services (Web and Worker Roles)

Azure Service Fabric(Stateless, stateful or Actor services)

• 1 role instance per VM

• Uneven utilization

• Low density

• Slow deployment & upgrade (bound to VM)

• Slow scaling and failure recovery

• Limited fault tolerance

• Many microservices per VM

• Even Utilization (by default, customizable)

• High density (customizable)

• Fast deployment & upgrade

• Fast scaling of independent microservices

• Tunable fast fault tolerance

Azure Cloud Services vs. Azure Service Fabric

fully managed, scalable, queryable, schemafree JSON

document database service for modern applications

transactional processing

rich query

managed as a service

elastic scale

internet accessible http/rest

schema-free data model

arbitrary data formats

Run any SQL product on cloud VM

Support for SQL Server, Oracle, MySql

Ready to go VM images available in Gallery

Persistent storage using attached disk in blob storage

Has all the benefits and powers of VMs combined with the full features of a SQL Engine

SQL IaaS

Azure Data WarehouseA relational data warehouse-as-a-service

App Service Azure SQL Database

Azure Machine LearningIntelligent App

Hadoop

Azure SQL DataWarehouse

Power BI

“Development

and Operations

collaboration”

What is DevOps?

The DevOpsconversation

PEOPLECollaborate more

Share common goals

Focus on improvement

BRINGING PEOPLE TOGETHER

PROCESSEliminate waste

Increase efficiency

Streamline feedback

DELIVERING VALUE FASTER

TOOLSEnhance productivity

Enable collaboration

Facilitate experimentation

EXECUTING A DEVOPS STRATEGY

PRACTICES

Automated Testing

Continuous Integration

Continuous Deployment

Release Management

PRACTICES

Usage Monitoring

Telemetry Collection

Testing in Production

Stakeholder Feedback

PRACTICES

Testing in Production

Usage Monitoring

User Telemetry

Stakeholder feedback

Feature flags

PRACTICES

Code Reviews

Automated Testing

Continuous Measurement

PRACTICES

Application Performance Management

Infrastructure as Code

Continuous Delivery

Release Management

Configuration Management

Automated Recovery

PRACTICES

Application Performance Management

Infrastructure as Code

Continuous Deployment

Release Management

Configuration Management

Automated Recovery

PRACTICES

Enterprise Agile

Continuous Integration

Continuous Deployment

Release Management

FLOW OF

CUSTOMER VALUE

TEAM

AUTONOMY

& ENTERPRISE

ALIGNMENT

BACKLOG refined

with LEARNING

EVIDENCE

gathered in

PRODUCTION

MANAGED

TECHNICAL

DEBT

PRODUCTION

FIRST MINDSET

INFRASTRUCTURE

is a FLEXIBLE

RESOURCE

DevOps habits and practices

Firms with high-performing IT organizations

were 2x as likely to exceed their profitability,

market share, and productivity goals

Strong IT performance is a competitive advantage

DevOps practicesimprove IT performance

Deploy code 30x faster

… and with 200x shorter lead time when

compared to lower-performing peers

Have 60x fewer failures… and recover from failure 168X faster when

compared to lower-performing peers

The DevOps cycle

2) Code Repository

1. Developers

3) Build 4) Test

5. Deploy to Cloud

6. Monitor and Improve

Contoso App

Azure

TFS

Develo

p Developer Workstation

Team Collaboration

Bu

ild &

Test Build/CI

Test

Dep

loy Release

Mo

nit

or

& L

earn Monitor

DevOps in the Microsoftecosystem

Workstations - On-Premises | Hybrid | Cloud Monitoring - On-Premises | Hybrid | CloudServices - On-Premises | Hybrid | Cloud

DEV TEST QA

Environments - On-Premises | Hybrid | Cloud