4 ms·
Unless I'm missing something, it looks like each Deno.openKv() instance only gets a single queue. For the local version you could get multiple queues by callin
by simonw 3y ago
Unless I'm missing something, it looks like each Deno.openKv() instance only gets a single queue.
For the local version you could get multiple queues by calling Deno.openKv("db-2.db") with different SQLite file paths each time, but that feels like a lot of overhead for a pretty common need.
I guess this is a Deno architectural style thing - maybe when you build complex apps on Deno it's expected that you'll have a microservice style architecture where lots of different scripts work together, each of them with their own KV store and hence their own queue?
- gabeidx 3y agoYou are right, there's only a single queue at the moment. One of the core devs has confirmed this on their discord: https://discord.com/channels/684898665143206084/1156714282533265459/1156750131014668348 https://discord.com/channels/684898665143206084/115671428253... Quoting here: > Correct. Currently a single queue is supported. You could multiplex multiple types of messages on the single queue though.