What is our primary use case?
My main use case for Apptio Cloudability is that we use AWS as our backend for mobile apps, so I use it to check the cost and any wasted efforts from using our APIs, or if there's any break. For example, if we are using more APIs at some point than what is required, we are able to see the day-to-day costs regarding our APIs and analyze it for further action.
Beyond that main use case, at some point, our application calls an API every second or is uploading full-size photos, which multiplies the backend cost. With Apptio Cloudability, I can look at this cost impact so that I can find the problems, such as wasting money, without having to wait until the month-end when we get the bill.
Before that, I can check the application and see that an issue is happening. For example, it's calling multiple times, which is leading to a higher cost. The app will also become very slow if we upload or download the images frequently, every second. In that scenario, that is the best case where I have utilized this application.
Regarding how my organization uses Apptio Cloudability to attribute AWS usage and cost data back to specific business units or applications, we have multiple applications in my company, so it is used across the company with all applications. Because APIs are used in a web application or mobile application, I use it in all the places.
One FinOps capability I've implemented for AWS using Apptio Cloudability is that I use it for breakdowns, alerts, waste detection, and forecasting and budgets.
How has it helped my organization?
Apptio Cloudability has impacted my organization positively. As I mentioned earlier, my company plans a monthly release where the application will be released on a monthly basis. If I know that something is happening in the application which is leading to more cost, we would have to wait until the bill is generated at the month-end. It will take another month to release the app.
However, using this application, I am able to understand that something is happening with this API. In one example, uploading and downloading images frequently, such as while we are scrolling in the table, we may need to download the images and upload. Using this application, I can catch the bug as early as possible, and I can fix it and plan the release. It leads to staying within the budget, and the second thing is the app's performance. So I can save money and time as well.
For specific outcomes or metrics, we don't see major spikes. I usually do my best to make the application perform well. A very minute percentage will change in the metrics using this application, not a really big one.
What is most valuable?
The features that stand out to me in Apptio Cloudability are that I use this for two purposes. One is for APIs and the other is for push notifications from AWS. It gives a clear view of cost and app backgrounds. It also shows the cost spikes and waste early on. It also shows the cost per feature or per user, which helps product decisions.
I also heard that it will be used across AWS, which we are already using, but apart from that, it's also used for Azure and Google Cloud. That is good. It helps engineering and finance use all the data.
Out of those features, the one that has been most valuable for me personally is identifying waste early. Ultimately, we should not cross the limits of the product, which would lead to a problem for my company or the application. It catches the cost spikes and also shows the waste early, which is not required. That is the best one because I can't wait for the month-end to get the bill. In the meantime, I can identify the issue and plan for a release to fix that issue. I can make a release as early as possible.
Regarding Apptio Cloudability's AI capabilities, its governance and security are fine. I am good at security. All the data is secured using this application and I am happy with that.
The information I get from Apptio Cloudability is trustworthy. It almost matches reality and matches my expectations.
Regarding how Apptio Cloudability interacts with my data from AWS and other cloud environments, this application's information is very accurate, which matches reality. The second thing is the UI. I am able to see a clear picture of what exactly I want. There is no mess with the metrics. For example, if I want the graph to be in a certain format, it's in a way that non-technical business people can understand what is happening. The visibility and everything is good.
The aspects of Apptio Cloudability's support for AWS that are most notable or impactful for my organization are mainly push notifications and API calls.
Regarding how I identify underutilized AWS resources using Apptio Cloudability, I rely on savings suggestions.
What needs improvement?
Apptio Cloudability is a paid enterprise tool. For small projects, it may cost more than it saves. That's one thing. Also, it won't show application crashes or performance. It only shows the cloud cost. It doesn't show any app code, crashes, or performance metrics. These are missing in the tool.
I feel Apptio Cloudability could be improved by showing performance. For example, there is an API that may take some time to load the data. Ultimately, the user will be happy if he gets the instant information that he requires. So, the API performance plays a major role in that.
If this application could handle this kind of situation, for example, showing that an API call got the response in this much time, that data would also be very useful for a developer to understand that this API took more time than required and we need to fix it. That data would be very useful to have.
Regarding additional improvements that would make my workflow easier, I only thought of including the time taken for an API in the application.
Regarding how I integrate Apptio Cloudability's recommendations and alerts with my existing AWS deployment workflows, it needs good tagging in AWS, otherwise the numbers are actually vague. That is something I'm now mentioning. It needs good tagging in AWS.
For how long have I used the solution?
I have been using Apptio Cloudability for around three years.
What do I think about the stability of the solution?
Apptio Cloudability is stable.
What do I think about the scalability of the solution?
The scalability of Apptio Cloudability is very smooth because I am handling many applications. For all applications, I am using the same application for this cost API information.
How are customer service and support?
Regarding customer support for Apptio Cloudability, I usually raise a service request if any issue happens. It will be very fast to respond. It's good.
On a scale of one to 10, I would rate the customer support as 10.
Which solution did I use previously and why did I switch?
I have been using Apptio Cloudability from the beginning because I don't have a second thought about that. I have been using it from the start and I don't have a second thought about switching.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Apptio Cloudability is a good experience. I'm able to see the accurate numbers regarding the pricing and setup cost and everything. I'm good with that. My experience is very good.
What other advice do I have?
On a scale of one to 10, I would rate Apptio Cloudability overall as eight.
I chose eight out of 10 for a few reasons. One, it's only useful for a big company. The second thing is, as I said, the performance of an API should be included, which will help each developer or the company fix their issues. Those are the two.
My advice for others looking into using Apptio Cloudability is that it will be very helpful. The only thing is the performance of an API. Apart from that, it's good and I will suggest this application for day-to-day regular development tasks.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)