proposal: Merge backend and frontend into a single service #29
Description
Currently frontend and backend are two separate binaries with frontend depending on the backend. It however means that there is a lot of duplication in the two binaries regarding paths, with one backend JSON, and frontend it to HTML and then serving the website. Given the amount of possible traffic the system gets, this is possibly an overkill, which adds more complexity than it solves. I would propose that the two binaries are merged together into a single one, with a gRPC interface being generated which can be used to communicate. The interface would be generated, and used to communicate between the frontend, and database reading components of the new combined binary. This means that in the future if there is ever a need to split the binary, this will be possible quite easily, with already tested and implemented interface between the two.