One biggest advantage of the Tibco ActiveSpaces is it's ease of integration with the TIBCO suite of products. Hence it is more suitable to TIBCO AS in conjunction with the TIBCO suite of products.
All products could offer the same or different level of advantages. For the …
TIBCO ActiveSpaces is only suited in the company where Tibco suites have been already used, the license cost is not a concern, it is only required for data caching purposes and only works in the client/server mode for middle-sizes of data. If the expectation is data cache + distributed computation or embedded IMDG is also one requirement or the data cluster needs span multiple data centers, other light-weight OpenSource IMDG solutions should be considered
Mashery is great when it comes to deployment to your own datacenter and when it comes to managing third party API's like Salesforce using Mashery Cloud version. I would be a little bit more careful when deploying it on Kubernetes as it was not designed for it. New version 5 is re-architected to run more on natively on Kubernetes, but we have not tested it yet.
Tibco ActiveSpaces is an excellent caching tool. With good design, we can haven a efficient cache layer, that can respond to business needs in sub-seconds (milliseconds) rather than seconds / minutes to respond. This is specially useful for improving the efficiency of the services used in customer interactions.. like login, serving billing information, serving the customer's service usage and any other information customer is interested in accessing frequently.
System process can also use the ActiveSpaces . By caching the information frequently used by the system processes, the data cab be accessed more frequently. And without much disruptions.
If you are already using TIBCO tools, then ActiveSpaces is the right choice to use, as the product is well integrated with all the TIBCO Suite of products. ActiveSpaces integrates well with most common products like TIBCO BusinessWorks, TIBCO BusinessEvents etc.
ActiveSpaces can be easily deployed to a target (TIBCO) environment, with very little additional effort. Although there is an effort required to deploy them.
ActiveSpaces is supported by TIBCO BusinessWorks 5.13 and TIBCO BusinessWorks 6.x. Hence you are not forced to use any version of TIBCO BW, just because you have to use TIBCO ActiveSpaces.
TIBCO ActiveSpaces Tuple-based data structure is not flexible enough to support customized native data objects.
There is no secondary index option.
Doesn't provide "predicate based In-Grid distributed search and result aggregation."
only can be used as data cache, the node's only contribute memory but can not use the data partition owner node's computation power to apply the distributed computation customized by the user.
Cross data center replication (geographically) is a pain.
Encounter the performance issue when the data volume is huge, even according to the architecture design, linear scaling up should not have that issue.
The "Control Center" admin dashboard is not performant. We have a lot of configuration data in Mashery (many endpoints, many plans, many users, many keys, etc.) and the website struggles with the volume of data it has to deal with.
Their systems have limitations that make it more difficult for us to operate the way we would like. For example, there is a limit to the number of API Definitions we can create, as well as a limit to the number of Endpoints we can define in a Plan.
Their support organization leaves a lot to be desired. Responses are slow, and when they do come they are often inadequate. We have to re-phrase the question to get them to answer it differently, or we have to repeatedly follow up to ask for additional clarifying information.
i find some of the package adding and key are complex . UI experience is bad . Every step need front and backward navigation too much. It would be better if endpoint itself contain package and key addiction option
One biggest advantage of the Tibco ActiveSpaces is it's ease of integration with the TIBCO suite of products. Hence it is more suitable to TIBCO AS in conjunction with the TIBCO suite of products. All products could offer the same or different level of advantages. For the enterprises that are already using the AWS, then they will prefer to go for Amazon ElastiCache. Oracle In-Memory Cache might have the same level of advantage but the if you are already using the TIBCO suite of products like the BusinessWorks, then TIBCO ActiveSpaces seems to be the right option since there is an out of box plugin available for TIBCO AS and it is compatible with TIBCO products. Otherwise, lots of custom coding is required to use the Oracle or Amazon products as these plugins are not readily available and supported by TIBCO BW.
I've really only looked at Mashery since it has been around a very long time and has a rich feature set. I do know our platform teams are looking into AWS gateway but not sure this product has everything we need.
As a API Mediation layer it has helped with the troublesome port setup with internal and external clients. Meaning it made that easy to the client that they know where to go for access to an API.
The interactive documentation is very well put together and has reduced the time that developers have to go back and forth with each other to figure how to call the API.
