Likelihood to Recommend
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.
Read full review
When we have a large organization and number of changes and deployments are more than we should go for Copado. As we know it is a paid managed package and the cost is high so for dealing with fewer deployments it is not preferable to buy. Copado is well suited for users who don't have much technical understanding. So those users can see the User interface select the changes that need to be deployed by selecting the metadata. From Git operation to deployment all is handled by Copado itself. Copado has reduced the efforts for creating the package.xml and direct deployments can be done within a few clicks. Another Major aspect is that it can be directly synced with Jira or Azzure board from where the user stories will be synced and actions can be performed accordingly. For small organization, Copado can be expensive and to set up and maintain we need a technical person to do so.
Read full review Pros 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. Read full review Metadata Deployments Data Deployments Salesforce CPQ deployments that require a lot of various Data Transferring deployments between teams. Read full review Cons 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. Read full review Back promotions are sometimes difficult and behave in a weird manner After the deployment to production next changes in the pull request shows all the changes from the previous release as well Cannot be used through mobile Read full review Likelihood to Renew
We have a huge knowledge of the product within our company and we're satisfied with the performance.
Read full review Usability
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
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.
Read full review Reliability and Availability
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.
Read full review Performance
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.
Read full review Support Rating
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.
Read full review Alternatives Considered 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.
Read full review
Flosum is a downgrade for sure and I do not recommend it. Gearset is an upgrade and my preferred solution. Gearset has simplified the deployment path and makes it very easy to move between Salesforce instances. If there are any difficulties with Gearset they also have the best customer support for any deployment tool I've tried. Overall I'd say Gearset is #1, Copado #2 and Flosum a distant #3.
Read full review Scalability
It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm
Read full review Return on Investment 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. Read full review It has reduced the efforts to create package.xml manually and deploy the changes Another positive impact is that we can track the commits to which org they have reached in an organized way and we don't need to maintain them separately For setting Copado it take a lot of time and training is required for the complete setup which is time-consuming Read full review ScreenShots