Which architecture is better in terms of performance and scalability?

Question

Highload

Immediately: it is clear that each project needs its own architecture and there are no templates when it comes to highload.
Often there are solutions in the form of separating servers into front (for rendering pages) and back (for API). In my case, development on node in cluster mode with a balancer on nginx. Each node worker provides both the API part and the rendering of the page, and it seems that this should be good, because. in node io is asynchronous. Due to the fact that all servers are identical - they are easy to scale and deploy (you can end up leaving 2 servers and turning off one at a time with a split architecture, you need 4). And my question is that using a different architecture with a division into the API of the server on the node and the server under the front (let's say on apache + php) can I win something? I wonder if anyone has tested node rendering performance against apache+php.
PS - Abandon server rendering and go to Angular 2 (for example) is not an option.

Answer 1

Tailored for specific tasks.

1. Formalize the tasks that the architecture of your particular project should solve.
   
2. Carry out load testing of the system in accordance with the tasks.
   
3. Build graphs and charts based on the results.
   
4. Examine the result and find bottlenecks.
   
5. Optimize bottlenecks according to tasks.
   
6. profit.
   

Answer 2

Is it cheaper to request a server that generates a front that requests an API, or just request an API? What Angular, what React, what Vue support serverside rendering, and when a user enters the site, he may well get a rendered page, and then load only the API.

Answer 3

If we are talking about a modular architecture, I suggest taking a look:
https://github.com/Dugnist/jsberry
I will be glad for forks or contributors...)