migrating solutions to microsoft azure [mihai tataran]

28
ITCamp Community Timișoara, 29 Oct

Upload: itcamp

Post on 07-Jan-2017

49 views

Category:

Software


2 download

TRANSCRIPT

Page 1: Migrating solutions to microsoft azure [Mihai Tataran]

ITCamp Community Timișoara, 29 Oct

Page 2: Migrating solutions to microsoft azure [Mihai Tataran]

Migrating solutions to Microsoft AzureITCamp Community, Oct 2016

Mihai Tătăran

Page 3: Migrating solutions to microsoft azure [Mihai Tataran]

COMPLETE IT & TECHADVISORY SOLUTIONS

CONSULTING | SOFTWARE DEVELOPMENT | TECH SUPPORT | TRAINING

Page 4: Migrating solutions to microsoft azure [Mihai Tataran]

Mihai TătăranGeneral Manager @ Avaelgo

Microsoft Gold Cloud Platform PartnerTraining and consulting, Software development, Infrastructure

Microsoft Azure Most Valuable ProfessionalCo-founder @ ITCamp & ITCamp Community

Page 5: Migrating solutions to microsoft azure [Mihai Tataran]

Objective Understand what are the first steps you need to consider when migrating solutions to the Cloud

With examples on Microsoft Azure

Page 6: Migrating solutions to microsoft azure [Mihai Tataran]

Why the Cloud?Cloud is just another term for hostingIT guys are pragmatic, risk adverse peopleGap between the reality and perceptionMoving to the Cloud is a strategic decision

Page 7: Migrating solutions to microsoft azure [Mihai Tataran]

Why the Cloud?UTILITY COSTS LESS

EVEN IF IT COSTS MORE

• Higher cost per unit time than leasing or upfront purchase

• Zero cost when not used• Apples vs oranges

Our services are based on a real life experience and delivered as a practical step-by-step process.

THE PEAK OF THE SUM IS LESS THAN THE SUM OF

THE PEAKS

• Each company has its own peaks (April 15, May 25, Black Friday)

• A cloud provider reallocates resources across companies

ON-DEMAND IS BETTER THAN PREDICTION

• Forecasting is estimative, often wrong, sometimes impossible

• Better to be able to scale up or down “immediately” depending on demand

FIXED COSTS DISTRIBUTED OVER MORE UNITS OF

OUTPUT

• A large cloud provider has great economies of scale (volume purchasing, network bandwidth, operations, administration, etc.)

AGGREGATE DEMAND IS SMOOTHER

• Multiple customers with different demands smooths variation

REAL-TIME DECISION MAKING

• Decision making depends on complex computation (BI, risk analysis, etc.)

• Access to “unlimited” compute power over a short time period is priceless

Page 8: Migrating solutions to microsoft azure [Mihai Tataran]

The Cloud is real and usefulEnterprises are starting the Cloud journey

Getting their feet wetUnderstanding the modelMoving or preparing to move production workloads

