Deno: Question: Is Deno limited to a single thread per OS Process?

[akircher]

Apologies if this out of scope. I am also out of my technical depth.

As background, CouchDB currently uses their own C/C++ bindings to Spidermonkey in order provide the JS runtime for its maps, views, validation, etc. As this is burdensome, their JS runtime is quite old and they seem to be looking for an alternative to maintaining their own bindings.

I suggested using Deno but their feedback was that because (of v8?) deno can only one be single threaded per OS Process. And therefore not NIF-able in Erlang. Is this true? If so, are there other use cases outside of CouchDB where this limitation would be problematic to adoption? Would it be hard to overcome this limitation?

[kevinkassimo]

I believe workers are essentially separate threads. Deno has basic worker implemented but have not yet exposed to the userland. In the meantime Deno, like Node, uses a thread pool internally for async io tasks.

[akircher]

Somewhat related to #1666

[bartlomieju]

FYI @akircher Web Workers were released with Deno v0.3.6

[akircher]

Thanks @bartlomieju I will update the thread in couchdb!

[bartlomieju]

@akircher can we close this issue now?

[akircher]

Yes, my mission was accomplished by getting Deno on the CouchDB team's radar.