←back to thread

Serving 200M requests per day with a CGI-bin

(jacob.gold)
156 points feep | 1 comments | 04 Jul 25 13:16 UTC | HN request time: 0.212s | source
Show context
Traubenfuchs ◴[04 Jul 25 13:55 UTC] No.44464611[source]▶
Try an apache tomcat 11 next. You can just dump .jsp files or whole java servlet applications as .war file via ssh and it will just work!

One shared JVM for maximum performance!

It can also share db connection pools, caches, etc. among those applications!

Wow!

replies(4): >>44464663 #>>44464883 #>>44470934 #>>44477758 #
atemerev ◴[04 Jul 25 14:01 UTC] No.44464663[source]▶
I miss this so much. Deployment should be just copying the file (over ssh or whatever). Why people overcomplicated it so much?
replies(5): >>44464765 #>>44464831 #>>44465743 #>>44466836 #>>44467142 #
1. mrkeen ◴[04 Jul 25 19:20 UTC] No.44467142[source]▶
Perhaps. Over SSH? With a password or with a key? Do all employees share the same private key or do keys need to get added and removed when employees come and go. Is there one server or three (Are all deployment instructions done manually in triplicate?). When tomcat itself is upgraded, do you just eat the downtime? What about the system package upgrades or the OS? Which file should be copied over - whatever a particular Dev feels is the latest?