Now here's why, by using Node.js, you'll only end up “sabotaging” its very advantages, instead of turning it into a true “horsepower” for your app, as you might expect: It's just not the best technology at hand when it comes to heavy computation. adjust your decisions to it: There are plenty of better solutions (other than Node.js) for powering your CPU-intensive app. A CPU-Heavy Application: Using Node.js Is Simply a Bad Ideaįace it, deal with it and. Scan them through, take note all the factors that I'll be outlining and think them through before rushing to use Node.js to power your next project with.ġ. Here are the 3 bad use cases for this JavaScript runtime environment. Specific use cases for which the otherwise flexible and revolutionary web server technology turns out not to be. Even so, there are certain cases when using Node.js is not the best decision you could make. The one where it was just the client who could initiate communication, never the server, as well. It's undebatable: Node.js has practically laid the foundation of the real-time web! The real-time, two-way connection web apps have revolutionized the old web response paradigm.
0 Comments
Leave a Reply. |