
In version 46 of Txture, we took another iteration on our Application Portfolio Advisor (APA), which helps cloud architects, cloud governance teams and associated stakeholders to identify transformation candidates in an application portfolio and provide metrics to visualize success of change.
In this post we want to highlight two particular improvements we've added to APA:
Transformation Cockpit provides all the features you need to assess applications and plan target architectures in detail.
In the Application Portfolio Advisor, we now show you previews of relevant transformation scenarios. This helps you select the best-suited applications for different cloud transformation initiatives.
Figure 1 shows a few simulated cloud approaches to optimize selected portfolio applications already running in the cloud.
Figure 1. Savings potentials and simulated cost shown for a few selected cloud applications.
Each simulated approach is also presented with details on savings per application. You can then directly access the Transformation Cockpit for viewing cloud proposal details, adjusting them, discussing with engineers and eventually defining the roadmap for teams to deliver the migration - see Figure 2.
Figure 2. Per application savings possible for a particular cloud approach. Details and adjustments are offered in the Transformation Cockpit.
In this release, next to standard migration and modernization approaches, we have also added simple approaches to get a view on possible optimizations just by doing (performance based) right sizing (cf. "APA Right-Sizing) and shifting to more effective data center locations (cf. "APA Datacenter Relocation").
For version 47, we will continue our efforts to add even more default cloud approach choices and more info on savings as well as benefits of a particular approach.
While APA focuses on your application portfolio, giving you per-application or per-business capability cost allocation views, there will always be assets in the repository that stay detached from application stacks or are yet to be connected.
In order to observe technology obsolescence, cost and carbon for these detached assets, we have added a dedicated view mode in APA - see Figure 3 and 4.
Figure 3. Detached assets mode in APA to allow toggling inclusion of assets not belonging to any application stack.
Figure 4. Example cost views including both application stack cost and those incurred by assets detached from applications.
Want to learn more about the Txture platform? Reach out to us, we'll be happy to help!