That is to say, the server you directly face to users is tomcat or the like, followed by nginx, and behind nginx is c++. There are at least 3 layers. If there is a reverse proxy outside tomcat, it will be 4 layers!
There are indeed too many levels and it looks a bit complicated!
First of all, it is probably too difficult to change the C++ at the end. Generally, this is the part of the code that no one wants to touch or dare to touch.
Considering scaling and performance, a reverse proxy is also a must! But you use nginx only as a reverse proxy, which is a bit condescending. . .
I suggest you take a look at openresty, a full-featured web server based on nginx and a bunch of plug-ins. As you said, just convert the json format to openresty, so easy! At the same time, it can maintain the asynchronous and high concurrency characteristics of nginx! https://openresty.org
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
That is to say, the server you directly face to users is tomcat or the like, followed by nginx, and behind nginx is c++.
There are at least 3 layers. If there is a reverse proxy outside tomcat, it will be 4 layers!
There are indeed too many levels and it looks a bit complicated!
First of all, it is probably too difficult to change the C++ at the end. Generally, this is the part of the code that no one wants to touch or dare to touch.
Considering scaling and performance, a reverse proxy is also a must! But you use nginx only as a reverse proxy, which is a bit condescending. . .
I suggest you take a look at openresty, a full-featured web server based on nginx and a bunch of plug-ins. As you said, just convert the json format to openresty, so easy! At the same time, it can maintain the asynchronous and high concurrency characteristics of nginx!
https://openresty.org
Make a unified access layer, shield the back-end servers of different languages, and present a unified entrance to the web side