Apache Tomcat vs. Mashery (now part of Boomi) vs. NGINX

Excellent value for companies wishing to host Java applications in the cloud. Utilizing hosting tools such as load balancers and network and application firewalls, Tomcat can be part of a powerful system to host web applications to thousands of users. There has been consistency in the development and support of Tomcat since its initial release in the late '90s and the best commonalities have been carried forward. If you host Java web applications, Tomcat is as good as any for an application server.

Incentivized

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.

Incentivized

Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.

Incentivized

• Fast to start up, which is useful when we need to just check that our changes are working correctly.
• Free, which allows us to not be involved with the finance/legal team about using it.
• Bundled with Spring Boot, which makes it even more convenient for our testing.

Incentivized

• Easy integration of the TIBCO Cloud Mashery developer portal allows simple onboarding and user and application management.
• Configuration of TIBCO Cloud Mashery is both flexible and focused to address the main tasks for an API Management solution.
• The built-in OAuth Token capabilities provide a quick start to properly manage application access.

Incentivized

• 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)!

Incentivized

• Using tomcat manager to troubleshoot is not very informative. Error messages are vague, you have to dig into log files for more information about the problems.
• Is great for simple web applications, but may not work for heavy development which may require a full J2EE stack, might like JBoss better.
• Security in tomcat is not straightforward, as I discovered that you have to understand how to set up realms in tomcat in order to hash passwords, which I was not overly familiar with, which is a big deal when setting up users in the tomcat-users.xml file.

Incentivized

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

Incentivized

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

We have a huge knowledge of the product within our company and we're satisfied with the performance.

Incentivized

Ease of use.

Incentivized

Great value for the product

Incentivized

Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.

Incentivized

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

Incentivized

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

Incentivized

Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.

Incentivized

Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.

Incentivized

Well, in actuality, I have never needed support for Apache Tomcat since it is configured and ready-to-go with no configuration needed on my end.

Incentivized

Support has been good overall.

Incentivized

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.

Incentivized

Initially it was difficult to understand . after few day , it was easy

Incentivized

Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it requires less memory to operate, you may realize that it is very efficient.

Incentivized

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.

Incentivized

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

Incentivized

It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm

Incentivized

• Tomcat is cheap and very quick to deploy, so it has benefited much when situation needs applications to be deployed quickly without wasting time on licensing and installations.
• Plenty of documentation available so no vendor training is required. Support contract is not needed as well.

Incentivized

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

Incentivized

• By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
• Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
• Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.

Incentivized