My main interest currently is business driven cloud adoption and from that perspective I addressed migration and modernization themes on the Serverless meetup 10.11.2022. From business requirements perspective, should everything be serverless?

1. Business driven cloud adoption
Serverless Meetup 10.11.2022 @ Solita
Dr. Tero Peltola | Cloud Advisor

3. How to reach
Agility to execute
with confidence
Take advantage of the knowledge,
experiences and best practices that have
been gathered from multi-domain
enterprise data capability development
initiatives over the years.
1.
2.
Leverage high level of automation,
purposely selected technologies and
modern ways-of-working to get things
done with a great pace and in a
impactful manner.
3.
Provide self-organized and proactive
team to work in close collaboration with
all stakeholders for continuous data
development and operations.

4. Brief history of migrations
World of Migrations
S
• From a business perspective, a good migration don’t
affect business continuity
• From a technical perspective, majority of the
migtations are Lift&Shifts
• Benefits based on cloud technologies when L&S?
• …many of those remain hidden.
• Such as cloud-native serverless solutions.
*Not in scale

5. Perceived Benefits
IT Modernizations
Improved Efficiency
Increased Data Security
Improved Productivity
Increased Agility and Innovation
* Adapted from Gartner

6. Cost Reduction?

7. Return of Investment
• The current state?
• All related costs.
• Migration project is not cheap.
• There will always be overlapping period.
• ROI positive not sooner than after 5+ years
 why bother?

8. Should migrations have a strategic
dimension?
• Strategic decision  long-term perceived returns,
not focusing only on tangible financial benefits.
• Application level decisions  short-term target,
decisionpoint align with application lifecycle.
• The battle between short-term costs and long-term
TCO is always in cloud migration business cases.
More: https://cloud.solita.fi/en/is-cloud-always-the-answer/

9. Reasoning for migration
DevOps
Mindset, culture, ways of working
Maximal automation, APIs
Global Presence
Ability to serve Customers and users
everywhere easily is built in.
Mobile & Web
Scalability, global reach
Ready building blocks
Datawarehouse & Analytics
Extracting value from data
Dev/Test Environments
Start/Stop, Scale up/down
Clone, redeploy
Developer autonomy
Disaster Recovery
Minimal costs during normal times -
ramp up & scale out if things hit the
fan.
Cost Transparency
Granular visibility to costs
Enforce ownership
Data Center Alternatives
Option for discontinuities.
Align with app’s lifecycle
* Adapted from Gartner “How to Build a Business Case for Migrating to Public Cloud IaaS” (2022)
New Infrastructure needs
No heavy initial investments
Scalability
IoT
Value creation based on sensor data

10. Migration strategies: the “R’s” of
Applications
VALUE
EFFORT
RETIRE = Decommission
RETAIN = Do nothing
REHOST = Lift & Shift
REPLATFORM = Lift & Reshape
REPURCHASE = Replace with SaaS
REFACTOR / REBUILD
(RELOCATE
skipped)

11. Serverless – because I can?
Trade-offs
serverless <–> on-prem
Level of control? Trust?
Logging, trails?
Expertise/ways of working?

12. Serverless – not because I can
Migrating on-prem application to cloud and
modernize it to serverless during the migration
project is a risk.
To bear the risk
>> Business need ?
>> Mitigation plan to address ’all’ risks.
Serverless – because I need

13. Serverless – justifying?
• Enable developers to focus their efforts on
delivering code
• Experimental approach
• Write off technical debt & staying up-to-
date
• Simplify the application (which might then
enable you to use high-productivity tools)
• Enable developers to utilize architectures
that are better-suited for the current
business requirements

14. How to “ryssiä”
• Lack of accurate data, vague initial state analysis.
• Not honest about the outcome, sugercoat results –>
Organization don’t buy it
• Leadership&vision missing; Too broad scope
• No ownership, business engagement missing
• Failure identifying the business case due to
• Erratic cloud cost calculations
• Over streching the lifespan of the onprem

15. How to
migrate
with
excellence

16. Holistic perspective to business driven cloud
adoption
Migration to cloud is more than
just technological update.
Exploring towards expected
benefits require holistic
perspective and change
management.
Multiple aspects are required in
cloud journey to have impact
that lasts.

17. Cloud Migration
Migration
Assessment
Applications &
Solutions
Prerequisite data
Servers &
Infrastructure
Technical and
Business
Dependencies
Migration
Obstacles (biz,
org, tech)
Initial Migration
Patterns
Initial Quick Wins
DISCOVER
Management
buy-in
PREPARE MIGRATE
Monitoring, Logs
& Security
Support &
Optimize
Guardrails &
Policies
Backups &
Continuity
KPI follow-up
Decommission
source VMs
Facilitation &
communication
Workload
cutover
Application
reconfiguration
Connectivity
reconfiguration
Migrate
User
acceptance
testing
CUTOVER
ROLLBACK
Troubleshooting
Migration Group
into staging area
(if required)
Establish CI/CD
pipelines and
code repository
Define metrics
Prepare and
premigrate
data(bases)
Prepare
Prepare cloud-
native services
Cloud
Foundation &
Landing Zones
“Migration
Engine” (tools
and stage)
Build
Post-migration
capabilities
Pilot Migration!
Go: Into Migration
Phase, for each
migration group.
No-Go: Back to Design
& Build
Connectivity and
IP design
Design
Migration Groups
& Patterns
Project plan &
schedule
Enterprise-scale
Landing Zones
Solution Design &
Right-sizing
Cloud
Governance
Current
application
partners & their
support
Expected
Business Benefit
Exit plan
Required expertise /
knowledge
Identifying the
optimal
organizational
structure
Current cost structure
possible new value
creation patterns
Valid
Business
Case
Cloud Strategy
Connection to Business case
Risk assessment and
mitigation plan
Current key people
and stakeholders &
their support
Business value,
drivers, and KPIs
Explore
Cost estimate /
estimated usage
after cloud migration

18. Key Elements of Success
Focus to holistic management:
Most complex part is managing
dependencies, stakeholders and
schedules. Lead the
transformation. Communicate.
Set the vantage point to
application perspective instead of
server perspective. Applications
are business enablers.
Automate everything. Build Infra
as a Code based solutions and
have them in version control.
Utilize support from cloud
vendor(s)
Engage your management.
Migration benefits from controlled
cloud adoption in all levels
Close cooperation leads to best
results. Ensure having relevant
combination of competence:
business, project management,
cloud, tech, database.

19. Thank You
Questions??