Thanks, man. Your answer was complete! The problem with ECS that because is not available in Brazil yet. But if the orchestration it's a very complex way probably, I will ignore the problems with latency and start at ECS. Have you one opinion to help me? The latency in Brazil is 30ms out of here the minimum will be around 100ms.

The approach using states. Give us the power over the flows, over what will be rendered by the data, when us work with big applications. This approach seems me more easy for writing TDD/BDD and for maintain the low level of complexity. I hope, help you.

Me too, But I need more informations about sockets because my server is works only realtime server and I'm monitoring only with Process and Memory.

But in GraphQL you have a understandable uri "<host>/<resource>?query=<query-data>" in falcor I don't see this clear, this looks complicate the communicate between services. Or not?

@cengkuru yes only https pages but has one exception for localhost.

If you works only evergreen browsers. I recommend you start learning Service Workers . But if you need now, I did a sample a short time ago maybe can help you.

But I use npm too =/

You don't need using redux! But redux helps you apply a pure funcional programming approach on your application. With redux you gain more control about the flows and the states of your application, is more easy to test and to maintain. It may seem difficult at first, but as you learn becomes easy and amazing. If you need learning more about redux I recommend this amazing tutorial

This is a good ideia, normalize the icons to continue give the same experience. And most applications do this as: slack, facebook, web.whatsapp....

The speed of redis is because persistence happens in memory first and after is "saved in disk". For have low latency you need a database with the same approach like mongodb and if possible run your databeses on SSD instances.