Apache Tomcat VS WildFly

Manual instrumentation allows you to define your Spans within the code itself rather than relying on automatic instrumentation finding the entry point for a trace. Manual instrumentation is especially helpful for applications that don’t use an application server such as Tomcat, JBoss, or Jetty.

99% is a huge exaggeration. Two essential deployment tools off the top of my head: https://tomcat.apache.org/ https://docs.jboss.org/author/display/AS71/Developer%20Guide.html

Do we still enjoy it? We are running many Vaadin apps in production since that first one. If there are not any specific requirements we use a “modular monolith” concept, which fits our stack best. We pack applications as WAR and deploy them under Apache Tomcat. And yes, we enjoy the development process. It’s very straightforward and Vaadin and SpringBoot fit together well.

JasperReports Server Community requires a Java application server and a database to create a repository in order to work properly. After downloading JRS, the installation process can install Tomcat server and PostgreSQL database automatically for us and the services will run depending on the Jasper server. It's also possible to connect JRS to services already installed on the server. Moreover, while the free version supports the MySQL server, with the paid version you can also use commercial databases, for example, ORACLE Database, as a data repository.

Regarding the venerable Tomcat, they [somewhat] recently added support for Unix domain sockets.

* https://github.com/apache/tomcat/pull/402

* https://github.com/apache/tomcat/pull/532

We fronted the server with haproxy LTS. Our initial testing showed roughly and order of magnitude [10x] increase in the number of requests the server could handle.

It's not completely plug-and-play; we still had a write a custom valve to set the request remote ip address and some other TCPish stuff, but nevertheless the capacity far outstripped our need for the technology.

Example: Little Johnny was developing a Java web app and thinking about how he would configure Tomcat to listen to requests and redirect the data into his app... until he remembered this would violate Factor 7! Instead, he decided to declare Jetty as a dependency, keeping the HTTP service inside the app instead of configuring an external web server and then injecting its functionalities. Now, whenever he wants to instantiate another server for this app, all he has to do is installing dependencies and running the app, isn't it convenient?

Apache has multiple "server" projects- Apache HTTP Server is an a server program written in C, while Apache Tomcat is a server program written in Java.

Multiple applications in the same JVM? Wildfly, Tomcat, Jetty.

Download Apache Tomcat from the project website. Make sure to download the correct version, depending on the Java and Servlet API versions that your application uses. For example, in the case of Vaadin applications, download Apache Tomcat version 9.

user@opensuse:~/rpmbuild> cat SPECS/wildfly-26.1.3.spec %define _topdir /home/user/rpmbuild Name: wildfly-servlet Version: 26.1.3.Final Release: 4%{?dist} Summary: WildFly 26.1.3 Application Server License: Apache License, Version 2.0 URL: https://wildfly.org/ Source0: https://github.com/wildfly/wildfly/releases/download/26.1.3.Final/wildfly-servlet-26.1.3.Final.tar.gz #BuildRequires: java-1_8_0-openjdk-devel #BuildRequires:  maven #BuildRequires:  git #BuildRequires:  subversion #BuildRequires:  xmlstarlet %description WildFly is a flexible and lightweight open-source application server. %prep %setup -q %build %install rm -rf %{buildroot} mkdir -p %{buildroot}/opt/wildfly cp -rp * %{buildroot}/opt/wildfly %files %defattr(-,root,root) /opt/wildfly %post ln -s /opt/wildfly/bin/standalone.sh /etc/init.d/wildfly systemctl enable wildfly.service %preun systemctl disable wildfly.service %postun rm -f /etc/init.d/wildfly %clean rm -rf %{buildroot} %changelog * Mon Feb 27 2023 user [email protected] - 26.1.3-1 - Initial package creation