The News
At AWS re:Invent, Moti Rafalin, CEO & Co-Founder of vFunction, highlighted a series of updates and collaborations focused on accelerating application modernization, particularly for organizations working to re-architect legacy Java and .NET systems. The announcements centered on deeper integration with Amazon Q Developer, automated architectural analysis, and real-world modernization outcomes from early adopters.
These updates underscore a broader industry trend: enterprises are increasingly looking for ways to transform monolithic applications into modular, cloud-native architectures without the cost, risk, or multi-year timelines traditionally associated with great refactoring efforts.
Key Announcements
Technical Modernization with Amazon Q Developer
vFunction released a guided demo showing how its platform analyzes monolithic applications, surfaces domain boundaries and technical debt, and feeds that context into Amazon Q Developer. The integration enables developers to automatically generate TODOs, resolve architectural issues inside the IDE, and extract cloud-ready services such as Spring Boot components.
Modernization Acceleration
CDL, a UK insurtech provider, highlighted how combining vFunction with Amazon Q Developer helped them overcome architectural bottlenecks in their Policy Administration System. Despite earlier cloud and container migration efforts, architectural constraints persisted. vFunction provided dependency maps, prioritized refactoring tasks, and helped the team begin modularization work more confidently and quickly.
Enhancements for Architectural Technical Debt and GenAI Workflows
vFunction emphasized platform capabilities that identify and remediate technical debt, such as circular dependencies, domain entanglement, and “god” classes, using static + dynamic analysis and GenAI-assisted remediation. Integration with Jira, Azure DevOps, and IDE tools supports continuous modernization.
Alignment with AWS Modernization Programs
The company reiterated availability through AWS migration and modernization initiatives, including programs where eligible customers can receive funded licenses to support refactoring work. This is particularly targeted at organizations wanting to move monoliths toward AWS-native architectures like Lambda, ECS, or EKS.
Modernization Meets AI-Driven Development
vFunction’s AWS re:Invent 2025 presence reflects a shift in how enterprises approach modernization. Traditional large-scale rewrites and fully manual refactoring projects are increasingly misaligned with developer capacity and cloud adoption timelines. The emerging model blends:
- Architectural intelligence
- Automated code reasoning
- AI-driven assistants
- Incremental extraction and modularization
- Integration with existing SDLC tools
The integration with Amazon Q Developer reinforces an industry trend: AI assistants are most effective when provided with deep contextual knowledge of application architecture that typical LLMs cannot infer from code alone. By supplying this architectural context, vFunction aims to make modernization more repeatable and less dependent on rare architectural expertise.
The CDL example illustrates this demand. Even organizations that have already containerized and migrated workloads to cloud environments still face friction when underlying architectures remain tightly coupled. Architectural modernization, not simply infrastructure modernization, is becoming a prerequisite for realizing cloud value.
Market Challenges & Insights
Architectural Debt Remains a Top Barrier
Industry data indicates that architectural technical debt (ATD) is one of the most crippling impediments to achieving cloud elasticity, developer velocity, and scalable AI adoption. The recent study titled “Microservices, Monoliths, and the Battle Against $1.52 Trillion in Technical Debt” found that architectural debt is now considered the most damaging type of software debt for applications.
- Notably, 51% of organizations say they spend more than 25% of their annual IT/engineering budget on remediation, refactoring, re‑architecting, or addressing technical debt.
- Among the root causes: 44% of respondents pointed to monolithic complexity (lack of clear domain boundaries, poor modularity) as a top challenge. Another 39% described insufficient visibility into architecture, making it difficult to track dependencies, especially across microservices.
These findings reinforce that architectural complexity, not just outdated code or performance issues, remains a primary blocker. The announcements from vFunction are part of an expanding ecosystem of tools that help organizations address architectural debt in a more incremental, observable way rather than resorting to wholesale rewrites.
AI Assistants Accelerate Work Only When Grounded in System Context
The same vFunction research highlights that many enterprises view architectural observability, the ability to statically and dynamically analyze applications to understand structure, dependencies, and drift, as extremely or very valuable: 80% of respondents reported architectural observability capabilities would significantly benefit their engineering function.
This underlines a key market insight: if AI‑powered assistants or modernization tools operate only at the “code snippet” level, without structural awareness of the system, they will likely fall short of enabling real velocity or scalability. Tools that embed architectural context and observability are better positioned to enable meaningful acceleration, especially for AI adoption and cloud-native transformations.
Modernization requires a Shift from one-time projects to continuous cycles, also shows a strong trend toward continuous remediation: 77% of organizations have launched enterprise‑wide initiatives to tackle technical debt proactively. Rather than viewing modernization as a one‑off project or a periodic refactor, enterprises seem to be leaning into an ongoing, disciplined “architecture health” approach, continuously detecting architectural drift, monitoring complexity, and making incremental improvements. This shift mirrors broader industry patterns in which organizations prioritize maintainability and scalability over one-time migration events.
Cloud Value Realization Depends on Architecture
Broad market research supports what the architectural debt data suggests: simply lifting and shifting workloads to the cloud, without addressing underlying architecture, often fails to deliver the expected agility or cost benefits. One recent study found that around 80% of CIOs report they have not achieved the level of agility and business outcomes they anticipated from their cloud modernization efforts.
Part of the problem stems from legacy monolithic or overly complex architectures: estimates suggest that 35–45% of enterprise application portfolios remain monolithic, complicating modernization. Moreover, technical‑debt remediation associated with architecture, not just code, remains a critical and ongoing burden. For many organizations, migration alone does not eliminate architectural constraints; without structural refactoring and observability, cloud benefits (scalability, cost efficiency, agility) often remain unrealized.
Looking Ahead
The discussions with Moti from vFunction at AWS re:Invent 2025 highlight how modernization tooling is shifting from static analysis and lengthy consulting engagements toward AI-enabled, architecture-guided, assistive development. As cloud providers increasingly emphasize agentic AI and AI-assisted engineering workflows, architectural context is poised to become a key input for both intelligent development and automated system refactoring.
Next steps for organizations:
- Assess architectural visibility – Map existing monoliths and complex systems to identify areas where AI-assisted insights can accelerate modernization.
- Pilot AI-assisted refactoring workflows – Leverage tools like Amazon Q Developer and vFunction’s capabilities to experiment with incremental, architecture-guided modernization.
- Integrate modernization tooling into developer processes – Embed automated remediation and architectural guidance directly into CI/CD pipelines to maximize developer velocity and minimize disruption.
For organizations evaluating modernization strategies in 2025 and beyond, the key takeaway is clear: modernization outcomes improve when architectural insight, developer tooling, and automated remediation are tightly integrated. AWS’s ecosystem, particularly through Amazon Q Developer, appears well-positioned to make these patterns more accessible for engineering teams seeking to break down monoliths and unlock the next phase of cloud value.
TinyMCE AI Embeds Writing Intelligence Directly Into Dev Workflows
Twilio Expands Flex With Embeddable Contact Center Architecture
Telestream Expands Multi-Cloud Media Workflows with Oracle Cloud
New Research Finds AI Recommendations Drive Discovery, But Not Decisions
Mirantis and NVIDIA Automate AI Factory Deployments at Scale
