vFunction
Continuous Modernization Manager
Shift Left for Architects
vFunction Continuous Modernization Manager enables architects to assess, monitor, find, and fix application modernization issues before they result in a technical debt disaster – the first shift-left product for architects.
Trusted By
Catch Architectural Drift Anomalies Before Disaster Strikes
Baseline
Application Architecture
Monitor & Detect
Architectural Drift
Pinpoint
Architectural Anomalies
Find and Fix Architectural Anomalies
Application architects today lack the observability, visibility, and tooling to understand, track, and manage architectural technical debt as it develops and grows over time. vFunction Continuous Modernization Manager allows architects to shift left into the ongoing software development lifecycle from an architectural perspective to manage, monitor, and fix application architecture anomalies on an iterative, continuous basis before they erupt into bigger problems.
- Baseline, monitor, and alert on architectural drift issues such as new services are detected, new common classes found, service exclusivity changes, new dead code found, and new high debt classes identified.
- Get notified of architectural anomalies immediately through various alert systems including Slack, email, and vFunction Notifications Center.
- Once an architectural drift issue is pinpointed, address them directly with your development team or use vFunction Modernization Hub to resolve the issue.
According to a Gartner® report
“By 2026, 80% of technical debt will be architectural technical debt.”
Source: Gartner, Measure and Monitor Technical Debt With 5 Types of Tools, Tigran Egiazarov, Thomas Murphy, 27 February 2023.
GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved
Continuous Modernization Saves Money, Prevents Meltdowns
Architectural meltdowns and technical debt disasters have become all too commonplace. Technology leaders must move to a continuous modernization culture where technical debt is managed by setting organizational baselines for technical debt, monitoring for architectural drift, and catching major architectural anomalies before they become business catastrophes.
vFunction Continuous Modernization Manager – as part of the vFunction Application Modernization Platform – enables software architects, developers, and engineering leaders to both find and fix application or microservice architecture anomalies, determine architectural baselines, set thresholds, and alert when critical modernization anomalies are detected.
Unchecked architectural drift causes:
- Ballooning technical debt
- Architectural erosion
- System failures
- Security breaches
- Sky high cloud compute costs
- Dead code creep
Analyze
Analyze Analyze the application architecture in production, test, or staging with dynamic and static analysis.
Baseline
Baseline Set architectural baselines for technical debt, detected classes, dead code, common code, and high debt classes unique to your application.
Monitor
Monitor Observe and actively monitor for architectural drift from the established baselines to detect anomalies indicating significant architectural erosion events.
Alert
Alert Detect and pinpoint anomalies and threshold violations – often down to the offending Java class – and receive alerts in Slack, email, or the vFunction Notification Center to determine appropriate remediation.
Fix
Fix Triage architecture anomalies and use vFunction Modernization Hub to re-architect or refactor issues identified.
Architect Toolbox
Continuous Modernization Manager: How Does It Work?
vFunction Continuous Modernization Manager observes Java and .NET applications and services to first baseline the architecture, set baselines, and monitor for architectural drift and erosion to detect critical architectural anomalies including:
- New Dead Code Found: vFunction will detect new dead code in applications indicating that new, unnecessary code was added to the application or the baseline architecture drifted and existing class or resource dependencies were changed.
- New Service Introduced: Based on the observed baseline service topology, when a new service has been detected vFunction will identify and alert that a new domain or major architectural event has occurred.
- New Common Classes Found: Building a stable, shared common library is a critical modernization best practice to reduce duplicate code and dependencies. Newly identified common classes can be added to a common library to prevent further technical debt from building up.
- Service Exclusivity Dropped: vFunction measures and baselines service exclusivity to determine the percentage of independent classes and resources of a service, alerting when new dependencies are introduced that expand architectural technical debt.
- New High-Debt Classes Identified: vFunction identifies the highest technical debt classes that are the highest contributors to application complexity. A “high-debt” class score is determined by its dependents, dependencies, and size and pinpoints a critical software component that should be refactored or re-architected.
Users will be notified of changes in the architecture through Slack, email, and vFunction Notifications Center. Through vFunction Continuous Modernization Manager, architects will be able to configure schedules for learning, and analysis and the option to configure baseline measurements.
R&D Lead, Trend Micro
