The problem with only use the review tool .. is that you are limited to online tool. How can you make sure the CSS is working, or the the code quality was followed since you are reviewing just the line changes or even worst, how to approve one pull request if you do not test at least locally. You need to keep in mind that, approve one pull request.. you are saying that this feature is ok to merge into another branch .. and this means that the feature are following code conventions, code quality and most important... is working at least happy basic path

But my question is about responsibility. I need check if the e-mail address is available.. And I have one library (javascript/npm library) that check data before post The best place check if the e-mail is available is on my npm library.. or UI (after validate with my library)?

Make sense .. so you use the code review tool just for basic review and then pull and test the code locally

The name has been changed to classcat

And about Preact ? infernojs ?

How about none of them?... :) try to use Css in JS Check this link.. https://objectpartners.com/2017/11/03/css-in-js-benefits-drawbacks-and-tooling/

Use SSR... there are some libraries that can help you with this like this one https://github.com/zeit/next.js/ and severals articles about this.. https://blog.eleven-labs.com/en/react-ssr/ https://medium.com/@phoebe.greig/headache-free-isomorphic-app-tutorial-react-js-react-router-node-js-ssr-with-state-and-es6-797a8d8e493a https://medium.com/@firasd/quick-start-tutorial-universal-react-with-server-side-rendering-76fe5363d6e

And about this... "Additionally, if you need it to be responsive, you probably have to setup a script to ping it every few minutes or something. Otherwise the function can be unloaded, and the next request will cause a whole startup process again. " This is true ? Source: https://dev.to/ridermansb/serverless-is-just-for-image-processing-or-can-i-use-to-build-my-api-d3c/comments/1km5

Thanks Anthony Lapenna nice tips. I replied the Dong Nguyen comment using nginx proxy and works. And yes, now I use network and compose in my code :), thanks for the tips.

This is what I have been done... In default I put a proxy... server { location /api/ { proxy_pass http://api:3000/; } } In frontend Dockerfile I just copy... COPY default /etc/nginx/sites-enabled/ default When I run the front-end app.. I link with my API docker run -d -p 80 :80 --name frontend --link api :api frontend When you link another container, docker update /etc/hosts with container name and API, now works! :) Is better use network over link since link is deprecated. About the api.myapp.com I agree. My API is just a container so its easy, I just need to change the frontend calls and nginx config to point to the right domain. In the feature I will do that :).