Apache Tomcat

We use Apache Tomcat the primary application server for our company's software-as-a-service application. We have used Apache Tomcat since 2008. We use Apache Tomcat due to its many years of industry support and huge user community and ease-of-use. Tomcat is easy to configure and performs well for our needs.

All our development teams use Apache Tomcat. It is our best choice for our servers that run business modules and cron tasks. We use it as well in localhost for testing purposes. We use the Tomcat plugin with Jenkins for deployment.

We use Apache Tomcat to deploy our web applications in our organization. Web app deployment is simplistic with Apache Tomcat. Apache Tomcat also supports modern security demands. This is a lightweight and stable solution for hosting applications. Apache Tomcat has provided a rich API set. Documentations are widely available to learn about Apache Tomcat. Also, we host web application locally before deploying those to the production environment for development and testing purposes.

Apache Tomcat, for us, is used only when we need to stand up an application in our localhost machine. It addresses the need for local servers to test our changes before we push the application to the cloud. As far as I'm aware, it is used by any application that uses the Spring Boot framework when standing the server in the local workspace, so I believe it is used across the whole organization.

We use Tomcat as our Web Application server for small and middle size web application and expose Restful API microservices in our multiple projects. Tomcat provides a rich set of API so we could easy to integrate with our Gitlab pipeline to have full lifecycle CICD or build script to automate all deployment process.

Our organization use Tomcat to deploy mostly light Java based web applications. Many of our applications are being deployed in Apache Tomcat, due to the ease of deployment and cost factoring. We use Tomcat as our main applications server due to its performance and light weight.

We are using Apache Tomcat to deploy our web application; it's a robust servlet container which performs really well in production.

Apache Tomcat is being used in my organization to run seven of my ten applications. It has been our preferred solution for an application server for years as a lightweight and stable solution for hosting applications. It is currently being standardized across the whole company; however, we standardized on it years ago. It solves the problem of providing low-cost application servers that require very little maintenance but also provides excellent scalability at the web tier. The desire to drive down costs, while still providing solid secure solutions was a driving business factor in choosing to move to Tomcat.

We use tomcat bundled with the SpringBoot in Fedex IT departments, majorly for small/middle-scaled and light-weighted web application and RESTful based micro services. Those light applications are supposed to be containerized to support the cloud-native initiative. Also for a quick POC purpose, we use Tomcat as the light solution to host some pure servlet based codes.

My organization offers a web product for mobile operators to expose their own web APIs as a managed service, which is expected to be highly performed since it handles millions of transactions on daily basis. So Apache Tomcat is a part of it by deploying all the web applications/services associated with the product.

Tomcat is utilized across our enterprise as a solid, complaint, j2ee web container.

Tomcat is being used as an application server across the organization. Most of our backend web applications and RESTful APIs run on Tomcat platform. Tomcat is baked into the AMI that is created for AWS and our web applications are pushed into the AMIs using Chef scripts. Then the tomcat server is brought up and applications are deployed.

It is used by our IT department as a main web server. Most of our Java apps are hosted on this web container. We also use Tomcat to run our F5 application. So it acts as the main traffic controller for our domain.

Apache Tomcat is being used to serve as an SSL encrypted web server that hosts an attendance and billing system for a non-profit private school that serves 256 students from parents and other school districts. The attendance and billing system has to be flexible to accommodate students and many school districts that send students to this school. It connects to MySQL which hosts the database and J2E development environment.

We use Tomcat as our web application server to develop marketing content. It is a solid tool with a reliable enduring track record which is something we need for our enterprise. Its popularity across the community helps us leverage what has been done already to speed up our own development by not re-inventing the wheel.

We are using tomcat as a middleware web server for some of our Ellucian products including Degree Works and XE. It will soon be replacing all of our middleware products, particularly Oracle Fusion Middleware.

Tomcat was our main server. We used it both in our local machines and we ran it in our Amazon Web Services host. This was only being used by the engineering team because no other teams needed to know what server we were running. In addition, it was only our web team that dealt with the actual server.

Apache Tomcat served as the Servlet Container for any web-based applications written in Java. It was used throughout the organization for a number of different products.

In my company this software is used to deploy every web app that we produce. Each department of my company develops web apps that are suitable for Apache Tomcat; this software is our official servlet container. We configured it to handle hundreds of concurrent sessions, SSL connections, and redeploy web apps on the fly and so on.

Apache Tomcat is the most widely adopted application server used in our company. We have currently over 2000 Tomcat 6 and Tomcat 7 instances and we're starting the adoption of Tomcat 8. Tomcat is used to run internal applications and hosted applications.