Quantcast
Channel: linuxadmin: Expanding Linux SysAdmin knowledge
Viewing all articles
Browse latest Browse all 17761

Web architecture question - trying to upgrade to http2

$
0
0

Hey fam, trying to upgrade my servers to http2. My current configuration is:

static files (.pug / .styl files generally) -> apache CGIs -> Varnish

My main issue is that Varnish doesn't support http2 and isn't planning to support it, so I need something to replace my reverse proxy. I'm leaning towards switching to nginx for this, which has good http2 support. Wondering how I should architect my server though once I switch. I'm thinking one of two architectures:

static files (.pug / .styl files generally) -> apache CGIs -> Nginx

Basically keep everything the same, except switch to Nginx as a reverse proxy/cache. OR:

nodejs server to compile .pug / .styl files dynamically -> Nginx

Remove apache altogether. My main concern with this is I don't trust the stability of nodejs as much as I do apache. The benefit though would be that with node always running, I wouldn't have to spin up a node instance every time a CGI compiles a file. Right now this takes about 300ms of additional latency to spin up a server and compile. Would appreciate any thoughts/comments/suggestions.

submitted by /u/pwnies
[link] [comments]

Viewing all articles
Browse latest Browse all 17761

Trending Articles