Serve frontend using thttpd #42

New Issue

Jef Roosens · 2021-09-24T12:04:01+02:00

Jef Roosens commented

2021-09-24 12:04:01 +02:00

This might be a dumb idea, but I think it'd be interesting anyways.

The idea atm is to serve the frontend using the backend's Rocket server. This works perfectly fine, but it might not be the most efficient we can be. I know that thttpd is a really fast web server designed for serving static files, e.g. our frontend. Therefore I'd like to consider separating the frontend & backend using separate web servers. Backend gets handled by Rocket, and the frontend by thttpd.

Wether we should combine this into a single container or split it into multiple is still up for debate. A single container would be easier te manage, but it does violate the principle that each container should only do one thing.

One issue with this is the fact that thttpd only support HTTP/1.1. This'll have to be investigated.

Food for thought.

This might be a dumb idea, but I think it'd be interesting anyways. The idea atm is to serve the frontend using the backend's Rocket server. This works perfectly fine, but it might not be the most efficient we can be. I know that [thttpd](http://www.acme.com/software/thttpd/) is a really fast web server designed for serving static files, e.g. our frontend. Therefore I'd like to consider separating the frontend & backend using separate web servers. Backend gets handled by Rocket, and the frontend by thttpd. Wether we should combine this into a single container or split it into multiple is still up for debate. A single container would be easier te manage, but it does violate the principle that each container should only do one thing. One issue with this is the fact that thttpd only support HTTP/1.1. This'll have to be investigated. Food for thought.

Jef Roosens added the

Idea

label 2021-09-24 12:04:01 +02:00

This repo is archived. You cannot comment on issues.