Tomcat is an open-source web server supported by Apache.
N/A
Pricing
Apache Tomcat
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
Apache Tomcat
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
Apache Tomcat
Considered Both Products
Apache Tomcat
Verified User
Manager
Chose Apache Tomcat
Tomcat's configuration is simpler because it's a plaintext file that anyone can read -- and a script can manage. It's easier to monitor via Grafana. And it integrates well with software load-balancers.
Apache Tomcat is very smooth tool compared to other applications. Since there are very less feature it's very smooth. NGINX server doesn't need Apache Tomcat we can directly deploy so it faster comparatively. In my working time I have never come across the UI of NGINX. Apache …
Verified User
Employee
Chose Apache Tomcat
We work with Java, and we needed to integrate Tibco RV which had a Java library. Node was not so easy to manage in the backend and we opted for something more known. As said we still love Tomcat and we heard a lot of bad experiences with NodeJS, quite tricky and slow to learn. …
Commercial application servers are available that support enterprise application needs, but many times this is overkill for most web applications running in the cloud, particularly for independent software vendors. The capabilities and management tools provided with these …
Apache Tomcat is lightweight but performs well, even when running multiple applications. Its performance and security features are the reasons for choosing Apache Tomcat among its competitors. Also, there is a huge community support than other products.
Apache Tomcat is used for our cloud-based apps when testing on our local machines. Oracle WebLogic is used for our older on-prem apps. Thus, it's difficult to compare them apples-to-apples. However, Apache Tomcat is not really meant to run in production for our older apps …
We considered between Tomcat and WebLogic and then choose Tomcat as it is much simpler and have all the features we need, also we need to integrate Tomcat with our Gitlab pipeline and Tomcat is well supported with its API set. In the future we plan to move our system to Azure …
Apache Tomcat is more lightweight and much quicker to deploy, so compared to JBoss or Weblogic it's much more efficient and cost effective for deploying small apps. The instances start up almost immediately and almost no maintenance is needed from the admins. There is also no …
Tomcat stacks up against the others very well due to its adoption in the open source community, low total cost of ownership, maintenance, and ease of deployment. It's much more lightweight than Websphere or Weblogic and provides most of the features most developers would need, …
We use WebLogic as an enterprise level large application container. We have a big WebLogic cluster, hosting our core applications. We also use tomcat to build a quick POC and some light-weighted RESTful service for a cloud-native initiative, so the relationship should be …
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 …
Tomcat is definitely easier to implement, continues to be supported and further development to enrich the existing feature set carries on. It is the industry, de facto standard. With third party vendors offering support for the industry standard, utilizing another solution is …
As I have described before, Tomcat has competition from Jetty & frameworks like Netty. Also with NodeJs, lot of web application server side development and API development is beign done using javascript & Nodejs. So there is some decline in the use of Apache Tomcat. Though it is …
Tomcat is a more lightweight container in comparison to Oracle's Glassfish server. Glassfish however, became an enterprise product and can offer better after sales service.
Apache Tomcat is a much wider open standard than Microsoft IIS. It also seems to use fewer resources and is simpler to maintain. Troubleshooting when an issue arises is difficult. We had trouble managing the Tail logs when something strange happened. Logging is very complex and …
Well WebLogic is very complex. Most of what happens with WebLogic requires servers to be restarted, which isn't always possible. Also, Oracle tries to force you to only use their GUI interface for most of the administration, which could be done directly in the files, but are …
Relative to other solutions that worked with the Spring framework, Tomcat was the best. It worked exactly as desired and made releasing production builds a very smooth process. However, if I were able to choose, I would use one of the newer scripting languages that has a server …
GlassFish seemed to be fairly comparable in terms of easy of configuration and deployment, but we didn't do any side-by-side performance comparisons. Tomcat was better-known by the team, has more online forum support, and met the requirements of our project. Tomcat is fairly …
It's clear that JBoss is a full JEE stack implementation while Tomcat isn't, but if you don't need the whole JEE stack there are many lightweight alternatives that implement the required feature with Tomcat.
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.
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.
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.
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.
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.
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.
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.