NGINX vs TIBCO ActiveSpaces

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Read full review

• 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.

Read full review

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

Read full review

• 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.

Read full review

• Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache.
• Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy").
• Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly.

Read full review

• The cost of Tibco ActiveSpaces is quite high, while the added value it brought is not as we expected.

Read full review