Skip to content

Real-Time is not possible on Node.JS#99

Open
minecrawler wants to merge 1 commit into
azat-co:gh-pagesfrom
minecrawler:patch-1
Open

Real-Time is not possible on Node.JS#99
minecrawler wants to merge 1 commit into
azat-co:gh-pagesfrom
minecrawler:patch-1

Conversation

@minecrawler

Copy link
Copy Markdown
Contributor

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.

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`.
@wkoncki

wkoncki commented Sep 22, 2017

Copy link
Copy Markdown

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

in process control and enterprise systems to mean "without significant delay"

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants