Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

vFunction Architectural Observability Manager

vFunction Architectural Observability Manager

By: vFunction Latest Version: 3.5
Linux/Unix
Linux/Unix

Product Overview

Without measuring and using the right tools to manage and remediate architectural technical debt, it will become the largest unaudited liability of your organization. This creates significant compliance and off-balance sheet risks and exposure, hidden from the C-suite until it is too late. If migrating to AWS, just lifting and shifting your architectural technical debt to the cloud will prevent you from realizing the true benefits of the cloud. In summary, like financial debt, technical debt must be surfaced, tracked, and managed.

Architectural Observability (AO) Platform analyzes an application statically and dynamically, and uses AI to understand its architecture, observe drift, find and fix architectural technical debt, including extraction of domains into microservices, using its Code Copy (CC) feature.

Architectural observability is foundational to any modernization use case, including modernization associated with pre and post migration to the AWS cloud, and enables organizations to directly improve:

  • Feature release cycles
  • Business velocity
  • Speed of innovation
  • Developer Productivity
  • Scalability
  • Cloud benefits & cost

Directions (please note, your license will be provided only for the correct instance size corresponding to the number of applications as described below):

Upto 8 Applications - m6.2xlarge
More than 8 Applications - m5.4xlarge

*Unlimited Number of classes
*One can purchase any combination of Packs
*Definition of an application: for the purpose of counting applications for licensing, vFunction treats each JVM or CLR as an application. JVMs or CLRs running similar code bases are only counted once. Microservices do not count as Apps for pricing because they cover part of the functionality of one or more business Applications. While it makes sense to group them (e.g. by Business Capability), we reserve the right to enforce the fair-use policy: The ratio of total JVMs/CLRs to Business Applications shall not exceed 10:1

Version

3.5

Operating System

Linux/Unix, Amazon Linux 2023

Delivery Methods

  • Amazon Machine Image

Pricing Information

Usage Information

Support Information

Customer Reviews