To Refactor or Not: How to Systematically Modernize Your Java Applications
summary
A step‑by‑step framework that scores apps by business (backlog, customers, revenue), economic (licensing, infra cost) and technical attributes (inbound connections, OS dependency, HTTP sessions) and then prioritizes low‑effort/high‑value refactors. Uses Dynatrace APM to map topology, surface unknown service calls, and compute metrics like action frequency, response time and their product (user‑experience consumption). Replatform fast wins (convert Tomcat/ear to Spring Boot fat jars) or apply domain‑driven slicing guided by Conway’s law to build microservices on Pivotal Cloud Foundry.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:52Enterprise Perspective
- 6:09Application Filters
- 7:56Technical Filters
- 9:39User Experience Behavioral Analytics
- 12:45Topology Analytics
- 15:23Maturity Model
- 18:19Conways Law
- 20:29Reducing Cohesion
- 21:47Model Behaviors
- 22:14Monitoring
- 22:59Service Flow
- 23:29Monitoring Strategy
- 24:34User Experience
- 26:09Summary
- 27:24Questions
related talks
58mSoftware Modernisation
47mApp Modernization of Java applications.
48mContinuous Modernization
55mModernizing Legacy Code - While Not Bringing Down Prod
59mTools & Tips to Modernize Your Java code with AI
28mAutomated Java Upgrades: From Pain to Productivity in 30 Minutes
38mModernization 101: A Beginner's Guide to Application Modernization and Methodology
47mSave or Reimplement?