How to migrate solutions to Azure? What to consider, what are the risks, which are the most easy to move solutions?

1. ITCamp Community Timișoara, 29 Oct

2. Migrating solutions to Microsoft Azure
ITCamp Community, Oct 2016
Mihai Tătăran

3. COMPLETE IT & TECH
ADVISORY SOLUTIONS
CONSULTING | SOFTWARE DEVELOPMENT | TECH SUPPORT | TRAINING

4. Mihai Tătăran
General Manager @ Avaelgo
Microsoft Gold Cloud Platform Partner
Training and consulting, Software development, Infrastructure
Microsoft Azure Most Valuable Professional
Co-founder @ ITCamp & ITCamp Community

5. Objective
Understand what are the first steps you need to consider when
migrating solutions to the Cloud
With examples on Microsoft Azure

6. Why the Cloud?
Cloud is just another term for hosting
IT guys are pragmatic, risk adverse people
Gap between the reality and perception
Moving to the Cloud is a strategic decision

7. 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

8. The Cloud is real and useful
Enterprises are starting the Cloud journey
Getting their feet wet
Understanding the model
Moving 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 )

9. Key migration scenarios
LIFT 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

10. Infrastructure as a Service
IaaS
Platform as a Service
PaaS
Cloud Services Web Apps
Containers
Service Fabric
Azure IaaS and PaaS spectrum

12. I have an app or a solution…
Is it modern or legacy?
Topology
Latency, performance
Security and compliance
Maintainability, DevOps
Lock in

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

14. 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 DB
Or any other services, e.g. Caching, Queues, etc.
Eager loading vs. Lazy Loading. Example: Entity Framework

15. Latency
The cloud is not near your desk
Expect 40-50 ms
With Azure Express Route: large bandwidth (up to 10 Gbps) and
small latency (bellow 10 ms)

16. Security
Workload isolation
App, network, data, etc.
VPN
Data is encrypted in transit and at rest; destroyed when deleted
Data stays in the geo zone you choose, e.g. EU
Identity via Azure AD, multi-factor
Role Based Access Control
Security Center: Prevent, detect, and respond to threats on your
Azure resources

18. 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, 27018
Microsoft is the first major cloud
provider to adopt the first international
code of practice for cloud privacy
Microsoft personnel restricted
access
We own the data, Microsoft is the
processor
https://www.microsoft.com/en-us/trustcenter/Compliance

19. Lock in
Different degrees of lock in
E.g.: Force.com PaaS
Azure, Hyper-V

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

21. Site Recovery – on premises to Azure
Designated VM is copied to Azure initially
Periodically refresh replica (30” – 15’)
Delta sync
Keep replicas (point in time) for multiple hours (24)
Application consistent snapshots
Low Recovery Time Objective (RTO) and Recovery Point Objective
(RPO)
PaaS instances in the background which manage and monitor the
replication settings
Network included (*)

22. Initial state

23. Failover

25. Hybrid
We don’t have to move an entire solution
VNET, VPN, Express Route, StorSimple
Operations Management Suite

26. 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

27. Conclusion
The Cloud is here
Moving to the Cloud is a strategic decision
But there are best practices and clear paths

28. Next steps
Avaelgo: https://avaelgo.ro/cloud-consulting/
https://vimeo.com/avaelgo
mihai.tataran@avaelgo.ro