The document discusses strategies for migrating enterprise Java applications to Microsoft Azure, addressing the factors to consider, including business and technical aspects. It emphasizes various cloud migration options, such as lift and shift versus modernization, along with the pros and cons of each approach. The speaker encourages engagement and exploration of Azure's capabilities tailored for Java applications.

1. Sponsored talk: Please touch that dial!
Enterprise Java on Azure, from PaaS to IaaS
and everything in between
Ed Burns
@edburns@mastodon.social
Principal Architect
2023-03-22

2. My plan for
your time
investment
 Where are you starting?
 Factors to consider
 The settings on the dial
 The tradeoffs for the settings
 Summary and call to action

3. Professional Biography
 Client
 NCSA Mosaic (1994)
 SGI Cosmo Web Authoring
 Sun Netscape 6 OJI
• Server
• J2EE JSF (2002)
• Oracle Java EE
Servlet, JSF, Bean Validation, etc
Microsoft Azure Cloud (2019)
Books

4. Explaining the title
• There once was a device called a
“television”
• The content was delivered via
“channels”
• You could change
channels by turning a
dial
• Content producers would say “don’t
touch that dial” to try to keep you
engaged with the current channel
Source: Amazon.com: Don't Touch That Dial

5. Where are you
starting?

7. Starting your cloud journey
 Lift and shift and leave it
 Lift and shift and then modernize
 Modernize first and then go to cloud
 Start from scratch with cloud native

8. Container
Platform
Managed orchestrator.
Configure, secure &
automate container running
Agility High autonomy, rapid iterations
Low manual maintenance
Manual deployment, seasonal releases
High touch intervention & maintenance
Debt
Recovered
Paying
Interest
Investing
in
outcomes
On-prem
Own hardware,
manage full stack
IaaS
Manage & patch OS,
Middleware, backups,
dependencies, apps & data
PaaS
Develop & manage apps +
data against defined
capabilities
SaaS
(incl. Low code)
Compose apps processes,
data & workflows
Retain
Rehost
Rearchitect
Rearchitect
Refactor Rewrite
Rewrite
Replace
Replace
Replace
Retire
Migrating Java applications to the cloud

9. Migrate and Modernize your Java apps
Productivity
Control
Infrastructure-as-a-service Container platform-as-a-service Platform-as-a-service
Virtual Machines Azure Kubernetes
Service
Red Hat
OpenShift
Java SE Tomcat JBoss EAP Spring Boot
Azure App Service Azure Spring Cloud
Virtual Machine
Scale Sets
J

10. Azure differentiation for Java applications
Fully managed offerings for any Java
app – Spring Boot, Tomcat, and Java
EE including JBoss EAP
90+ compliance certifications –
more than other cloud provider
Supported offerings from VMware,
Red Hat, Oracle, IBM, Redis,
and Elastic
More regions than Amazon Web
Services and Google Cloud
Platform combined
Single sign-on across cloud and
on-premises environments
>95% of Fortune 500 companies
run on Azure
Microsoft employs more Java
Champions in its technical staff than
any other cloud provider
Java services on Azure are
implemented in a Java-native way,
compared to other cloud providers

11. Factors to consider

12. Business factors
 Price
 Time
 Effort
 Complexity vs. maintainability
 Staffing mix
 In-house
 System integrator (SI)
 Contractor
 License portability

13. Technical factors – Azure Well-Architected Framework
 Reliability
 Security
 Cost optimization
 Operational excellence
 Performance efficiency
https://aka.ms/azure/well-architected
https://aka.ms/azure/well-architected/learning

14. Settings on the dial

17. Tradeoffs for each
 Price
 http://aka.ms/pricing-calculator

18. Tradeoffs for each
 Time
 Your choice of Azure destination is heavily influenced by how much time you have to get it
done
 Lift and shift and stay is the fastest
 But also more expensive to operate…
 and not really taking advantage of the power of the cloud

19. Tradeoffs for each
 Effort
 How different is your current environment from your chosen Azure destination?
 https://learn.microsoft.com/en-us/assessments/

20. Tradeoffs for each
 Complexity vs. maintainability
 How much complexity can you mitigate?

21. Tradeoffs for each
 Staffing mix
 In-house
 System integrator (SI)
 Contractor
https://azure.microsoft.com/en-us/contact/connect-to-partner/

22. WebLogic on Azure
Robust, up-to-date Azure Marketplace images and solutions
for WebLogic
• Linux, Oracle JDK, WebLogic
Jointly published, maintained and supported by Microsoft and
Oracle, bring your own license
Supports common use-cases such as base image, single instance
and clusters
Supports key integrations such as App Gateway, Azure SQL,
Azure PostgreSQL, Oracle DB, Azure Active Directory, Oracle
Coherence, ELK
aka.ms/weblogic-on-azure
Tradeoffs for each
 License portability

23. WebSphere on Azure
Robust, up-to-date Azure Marketplace solution for
WebSphere Traditional
• Red Hat Linux, IBM J9, WebSphere
Jointly published, maintained and supported by
Microsoft and IBM, bring your own license, trial license
Supports common use-cases such as single instance and clusters
Enables key integrations such as IBM HTTP Server, Azure SQL,
IBM Db2, Azure PostgreSQL
Similar support for Open/WebSphere Liberty on AKS/ARO
now available
aka.ms/websphere-on-azure
Tradeoffs for each
License portability

24. JBoss EAP on Azure
Robust, up-to-date Azure Marketplace solutions for JBoss EAP
• Red Hat Linux, OpenJDK, JBoss EAP
Jointly published, maintained and supported by
Microsoft and Red Hat
Standalone and cluster configuration
Virtual machines and virtual machine scale sets
Bring your own license, pay as you go coming soon
Enables key integrations such as App Gateway, Azure SQL, Azure
MySQL, Azure PostgreSQL
aka.ms/jboss-on-vms
Tradeoffs for each
License portability

25. Summary
 Cloud migration involves
many tradeoffs.
 There are business and
technical factors for each
one.
 I am not going to give you an
opinionated answer.
 You can get opinionated answers
from Microsoft specialists and cloud
solution architects.
 I invite you to please touch
that dial!
Microsoft
https://aka.ms/javaee-on-azure-survey