Real-Time is not possible on Node.JS #99
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because Node.JS is a garbage-collected language with a work-queue. That means there are no guarantees for runtimes, hence no real-time guarantees. Maybe you wanted to use a different meaning here, but the word is just wrong. See for example the definition on [Wikipedia](https://en.wikipedia.org/wiki/Real-time_computing), which quotes `Ben-Ari, M., "Principles of Concurrent and Distributed Programming", Prentice Hall, 1990. ISBN 0-13-711821-X. Ch16, Page 164`.
|
This heavily depends on how you define "real-time" in your system. In programming sense of the word node may not make real-time possible but node based systems can be "real-time" from more business oriented perspective. The very article you quoted mentions that
If you are fine with business definition of real-time then node can give you a real-time web application. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because Node.JS is a garbage-collected language with a work-queue. That means there are no guarantees for runtimes, hence no real-time guarantees. Maybe you wanted to use a different meaning here, but the word is just wrong.
See for example the definition on Wikipedia, which quotes
Ben-Ari, M., "Principles of Concurrent and Distributed Programming", Prentice Hall, 1990. ISBN 0-13-711821-X. Ch16, Page 164.