By 2020, more compute power will have been sold by IaaS and PaaS cloud providers than sold and deployed into enterprise data centers (Gartner - http://www.gartner.com/newsroom/id/3354117 )Public Cloud market: $204 Billion in 2016 (Gartner - http://www.gartner.com/newsroom/id/3188817 )

Page 9: Migrating solutions to microsoft azure [Mihai Tataran]

Key migration scenariosLIFT AND SHIFT

• Take a workload from on premises and move it to the Cloud

• As close to 1:1 as possible

Our services are based on a real life experience and delivered as a practical step-by-step process.

ACCESS TO COMPUTE POWER

• Financial / insurance risk analysis

• 3D, CGI• Immense power for a short time

DEV/TEST

• Dev/Test environments, CI

MOVE APPLICATION TO PAAS

• Existing modern application• Migrated to PaaS• With potential changes

STARTUPS

• Liberalization of IT resources• Little upfront investment

Page 10: Migrating solutions to microsoft azure [Mihai Tataran]

Infrastructure as a ServiceIaaS

Platform as a ServicePaaS

Cloud Services Web AppsContainers

Service Fabric

Azure IaaS and PaaS spectrum

Page 11: Migrating solutions to microsoft azure [Mihai Tataran]
Page 12: Migrating solutions to microsoft azure [Mihai Tataran]

I have an app or a solution…Is it modern or legacy?TopologyLatency, performance Security and complianceMaintainability, DevOpsLock in

Page 13: Migrating solutions to microsoft azure [Mihai Tataran]

Modern or LegacyScalable, load balanced?Monolithic architecture?State What kind of state (in memory, files, etc.; serializable)?

Page 14: Migrating solutions to microsoft azure [Mihai Tataran]

Topology The topology in the Cloud will not match 1:1 the current topology Chatty applications / layers?Subnets with VPN?Example

App is no longer on the same machine as the DBOr any other services, e.g. Caching, Queues, etc.Eager loading vs. Lazy Loading. Example: Entity Framework

Page 15: Migrating solutions to microsoft azure [Mihai Tataran]

Latency The cloud is not near your deskExpect 40-50 msWith Azure Express Route: large bandwidth (up to 10 Gbps) and small latency (bellow 10 ms)

Page 16: Migrating solutions to microsoft azure [Mihai Tataran]

SecurityWorkload isolation

App, network, data, etc.VPNData is encrypted in transit and at rest; destroyed when deletedData stays in the geo zone you choose, e.g. EUIdentity via Azure AD, multi-factorRole Based Access ControlSecurity Center: Prevent, detect, and respond to threats on your Azure resources

Page 17: Migrating solutions to microsoft azure [Mihai Tataran]
Page 18: Migrating solutions to microsoft azure [Mihai Tataran]

Compliance EU Model Clauses

EU data protection law regulates the transfer of EU customer personal data to countries outside the European Economic Area

ISO/IEC 27017, 27018Microsoft is the first major cloud provider to adopt the first international code of practice for cloud privacy

Microsoft personnel restricted accessWe own the data, Microsoft is the processor https://www.microsoft.com/en-us/trustcenter/Compliance

Page 19: Migrating solutions to microsoft azure [Mihai Tataran]

Lock in Different degrees of lock inE.g.: Force.com PaaSAzure, Hyper-V

Page 20: Migrating solutions to microsoft azure [Mihai Tataran]

BCDR Use Azure as a failover site for your solutionAzure Site Recovery (or Azure Backup)Traffic Manager

Page 21: Migrating solutions to microsoft azure [Mihai Tataran]

Site Recovery – on premises to AzureDesignated VM is copied to Azure initiallyPeriodically refresh replica (30” – 15’)Delta syncKeep replicas (point in time) for multiple hours (24)Application consistent snapshotsLow Recovery Time Objective (RTO) and Recovery Point Objective (RPO)PaaS instances in the background which manage and monitor the replication settingsNetwork included (*)

Page 22: Migrating solutions to microsoft azure [Mihai Tataran]

Initial state

Page 23: Migrating solutions to microsoft azure [Mihai Tataran]

Failover

Page 24: Migrating solutions to microsoft azure [Mihai Tataran]
Page 25: Migrating solutions to microsoft azure [Mihai Tataran]

Hybrid We don’t have to move an entire solutionVNET, VPN, Express Route, StorSimpleOperations Management Suite

Page 26: Migrating solutions to microsoft azure [Mihai Tataran]

Microsoft Azure Stack

• Investments already made in private datacenters

• Regulations, compliance• System Center• Hosting providers

• Competition: OpenStack

• Azure and Azure Stack have a common architecture

• Same portal, same application model, same DevOps and dev

tools• Based on Azure Resource Manager

(ARM)

• The power of the cloud paradigm across corporate assets

• With minimal investments on customizing deployments

WHY HOWGOAL

Page 27: Migrating solutions to microsoft azure [Mihai Tataran]

Conclusion The Cloud is hereMoving to the Cloud is a strategic decisionBut there are best practices and clear paths

Page 28: Migrating solutions to microsoft azure [Mihai Tataran]

Next stepsAvaelgo: https://avaelgo.ro/cloud-consulting/https://vimeo.com/avaelgo [email protected]