Clojurians Log v2

I am very glad to have an orderly exposition about WAR files! The page puzzled me a bit and I hope these notes will be constructively helpful: I gather that Pedestal-based WAR files are container-specific: you make a WAR specifically for Jetty, or specifically for Tomcat, etc. That is not just a dependency! It is an architectural consideration that could best be mentioned early in the top section. Likewise, it will be vital for me to figure out, and a rule of thumb would be helpful here, how fastidiously to update the Pedestal WAR to match the container's major version or precise exact minor version. In the Dependencies section, a table of the required websocket-capable container jar for each popular Servlet container would help. (Or aliases in the deps.edn.) The Dependencies section includes some general information, which is inapplicable, for contrast! I had to reread a few times to filter it out. It might be helpful to someone, but perhaps it could be set off in a box to keep it from casting shade on the Pedestal specifics.

Good feedback. It may be the case that we can use more generic Jakarta WebSocket dependencies with a WAR deployment, I cobbled this together in a couple of hours.

Further, in the age of containers, I myself question the need for a WAR-based deployment ... which is funny, because Nubank currently does it that way (because historical reasons, because technical debt, etc.) though we are looking to move past that to embrace the embedded model.

WAR deployment is good insurance. Pedestal and embedded Jetty are less risky (I mean, lower-stakes) if there is a well-lit fallback to transplant the Pedestal-based app on short notice into any blue-chip Servlet container on the planet.