5 ms·

OMG. I've set up Confluence servers and Tomcat was the most nightmarish part of that experience. The idea that Tomcat was an actual improvement on something sen

OMG. I've set up Confluence servers and Tomcat was the most nightmarish part of that experience. The idea that Tomcat was an actual improvement on something sends shudders up my spine.

tyingq 6y ago
You would have had to lived through a full blown J2EE app on Websphere/Weblogic/JBoss to appreciate it.
- ralphc 6y ago
  OMG yes. So many times all you needed was what Tomcat delivered, but had to go through the convoluted and slow config of WebSphere. WebLogic was better but that's damning with faint praise.
- gonzo41 6y ago
  Im still in the jboss world. Though we've solved the problem, we just don't ever deploy more than 1 app to a jboss app server. I'm very much ringing the spring bell around my work. but the cutover of all our legacy stuff that is running fine will be decades.
closeparen 6y ago
Tomcat definitely shows its age, but I also see some amusing parallels to modern cloud / IaaS architectures in a heavyweight application that implements standard APIs for code you can HTTP POST to it.
desktopninja 6y ago
TBH, its not Tomcat but the terrible application packaging by Atlasssian. There was a time when they had it right. A single WAR file. Just drop it in the tomcat webapps folder and (depending on your preferred config) boom! Application deployed. Your data and configs lived in the path defined by JVM_OPTION -Duser.home | -Duser.dir or environment variable CONFLUENCE_HOME (IIRC). Backups were a breeze. Just archive the data folder. Updates were a breeze too! just replace the WAR and restart. Case in point Jenkins deployment in tomcat. Ahh super painless. Running multi tomcats on single host for application separation was as simple as CATALINA_HOME and CATALINA_BASE being set. Now we have a spaghetti monster called kubernetes that makes people think their apps will run better in it. Works for some but not for all. very much like that gym membership.

OMG. I've set up Confluence servers and Tomcat was the most nightmarish part of that experience. The idea that Tomcat was an actual improvement on something sends shudders up my spine.

tyingq 6y ago

You would have had to lived through a full blown J2EE app on Websphere/Weblogic/JBoss to appreciate it.

ralphc 6y ago
OMG yes. So many times all you needed was what Tomcat delivered, but had to go through the convoluted and slow config of WebSphere. WebLogic was better but that's damning with faint praise.
gonzo41 6y ago
Im still in the jboss world. Though we've solved the problem, we just don't ever deploy more than 1 app to a jboss app server. I'm very much ringing the spring bell around my work. but the cutover of all our legacy stuff that is running fine will be decades.

closeparen 6y ago

Tomcat definitely shows its age, but I also see some amusing parallels to modern cloud / IaaS architectures in a heavyweight application that implements standard APIs for code you can HTTP POST to it.

desktopninja 6y ago

TBH, its not Tomcat but the terrible application packaging by Atlasssian. There was a time when they had it right. A single WAR file. Just drop it in the tomcat webapps folder and (depending on your preferred config) boom! Application deployed. Your data and configs lived in the path defined by JVM_OPTION -Duser.home | -Duser.dir or environment variable CONFLUENCE_HOME (IIRC). Backups were a breeze. Just archive the data folder. Updates were a breeze too! just replace the WAR and restart. Case in point Jenkins deployment in tomcat. Ahh super painless. Running multi tomcats on single host for application separation was as simple as CATALINA_HOME and CATALINA_BASE being set. Now we have a spaghetti monster called kubernetes that makes people think their apps will run better in it. Works for some but not for all. very much like that gym membership.