Talk:Application portfolio management

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

"A web service that is structurally incapable of being part of a set of steps that provides value. For example, a web service that only accepts data breaks the schema."

I do not understand the last sentence. I think there maybe some words missing.

I went back too the source material and put some of the original text back in. It had been edited into nonsense. Nickmalik (talk) 18:06, 2 September 2014 (UTC)[reply]

Current Complexity[edit]

When Gibson & Nolan developed their idea in the 1970s, computing was far, far simpler than today.

Today is even more complex than during Y2K. Then it was simply mainframes & mini-computers. Today it is mainframe, client-server, web, SmartPhones, mid ranges, etc., etc.

Have the inventories of applications and the components in the applications from Y2K been maintained & kept current? Or abandoned? DEddy (talk) 17:37, 30 May 2015 (UTC)[reply]


The inventories that I've seen at several large organizations, maintained for the purpose of APM, have been neglected (not worth the trouble to maintain?), whereas the smaller scale (e.g. covering one data-center, rather than all sites) inventories, generated for IT security compliance via automated scans, are accurate at the time, but do not include cost and value measurement metadata and so are not useful for managing like an investment portfolio. Also the APM concept was pre-outsourcing because it originated before computer networks became pervasive and performant and so all applications were owned and operated in-house/on-premise by the using organization. Now that it is feasible to outsource not only the application software development, but the operations to CSPs (Cloud Service Providers), the notion of APM as evaluating investments is archaic, because services are not acquired and depreciated like assets, but are expenses requiring no capital outlay to hopefully recoup via productivity gains. Now there are new practices for organizations to employ to evaluate the portfolio of cloud services consumed and to minimize costs while maximizing the still-too-difficult to measure benefits, but this is a subject that could probably warrant its own article. https://en.wikipedia.org/wiki/Wikipedia:Requested_articles/Applied_arts_and_sciences/Computer_science,_computing,_and_Internet#The_Internet The proposed article could include links to the cloud cost optimization services that have sprung up e.g.:
https://www.agileit.com/cloud-licensing-services/
https://www.appxite.com/azure-cost-optimization
https://www.binadox.com/integrations/aws-cost-optimization/
https://www.bmc.com/it-solutions/cloud-cost-control.html
https://www.cloudability.com/product/gcp/
https://en.wikipedia.org/wiki/CloudHealth_Technologies
https://www.cloudyn.com/
https://welcome.metricly.com/aws_cost_optimization
https://www.nutanix.com/products/beam/
https://www.orbitera.com/billing/
...and even the CSPs own tools:
https://aws.amazon.com/pricing/cost-optimization/
https://azure.microsoft.com/en-us/pricing/details/cost-management/
https://cloud.google.com/cost-management/
Noiseiron (talk) 05:37, 26 March 2019 (UTC)[reply]