Architectural Observability Platform
Understand, monitor, and manage your software architecture
The first AI-driven Architectural Observability Platform that continuously observes your software architecture so you can find, fix, manage, and prevent architectural technical debt to improve modularity, scalability, and engineering velocity.
R&D Lead, Trend Micro
AI-Driven Architectural Observability
Observe your architecture
Modularize your application
What is Architectural Observability?
- Manage and remediate architectural technical debt
- Define & visualize domains leveraging dynamic analysis and AI
- See class & resource dependencies and cross-domain pollution
- Find & fix high-debt classes
- Improve modularity by adding common libraries
- Pinpoint dead code and dead flows based on production data
- Establish a baseline architecture
- Observe & detect architectural drift
- Refactor monoliths into microservices using Code Copy feature
vFunction Architectural Observability Platform
The Architectural Observability (AO) Platform helps you analyze your software architecture to find, fix, and prevent architectural technical debt (ATD). Using AI and static and dynamic analysis, the AO Platform enables a data-driven strategy to address architectural issues, modularize code, and continuously modernize your application. When architectural drift occurs, the platform identifies and alerts teams with helpful to-dos to keep ATD in check.
After modularizing a domain you can use Code Copy to automate the extraction of that domain’s code, to accelerate the creation of a microservice. Code Copy also generates Restful APIs for those services and automates needed framework upgrades.
How Architectural Observability Works
vFunction analyzes application architectures through AI-enabled dynamic and static analysis in test, staging, and/or production environments.
Assess architectural technical debt (ATD). vFunction learns your application and creates a meta model representing class and resource interdependencies. It then allows you to impose your architectural view (current or future) on it and understand the health of that architecture — how modular it is and what are the interdependencies of resources such as classes, database tables, beans, transactions, files, synchronization objects, sockets, and stored procedures. In addition, vFunction identifies sources of technical debt, such as high debt classes and dead code in the context of the defined domains.
Pinpoint and immediately address sources of technical debt. Define domains and identify cross-domain pollution, high debt classes, and cross-domain database relationships to add to your modernization to-do list.
Resolve issues, then set the architecture state as a baseline for ongoing observation, including new domain identification, exclusivity thresholds, common libraries, dead code, and more.
Scan the bytecode or initiate dynamic analysis on a scheduled basis or triggered from a CI/CD pipeline or application build/deploy.
Observe architecture drift events and alert the architect to what has changed and what should be fixed. Critical events include changes in common libraries, new dead code found, new database dependencies detected, new domains identified, new high debt classes introduced, and identified circular jar dependencies.
Architects will be notified of architectural events through Slack, email, and vFunction Notifications Center.
These events form the modernization to-do list for the architect, pinpointing specific classes, high debt targets, dead code issues, and database table interdependencies to create stories for the next agile sprint.
Assign modernization stories, validate fixes, and confirm improvement in overall technical debt scores.
Catch architectural drift events and fix them incrementally in each agile sprint. Increase modularity of your application up to full microservices transformation, either on an ongoing basis or as part of a defined modernization project.