←back to thread

Serving 200M requests per day with a CGI-bin

(jacob.gold)
154 points feep | 1 comments | 04 Jul 25 13:16 UTC | HN request time: 0s | 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 #
rexreed ◴[04 Jul 25 14:14 UTC] No.44464765[source]▶
PHP can work the same way. Push / FTP / SFTP PHP file to directory, deployed.
replies(1): >>44465231 #
Twirrim ◴[04 Jul 25 15:10 UTC] No.44465231[source]▶
We used to use symlinks to enable atomic operations, too. e.g. under /var/www/ we'd have /var/www/webapp_1.0, and have a symlink /var/www/webapp pointing to it. When there was a new version, upload it to /var/www/webapp_1.1, and then to bring it live, just update the symlink. Need to roll back? Switch the symlink back.
replies(1): >>44466037 #
trinix912 ◴[04 Jul 25 16:50 UTC] No.44466037[source]▶
Wouldn't that cause problems when someone would find the old version and corrupt the data with it? Or would only the current version be accessible from the outside?
replies(2): >>44466795 #>>44468182 #
1. Twirrim ◴[04 Jul 25 21:59 UTC] No.44468182[source]▶
Your apache/whatever config would be pointed to the symlink location. No one would be able to get at the old versions of the site.

We'd use this approach not just for webapps, but versions of applications we'd build in house, bundles of scripts, whatever.