NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
N/A
TIBCO ActiveSpaces
Score 7.4 out of 10
N/A
ActiveSpaces from TIBCO supports an application infrastructure.
[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.
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
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.
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.
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.
Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.
Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.
We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
we have a large number of services and we can manage a single Nginx instance for all of them
we have high impact services and Nginx never breaks a sweat under load
individual services have special considerations and Nginx lets us configure each one uniquely
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.
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.
