Split up between an actual front-end and application server

[moretea]

Currently the two concerns are conflated in one repository.

It's probably better to have a separate front-end that only has javascript assets that are executed by the client, and the application server that delegates requests the the end servers.

Browsing quickly through the endpoints offered in e.g. https://github.com/microservices-demo/front-end/blob/master/api/user/index.js, it might be more suitable to just handle this with a rewrite rule in the edge-router.

[rberlind]

This would cause a problem in some platforms such as Apcera which use their own built-in router. For instance, on Apcera, we do not run the edge-router service. Instead, we connect browsers directly to the front-end service.

[moretea]

In that case it might make sense to push those assets to a CDN, or have a "fake CDN" by running nginx container that only contains these assets.