TIBCO Cloud Mashery Reviews

Tibco Cloud Mashery is used for all external API calls entering our organization, whether it's from mobile apps, websites, or third party providers and partners. It allows us to secure access by identifying callers, throttling traffic, and encrypting data entering the network. With ever increasing communication demands from the entire organization, Mashery acts as a cloud-based gateway, and relieves us of maintenance, while providing a worldwide network of access point.

Mashery connects to our load-balanced Tibco BusinessWorks 6 servers. It communicates directly with Oauth services for user identification. The line is secured with mutual SSL. Development, test and production environment pass through a single Mashery instance, managed on administration level. TCI and mock simulation features have been of limited use. Nevertheless, Mashery has been a major advantage in speeding up our API readiness.

TIBCO Cloud Mashery is used as the company API Gateway for many different digital solutions. We use it with all our mobile applications and web portals. It is used in different business areas and solutions.

We have a microservice architecture following the event-driven concepts, we don't use GraphGL yet, but we plan to.

We currently use TIBCO Mashery as our customer API platform to provide access to our API and meter their traffic. The Mashery platform provides an easy way to grant our customer access, but also protect our services as well. It is used across our organization and for all of our customers.

Currently using Tibco Mashery base. I have yet to learn, but I am interested in learning more about Microservices.

TIBCO Cloud Mashery was used by a single department initially and, then, exposed across the organization.

It is a component-based architecture where we can easily distribute and implement multiple environments easily.

We are using Mashery as API gateway. We use it company wide. It provides the whole platform for developers and enables them to integrate their apps with our product.

We have hybrid architecture. You can use monolith, microservices whatever you want with Mashery.

TIBCO Mashery is used as an API gateway across the business applications and also in the legacy stack. TIBCO Mashery as an API Management Layer helps quickly deploying APIs and easily set the policies on them.
It is very easy to set the rate limits, plans, quotas, security policies across the set of APIs.

Our organisation had mixture of many different patterns including microservices, event driven, message driven, etc. Mashery fits the microservices and event driven very well. All the application estate for microservices has been deployed on Mashery for internal and external consumption of data.

TIBCO Cloud Mashery is being used across several organizations to maintain consistency across all of our API usage. Since we are a SaaS company, we have several APIs in use and several different departments that use them. Especially now that we are moving quickly to cloud native solutions, including containers, we need the ability to standardize processes.

We have a mix of on-prem and cloud native software architecture situations. The IT and Research and Development teams have been using TIBCO for quite some time, and have become very familiar with the entire product suite. They will continue to migrate to cloud native solutions and will use TIBCO Mashery for that.

We use TIBCO Cloud Mashery to control traffic to our environments...not only to production but to our lower environments. It helps protect access to PII information and our clients' financial information. This information is expected to be protected not only in a legal aspect but in the aspect of company integrity. We take pride in providing services to the automotive industry and we are obligated to protect our customers and TIBCO Cloud Mashery helps do that.

Any traffic from outside our corporate intranet is protected and controlled. TIBCO Cloud Mashery helps us maintain that control. Our environment has a lot of inter-dependencies. We have a lot of microservices that need to be protected. TIBCO Cloud Mashery has helped us maintain that protection.

Mashery is being used as an API management tool fronting our public API to clients. Used across the whole organization. It allows the business to decouple systems and enable wider distribution through API technologies to customers and partners.

We have a highly leading-edge distributed architecture evolving from the service module to microservices and reactive architecture. We have not used any of the TIBCO features as they come out with tools that have already built years ago.

TIBCO Cloud Mashery is used as a content management tool, and a great way to build out API documentation. It also allowed us in the past to secure and open secure APIs to other teams outside of our organization. It was used by a specific department within our organization to help address a very specific need we had at the time, rather than the whole organization.

I don't want to go into too much about architecture as I'm not comfortable sharing that sort of information to the public. What I will mention is that TIBCO Cloud Mashery has enabled us to adopt modern architectural patterns such as Microservices, Event-driven APIs, and other similar patterns. It has really increased and bettered the way we work together as a organization in whole.

I'm using TIBCO Mashery on a daily basis. Entire Travel Insurance backend is using it to provide an API gateway solution and also address authentication and authorization for our API partner. It also adds one level of security for API endpoints.

Also our API partner uses this for both authentication and authorization.

Yes, we provide API as a service to partners. We have microservice and some cloud VM running behind the LB. We direct requests based on ENDPOINT Path.

We use TIBCO Cloud Mashery across the whole organization as an API Gateway, for all new and old products.

We use microservices in the organisation. Mashery has enabled us to move very fast and expose these services to the external world and to expose them as Mobile APIs very easily.

TIBCO Mashery is used as API Management Platform for our organization, connecting multiple subsidiaries nationwide, supporting over 300 million API calls a year.

Hybrid implementation, managing both cloud and on-premises APIs and legacy SOAP web services.

IEEE uses Tibco Mashery API to deliver metadata and full-text content on scholarly and academic works from a repository of more than 4.6 million artifacts within the domain of electronics and electrical engineers. The IEEE Xplore API is utilized internally and externally by our customer base to obtain data from discovery, text, and data mining (TDM) functions to save time and effort to do research.

TIBCO Mashery is our core API management platform. We use it to manage our API's hosted on-premise as well in the cloud. Mashery is used across the whole organization by different teams and departments. Mashery allows us to manage access to our API's and gives us insights about how our API's are used by API consumers.

We use Mashery in the Engineering department as an API Gateway for a client-facing RESTful API that has thousands of unique endpoints. We use it because we didn't want to have to reinvent the wheel on security, authentication, permissions, access rights, and things of that nature.

Mashery has been our API management tool across all of Cox Automotive (over 26 business units including companies like Manheim, AutoTrader, KBB, ..). The main problem it solves is proper access to hundreds of APIs built by our teams.

We use TIBCO's Mashery to be our API gateway to surface data and a way for our partners to interact with our business services.

Mashery acts as our API Gateway in our digital transformation program. Currently, it's being used as a pilot to serve internal API consumers, but soon it will be extended to be used IN the whole organization.

The API Gateway helps us to decrease the time required for API consumer/clients onboarding and applying different QoS and security options per client/consumers.

At Cisco, we externalize API services using TIBCO Mashery, which is one of the best API management solutions.

TIBCO Cloud Mashery enables connectivity for mobile applications. It serves as connector for startups and partners as well as for internal and partner airlines. It is used in the key area of the enterprise. The services offered on TIBCO Cloud Mashery enable new businesses. They are used for data sharing. Finally they allow IT solutions to be created by business departments without the need to have bespoke development and interaction with the IT departments.

We use Mashery to help authenticate and cache users for our business-to-business data delivery API.

Mashery's API is being integrated in into the backend development of our company. It is being used throughout the entire organization across the market sectors, front end development, as well as the back end side of our projects. We integrate Mashery into the Ruby code and utilize this in order to address the problems of server capacity as well as the server side analytics being done at our marketing firm.