It has a paid versions: plus and enterprise. But actually, I couldn't find any information on their site about what the support covers.
No, it won't. It's basically just a NodeJS application server. On the plus side, you get a dashboard with statistics like latency, memory usages etc. But from your description it seems that it will be a redundant…
Despite a few shortcomings, such as the lack of automatic scaling, it is definitely more stable than, nginx unit, which we had a lot of problems with, due to segfaults and very "tricky" nodejs support.
If I understand the idea correctly, differential is for backend only (microservices architectures). There is nothing about browser support in the docs.
In this type of components, the worst is always the display of parallel events, i.e. events that have the same. I don't see such an example unfortunately.
The question is what about the security of such a solution compared to the self-hosted version of https://www.netmaker.io/.
Nice idea, there is also @babel/plugin-proposal-pipeline-operator which would require much less changes in the code if pipeline operator is introduced in the future. But it requires working babel.
They are so rushed with the numbering, I wonder when they will change to that relative to the year. After all, in a few years there will be a Node 50
Great job, when can we expect native MS Windows support?
Make it open source.
It has a paid versions: plus and enterprise. But actually, I couldn't find any information on their site about what the support covers.
No, it won't. It's basically just a NodeJS application server. On the plus side, you get a dashboard with statistics like latency, memory usages etc. But from your description it seems that it will be a redundant…
Despite a few shortcomings, such as the lack of automatic scaling, it is definitely more stable than, nginx unit, which we had a lot of problems with, due to segfaults and very "tricky" nodejs support.
If I understand the idea correctly, differential is for backend only (microservices architectures). There is nothing about browser support in the docs.
In this type of components, the worst is always the display of parallel events, i.e. events that have the same. I don't see such an example unfortunately.
The question is what about the security of such a solution compared to the self-hosted version of https://www.netmaker.io/.
Nice idea, there is also @babel/plugin-proposal-pipeline-operator which would require much less changes in the code if pipeline operator is introduced in the future. But it requires working babel.
They are so rushed with the numbering, I wonder when they will change to that relative to the year. After all, in a few years there will be a Node 50
Great job, when can we expect native MS Windows support?
Make it open source.