Is the Node server the only option to support maximum level of requests in an application?

Asked

Viewed 259 times

0

For an application project you will need to support on the server an immense amount of requests such as a e-commerce on the day of black Friday or the server of a game developer on the first day of the release of an ultra awaited game that can only be accessed and downloaded by login, As for example in the case of Diablo 3, would the Node.js server be the only viable option to support the trance without falling? Or Nginx would also be another viable alternative, and OSI would be discarded?

  • If I’m not mistaken, Uber uses Node.js, but it is not only the technology used in the backend that will dictate whether or not the server supports

  • Did the answer solve your question? Do you think you can accept it? See [tour] if you don’t know how you do it. This would help a lot to indicate that the solution was useful for you. You can also vote on any question or answer you find useful on the entire site (when you have 15 points).

1 answer

4

The type of technology used affects the ability to meet demand a little, but what really matters is the overall architecture, is to know what you’re doing. The least of the problems is usually which technology to use.

Anyway I don’t know why Node is being considered as a fast technology. You must have read a lot of article marketer out there. Node is slow. Sure, you can do a lot with it, but you have to do a lot of good to be fast, there are technologies that are much faster until you accept that something is not so good.

Has a website that does independent testing with several Stacks of technologies and shows how each one behaves (gets worse when we talk about latency). Until the 11th. are almost 100% efficiency, including there the ASP.NET Core, it loses only to frameworks experimental. Nodejs appears in 59o. place with only 11% efficiency. So the decision that the question asks must be the opposite of the proposal. Not that it is not feasible to use Node, but it is one of the least viable options.

The IIS has improved a lot, but it will not be the best performance option ever because its goal is to give diverse functionalities and not performances. Even Nginx is not such a quick option. It is when compared to more complete servers, but it has its cost as well.

Anyway the performance is not the most important and the decision of the best technology goes through wide analysis and deep observation of the concrete case, and this can only be done by someone very experienced and who is not biased, besides having all information in hand. But the most important thing is that the decision is not made upon false information.

  • 1

    I think the person confuses the use of memory by connection with speed

  • 4

    @Sorack maybe, but I believe he even loses out on this. I can’t imagine how a JS-based technology can be cost-effective in memory. Javascript is one of the biggest memory wasters you have.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.