Oracle GlassFish alternatives and competitors

We are using Tomcat and we are making the configuration with the help of Spring Boot only.

Tomcat is cloud-based, and all the microservices are developed in Spring Boot.

One of the most valuable features of Tomcat is its compatibility with the Apache web server and its ease of configuration. It is simple to set up and maintain and allows for easy management of database connections, transactions, and isolation. Overall, Tomcat is a user-friendly application server that makes it easy to manage various aspects of database interactions.

Tomcat is running a lot of services and operating to my requirements. 

One way to improve the solution is by making the logging capabilities of Tomcat better by providing a logger within the server itself and making it easy to access and view the server logs. This can be especially useful when debugging issues with applications deployed on the Tomcat server. By having the ability to view both the application logs and the server logs, you can more easily identify the source of any issues and troubleshoot them more efficiently. Providing a connector or other similar feature that allows you to access the server logs from within your application can also be helpful in this regard. Having access to both the application logs and the server logs can be a valuable resource when trying to identify and resolve problems.

To make it easier to identify and troubleshoot issues, it can be helpful to have a single location where you can view both the application logs and the server logs together. This could include only the debug and error logs, rather than all logs, to make it easier to focus on potential issues. By having all relevant logs in one place, you can more easily scan for problems and identify their source, whether it is within the application or the server. This can save time and improve the efficiency of your troubleshooting efforts.

I have been using Tomcat for approximately five years.

I have not had a problem where the solution failed.

I rate the stability of Tomcat an eight out of ten.

We have approximately 70 people using this solution in my company.

I rate the scalability of Tomcat an eight out of ten.

Tomcat itself does not need any support. Everything is on the internet. Proper documentation is there. I have never tried to contact or ask for support from Tomcat. Wherever there is no support, it is the best support for a solution.

As the CTO, I compared Apache Tomcat with IBM WebSphere Application Server and Oracle GlassFish. In the end, I chose Tomcat because it is easy to understand, well-documented, and has a strong community of users and developers. It is also straightforward to debug any issues that may arise. Tomcat is a reliable and user-friendly choice for an application server.

One of the advantages of using Tomcat is the strong community of users and developers that provides a wealth of knowledge and resources online. If you encounter any issues or problems while using Tomcat, it is likely that others have experienced the same issue and have shared their solutions online. This makes it easy to find answers and get support when you need it. In contrast, IBM WebSphere Application Server has a smaller user base, so there are fewer discussions and resources available online to troubleshoot problems. Tomcat's widespread use and strong online community make it a reliable and supportive choice for an application server.

I find IBM WebSphere Application Server very difficult to configure and with Oracle GlassFish, there is no proper documentation.

Tomcat is best for my use case.

The initial setup of Tomcat is straightforward compared to other options on the market, such as IBM WebSphere Application Server. In contrast to IBM WebSphere Application Server, which can be difficult to configure, Tomcat has a user-friendly setup process. Additionally, Tomcat has a default configuration that is optimized for performance, making it a good choice for those who may not be familiar with configuration settings. The default values in Tomcat are set to the best configuration, ensuring that even those who are not experts in configuration can use Tomcat effectively.

The price of the solution is good.

I rate the price of Tomcat an eight 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.

Our company uses the solution for enterprise clients in the banking and finance industries. 

We use different versions of the open source solution depending on client needs. 

The solution has flexibility and stability.

There is not much ability inside of the solution. The world is going beyond different micro and data-type things like Microsoft Office, so we are not seeing much ability within the solution. 

I have been using the solution for 15 years. 

The stability is rated an eight out of ten. 

The scalability is rated an eight out of ten. 

Technical support does not provide good responses to tickets so is rated a five out of ten.

Neutral

The setup is pretty easy so is rated an eight out of ten. 

The solution is cost-efficient compared to other products. Pricing is rated an eight out of ten. 

I rate the solution a seven out of ten.