Apache Tomcat vs. Codefresh

Tomcat is more than enough to deploy most of the mid-end web applications without any problem but for the high-end applications which require high scalability and high availability, which might need some tune-ups with the support of expertise in this regard. Otherwise, you may realize numerous performance issues, memory leaks, server crashes etc.

Incentivized

While deploying docker images on kubernetes pods I must say Codefresh helped me a lot. It has made my work easy as an Automation tool. I can setup a simple pipelines to automate my build for kubernetes. but for more complex pipelines Codefresh need some improvement

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

• Continuous Integration and Continuous Development. we can setup jobs that automatically triggered when there is any changes in code and starts building up the build images automatically and then pushing images to Container Registry
• We can involve Version control system like github, bitbucket, gitlab etc for integration of Codefresh with our code stored in these Version control systems.
• On the failure of any jobs/pipeline Codefresh can also send Notification on our email.

Incentivized

• tomcat is just part of the J2EE specification implementation, majorly focusing on the servlet (front-end) part. If you requires the full J2ee stack, like EJB support, you need consider other containers like Weblogic
• tomcat's cluster level support is very limited
• tomcat's admin/configuration is not so intuitive, and default logging needs a lot of improvement

Incentivized

• With Codefresh it's become hard to handle complex pipelines
• Need to focus more on Documentation part
• UI can be more attractive
• Security can be more increased

Incentivized

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

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

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

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 applications are superior to Tomcat, but most times unnecessary for the vast majority of web applications developed in Java.

Incentivized

It's very scalable It is cost effective It easily get integrated with third party tools It easily get integrated with Kubernetes Docker.

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

• It has simplified administration efforts, thus saving much time to focus on other projects and issues.
• It saves us in costs, as there are no licensing requirements.
• It gives us the ability to manage all of our java applets in one place, so as to be able to host both development and production systems on one server.

Incentivized

• Positive:
• As an Automation tools I must say it has reduced manual labour , reduced errors and improved quality of work.
• It easily get integrated with third party tools which increases ease ness in our work
• Negative:
• Although being a very good tools in CI/CD
• It requires improvement in UI, it's speed, security, optimization.

Incentivized