←back to thread

Serving 200M requests per day with a CGI-bin

(jacob.gold)
154 points feep | 2 comments | 04 Jul 25 13:16 UTC | HN request time: 0.41s | 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. nickjj ◴[04 Jul 25 16:11 UTC] No.44465743[source]▶
Docker helps with this nowadays. Of course you need to understand setting things up the first time you do it but once you know, it can apply to any tech stack.

I develop and deploy Flask + Rails + Django apps regularly and the deploy process is the same few Docker Compose commands. All of the images are stored the same with only tiny differences in the Dockerfile itself.

It has been a tried and proven model for ~10 years. The core fundamentals have held up, there's new features but when I look at Dockerfiles I've written in 2015 vs today you can still see a lot of common ideas.

replies(1): >>44466372 #
2. atemerev ◴[04 Jul 25 17:29 UTC] No.44466372[source]▶
Docker makes things opaque. You deploy black boxes and have no idea how the components there operate. Which is fine for devops, but as a software engineer, I prefer to work without Docker (and having to use Docker to install something on a local machine is an abomination, of course).