Principal Enterprise Architect (Cognizant Digital Business) at Cognizant
Real User
Top 10
2024-06-07T06:45:46Z
Jun 7, 2024
We use it for API management, as an API gateway. All those APIs have been published there, and we call them from there. It's a centralized platform. So, overall, it's used as an API gateway and for publishing APIs. This is a bit like a custom-built solution. So, it is specific to the customer. It is like a customer portal, like internet-facing. Currently, we do have it in our application portfolio. But in the future, we're trying to replace it due to organizational guidelines to move away from certain prices and costs.
Associate Vice President - Solutions, presales & services at Bahwan CyberTek
Real User
2022-05-20T19:28:29Z
May 20, 2022
Mashery comes as a package bundle for all three components of API management, like API management, portal, and API gateway. That is, all three components are combined into one. When companies want to monetize the APIs or they want the partners to consume the APIs, then the API management solution comes into the picture. It makes it more flexible in exposing APIs, whether you have existing APIs or you want to create new APIs.
Data Architect at a computer software company with 1,001-5,000 employees
Real User
2021-03-25T18:47:40Z
Mar 25, 2021
We implement a lot of TIBCO solutions for our clients. Most of the use cases for this solution are generally around API monitorization and API security. Some of our clients also use it for building an API mesh. We have deployed the latest version as well as the previous versions of this solution. We have on-premises deployments and public cloud deployments on AWS.
Learn what your peers think about TIBCO Cloud API Management. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
Chief Technology Officer at a transportation company with 10,001+ employees
Real User
2020-02-23T06:17:03Z
Feb 23, 2020
We're using the solution to expose our APIs so it can be used by a civil customer, where there are mainly internal touchpoints. We are also using it to expose our APIs internally.
APIs are critical business assets that form the foundation of digital business enabling new business models, improved operational efficiency, and connected customer experiences. TIBCO Cloud API Management empowers users to maximize the business value of their APIs products through an end-to-end solution that provides full lifecycle API management alongside capabilities for API discovery, implementation and analytics that speed business value realization across your digital ecosystem.
We use it for API management, as an API gateway. All those APIs have been published there, and we call them from there. It's a centralized platform. So, overall, it's used as an API gateway and for publishing APIs. This is a bit like a custom-built solution. So, it is specific to the customer. It is like a customer portal, like internet-facing. Currently, we do have it in our application portfolio. But in the future, we're trying to replace it due to organizational guidelines to move away from certain prices and costs.
We are using TIBCO Cloud API Management in the telecom domain.
We use TIBCO Mashery API Management for API gateway functionality and to add security and throttling. We also package and expose the API.
Mashery comes as a package bundle for all three components of API management, like API management, portal, and API gateway. That is, all three components are combined into one. When companies want to monetize the APIs or they want the partners to consume the APIs, then the API management solution comes into the picture. It makes it more flexible in exposing APIs, whether you have existing APIs or you want to create new APIs.
I use Mashery to integrate mobile applications with my services.
We implement a lot of TIBCO solutions for our clients. Most of the use cases for this solution are generally around API monitorization and API security. Some of our clients also use it for building an API mesh. We have deployed the latest version as well as the previous versions of this solution. We have on-premises deployments and public cloud deployments on AWS.
We primarily use the solution for B2B integration.
We're using the solution to expose our APIs so it can be used by a civil customer, where there are mainly internal touchpoints. We are also using it to expose our APIs internally.
We mainly use it to expose APIs for internal and external usage.