This gist showcases how DuckDB on nodejs fails silently to handle the same read only database on multiple nodejs processes when running in cluster mode. This behaviour is consistent with the duckdb CLI interface.
Calling (using an in :memory: database)
node cluster.js
outputs the correct result
Forked child
Forked child