Tomcat is a suitable choice for deploying microservices or smaller applications. For beginners, it's excellent due to its lightweight nature and ease of deployment. For those dealing with larger applications, considering an alternative like Oracle WebLogic Server may be beneficial. Overall, I rate this solution eight out of ten.
We regularly upgrade to the latest versions of Tomcat and apply security patches to comply with the latest security aspects. I rate it a nine out of ten.
When declaring the application, the springboard is ready for use with Apache Tomcat. By default, it comes this way when you unplug it from Git. So, when you are deploying any application, it uses Apache Tomcat by default. One engineer is enough for the solution. In data centers, we need to analyze the backlog. You need a cost analyst to determine if integration or migration is necessary. Both are important for identifying requirements. Once you have clarity on these points, you can proceed with management. If these factors are achievable in the decision-making process, then it's worth considering. Overall, I rate the solution a ten out of ten.
Overall, I would rate the solution a nine out of ten. There are several application server options: JBoss, WebLogic, Tomcat, and Payara. I've personally worked with all of them. I recommend Tomcat for on-premises deployments because I've found issues with WildFly – they have frequent releases and patches, and some become incompatible with existing setups. My advice is to go with Tomcat for on-premises setups. Also, if you want to move to AWS or GCP, it's easy. You just need to change how you compile your application; the application itself doesn't need to change. It's a matter of moving from a WAR (web archive) file to a JAR (JAVA archive) file.
The tool's ease of use didn't pose any problems for us. We felt that it didn't cause any delays or issues with extending the timelines. Any delays were mainly due to vendor dependencies rather than issues with Tomcat. As far as security is concerned, an integrated team is responsible for it. As a developer, I believe it's pretty secure because it utilizes two modules running on different ports. Each application, one on Tomcat and the other on local, operates independently without interfacing. I rate the overall product an eight out of ten. A dedicated team within our organization managed the Tomcat version upgrade. They were responsible for upgrading Tomcat. They didn't encounter any issues during the upgrade process.
The product is easy for expanding multiple web pages, installation, and implementation. I rate its performance a ten out of ten. It provides good integration with other tools and software. The platform enables security features for various components, including servers, log directories, catalyst policies, and XML files. It helps us configure them in a way that no attacker would be able to view any of these files. Overall, I rate Tomcat a ten out of ten.
You just need to keep it up to date with the latest Java Virtual Machine software, and that would be all. Overall, I would rate the solution a ten out of ten. For anyone starting with Java development, I highly recommend starting with Tomcat. It might be an old-fashioned technology, but it's reliable and easy to use.
Apache Tomcat is a free tool. It can redirect or direct STDPs and other types of traffic. We are using a multi-level server setup. It is a simple tool to install and configure. We can accommodate it because the Apache Tomcat Marketplace is available, which provides a free set of open-source plugins and components. Overall, I rate the solution an eight out of ten.
Principal Infrastructure Solution Architecture at National Bank of Kuwait
Real User
Top 5
2023-03-22T12:59:29Z
Mar 22, 2023
In our company, we always favor products like IBM WebSphere as it is a vendor product for which we get the right amount of support we need. Also, we are using IBM WebSphere on AIX. Hence considering our use cases, we feel that IBM WebSphere is a more stable and reliable platform. So as a critical system, we are using the aforementioned solution. We use Tomcat in a company when we have no other options and are forced to use it, especially in scenarios where no other platforms are supported. So, if we have an option in our company, then we keep the usage rate of Tomcat low. Overall, I rate the solution a six out of ten.
I'm not sure which version of the solution we're using. It's likely close to the latest version. Apache is well suited, at least for NICE Actimize. I'd recommend the product to others. Based on the exposure I have, since it's limited to just one application being hosted or using Apache Tomcat, I would rate the solution seven out of ten.
While Tomcat is a reliable choice for an application server, it may not be the best option for real-time tasks involving TCP connections, WebSockets, and socket programming. In these cases, Netty may be a better choice due to its stability and performance. In your experience, you found that Tomcat was prone to connection issues when used for socket programming, leading you to switch to Netty. It is important to consider the specific needs and requirements of your project when deciding which tool or technology to use. I rate Tomcat an eight out of ten.
I would recommend this solution to other businesses. It is important to understand what approach you are going to take when it comes to installation. Tomcat is user friendly compared to solutions such as WebLogic or Oracle. I would rate this solution an eight out of ten.
Sr. Devops Engineer at a media company with 201-500 employees
Real User
2021-07-15T15:12:20Z
Jul 15, 2021
We're just customers and end-users. We don't have a business relationship with Tomcat. We also use the solution on a private cloud as well as on-premises. I'd rate the product at an eight out of ten. We're pretty happy with it. I have experience with WebLogic and Tomcat. I'd recommend Tomcat over Oracle, as it's easier to manage and install. It's my understanding that the pricing is a bit lower as well.
Especialista em TI at a healthcare company with 10,001+ employees
Real User
2021-02-26T14:56:32Z
Feb 26, 2021
Read the documentation that is available on Apache.org. If you have any issues, look to see what is available on the forums and on the web. Some people have been able to find a solution using the web. We have not had big issues when using Tomcat. I would rate Tomcat an eight out of ten.
Senior System Analyst at a tech services company with 1-10 employees
Real User
2021-02-09T16:43:00Z
Feb 9, 2021
My advice to someone considering Tomcat is that they don't have too much load on their website. It's not for all websites. For normal sites, they can use Tomcat. On a scale of one to ten, I would give Tomcat an eight.
Managing Consultant/ Enterprise Architect at a tech services company with 1-10 employees
Consultant
2020-11-22T15:44:37Z
Nov 22, 2020
Apache Tomcat is the application server, but the enterprise server that runs in it is Apache ServiceMix. For anyone who is interested in using this solution, I would suggest knowing your use case, and knowing it very well. If you can make it containerized, it's better, so that it can scale better. But, again, know your use case. Because I have not used other hardware, there is nothing to compare with and it is hard to rate. In terms of my usage, I am happy with it. I would rate Apache Tomcat a seven out of ten.
Tomcat is a reliable and efficient web server, popular for hosting and running Java-based applications. It is praised for its scalability, compatibility with different operating systems and development frameworks, and its ability to handle heavy workloads.
Users appreciate Tomcat's ease of use, robust performance, reliable server functionality, seamless integration with various platforms, extensive documentation, and strong community support.
Tomcat is a suitable choice for deploying microservices or smaller applications. For beginners, it's excellent due to its lightweight nature and ease of deployment. For those dealing with larger applications, considering an alternative like Oracle WebLogic Server may be beneficial. Overall, I rate this solution eight out of ten.
I would recommend using Tomcat because it is simple to integrate and use. I'd rate the solution nine out of ten.
We regularly upgrade to the latest versions of Tomcat and apply security patches to comply with the latest security aspects. I rate it a nine out of ten.
When declaring the application, the springboard is ready for use with Apache Tomcat. By default, it comes this way when you unplug it from Git. So, when you are deploying any application, it uses Apache Tomcat by default. One engineer is enough for the solution. In data centers, we need to analyze the backlog. You need a cost analyst to determine if integration or migration is necessary. Both are important for identifying requirements. Once you have clarity on these points, you can proceed with management. If these factors are achievable in the decision-making process, then it's worth considering. Overall, I rate the solution a ten out of ten.
Overall, I would rate the solution a nine out of ten. There are several application server options: JBoss, WebLogic, Tomcat, and Payara. I've personally worked with all of them. I recommend Tomcat for on-premises deployments because I've found issues with WildFly – they have frequent releases and patches, and some become incompatible with existing setups. My advice is to go with Tomcat for on-premises setups. Also, if you want to move to AWS or GCP, it's easy. You just need to change how you compile your application; the application itself doesn't need to change. It's a matter of moving from a WAR (web archive) file to a JAR (JAVA archive) file.
The tool's ease of use didn't pose any problems for us. We felt that it didn't cause any delays or issues with extending the timelines. Any delays were mainly due to vendor dependencies rather than issues with Tomcat. As far as security is concerned, an integrated team is responsible for it. As a developer, I believe it's pretty secure because it utilizes two modules running on different ports. Each application, one on Tomcat and the other on local, operates independently without interfacing. I rate the overall product an eight out of ten. A dedicated team within our organization managed the Tomcat version upgrade. They were responsible for upgrading Tomcat. They didn't encounter any issues during the upgrade process.
The product is easy for expanding multiple web pages, installation, and implementation. I rate its performance a ten out of ten. It provides good integration with other tools and software. The platform enables security features for various components, including servers, log directories, catalyst policies, and XML files. It helps us configure them in a way that no attacker would be able to view any of these files. Overall, I rate Tomcat a ten out of ten.
The solution is lightweight and provides the high flexibility needed in any stand-alone application. Overall, I rate Tomcat a nine out of ten.
You just need to keep it up to date with the latest Java Virtual Machine software, and that would be all. Overall, I would rate the solution a ten out of ten. For anyone starting with Java development, I highly recommend starting with Tomcat. It might be an old-fashioned technology, but it's reliable and easy to use.
I rate the overall product an eight out of ten.
Apache Tomcat is a free tool. It can redirect or direct STDPs and other types of traffic. We are using a multi-level server setup. It is a simple tool to install and configure. We can accommodate it because the Apache Tomcat Marketplace is available, which provides a free set of open-source plugins and components. Overall, I rate the solution an eight out of ten.
I would recommend Tomcat to other users. Overall, I rate Tomcat ten out of ten.
I would recommend using this solution. Overall, I would rate the solution an eight out of ten.
I rate Tomcat a ten out of ten. I recommend that anyone choosing the solution use Google to find out what to do.
I recommend Tomcat to others and rate it a seven out of ten.
The solution is easy to manage and has good stability. I rate it as a nine.
In our company, we always favor products like IBM WebSphere as it is a vendor product for which we get the right amount of support we need. Also, we are using IBM WebSphere on AIX. Hence considering our use cases, we feel that IBM WebSphere is a more stable and reliable platform. So as a critical system, we are using the aforementioned solution. We use Tomcat in a company when we have no other options and are forced to use it, especially in scenarios where no other platforms are supported. So, if we have an option in our company, then we keep the usage rate of Tomcat low. Overall, I rate the solution a six out of ten.
I'm not sure which version of the solution we're using. It's likely close to the latest version. Apache is well suited, at least for NICE Actimize. I'd recommend the product to others. Based on the exposure I have, since it's limited to just one application being hosted or using Apache Tomcat, I would rate the solution seven out of ten.
I definitely recommend the solution for website hosting. I rate it a seven out of ten only because customer support is not available.
I give the solution an eight out of ten. Depending on the hardware an organization is using, there can be memory issues when using the solution.
While Tomcat is a reliable choice for an application server, it may not be the best option for real-time tasks involving TCP connections, WebSockets, and socket programming. In these cases, Netty may be a better choice due to its stability and performance. In your experience, you found that Tomcat was prone to connection issues when used for socket programming, leading you to switch to Netty. It is important to consider the specific needs and requirements of your project when deciding which tool or technology to use. I rate Tomcat an eight out of ten.
I would rate Tomcat a ten on a scale of one to ten.
I would recommend this solution to other businesses. It is important to understand what approach you are going to take when it comes to installation. Tomcat is user friendly compared to solutions such as WebLogic or Oracle. I would rate this solution an eight out of ten.
On a scale from one to ten, I would give Tomcat an eight.
I rate Tomcat eight out of 10. My only issue with it is the security. You need to use another solution.
We're just customers and end-users. We don't have a business relationship with Tomcat. We also use the solution on a private cloud as well as on-premises. I'd rate the product at an eight out of ten. We're pretty happy with it. I have experience with WebLogic and Tomcat. I'd recommend Tomcat over Oracle, as it's easier to manage and install. It's my understanding that the pricing is a bit lower as well.
I would recommend this solution to others. I rate Tomcat an eight out of ten.
My advice Look at all the options of server hosting before choosing Tomcat. I would rate Tomcat a seven out of ten.
Read the documentation that is available on Apache.org. If you have any issues, look to see what is available on the forums and on the web. Some people have been able to find a solution using the web. We have not had big issues when using Tomcat. I would rate Tomcat an eight out of ten.
My advice to someone considering Tomcat is that they don't have too much load on their website. It's not for all websites. For normal sites, they can use Tomcat. On a scale of one to ten, I would give Tomcat an eight.
Apache Tomcat is the application server, but the enterprise server that runs in it is Apache ServiceMix. For anyone who is interested in using this solution, I would suggest knowing your use case, and knowing it very well. If you can make it containerized, it's better, so that it can scale better. But, again, know your use case. Because I have not used other hardware, there is nothing to compare with and it is hard to rate. In terms of my usage, I am happy with it. I would rate Apache Tomcat a seven out of ten.