Share your experience using Fujitsu Interstage Application Server

I work with Tomcat as a programmer, but not as an administrator. My major use case involves using Tomcat, mostly enclosed in any Java image for a Java application for REST API.

I do not work with the product as a customer, partner, service provider, or seller. Apache is a product that is used in any case. If you are using any API gateway, that could also be part of Tomcat that you are using as a programmer or API programmer. Tomcat is included in those scenarios. As a programmer, I define the ports and maybe define some security, but that is all. There is nothing about CI/CD pipelines for independent deployment of applications into Tomcat. The word is a little different now than it was 10 years ago when I worked with Apache as an application server.

Tomcat brings the biggest benefit through its simplicity. It is not just simple in terms of interface; it is simple for managing or very quickly running this server.

Tomcat's simplicity is very valuable, and the metrics I track to measure Tomcat's performance during high concurrency are mostly basic compared to other products or commercial products.

Tomcat lacks a visual tool for configuring. Everything is from the command line. I would like a visual tool for configuration to be added to Tomcat, as I see this feature missing.

I have been using Tomcat for more than 10 years.

Tomcat is stable and might not have some glitches.

Tomcat is easily scalable.

Everything regarding technical support from Apache is in the documentation or in some discussion portal. I never needed technical support.

I have used something similar to Tomcat, like Jetty. I don't see many differences between Tomcat and Jetty from a technical standpoint from my perspective as a developer.

The installation and deployment of Tomcat is just unzip and running.

On-premises deployment is possible. On-cloud deployment is also possible; this is just a click on that and that is all.

Developing any kind of web application server is time-consuming and expensive, and I can use Tomcat as a commodity, which is an existing tool that everybody uses.

I never calculated the ROI in percentage terms because nobody prepared a business case for what it means to build Tomcat.

I am familiar with pricing for Tomcat. For me, it is open source. Since it is open source, I don't see any fee for that regarding whether the license for Tomcat is usually expensive or quite affordable.

Tomcat is mostly used as an application server, not so often as a load balancer.

I mostly work with Kafka and just tried Amazon MSK, but not in production.

Apache Tomcat is capable of connecting to LDAP for validation of user roles if required. Everything is possible with securing the transport via TLS. There is a capability for protecting administration via the configuration, but I think that is mostly there is everything. I am not sure about encrypting passwords in the properties or if this is already added into Tomcat.

I have not yet used Tomcat's TLS virtual hosting feature and seen benefits from it.

On-premises deployment is possible. On-cloud deployment is also possible; this is just a click on that and that is all.

I would rate this review as a 9 overall.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP) is the deployment of our specific applications.

A specific example of an application I have deployed using Red Hat JBoss Enterprise Application Platform (EAP) is some application pages about educational support from the government that stands out.

Red Hat JBoss Enterprise Application Platform (EAP) fits into that process by helping with scalability, which is the most important factor because the product gives me scalability opportunities, such as G-group or load balance or other options.

The best feature Red Hat JBoss Enterprise Application Platform (EAP) offers is G-group.

When I mention G-group, I am referring to clustering or grouping servers for high availability, which ensures that our application can support load balance and maximum uptime.

Red Hat JBoss Enterprise Application Platform (EAP) has positively impacted my organization by minimizing the downtime of applications, which gives me respect from users.

With time, we get results showing how much downtime was reduced. Clustering is the main standout feature for me.

I think documentation may need improvement for Red Hat JBoss Enterprise Application Platform (EAP).

Additionally, the support feature can be improved.

I have been using Red Hat JBoss Enterprise Application Platform (EAP) for five years.

I previously used Apache before Red Hat JBoss Enterprise Application Platform (EAP).

I gave this review an overall rating of eight.