Cross-process communication about goblero

[didil]

@asbjornu can you please explain the use case ? I'm not sure about what you're trying to achieve

[asbjornu]

@didil, thank you for the swift reply!

I have a project where I spin up two different instances of Gin. I would like to be able to enqueue jobs from these two HTTP servers (let's call them Server A and Server B), while having a third worker process the enqueued jobs. Currently it seems like Goblero can only process jobs enqueued on the same instance of the blero.Blero, within the same OS process.

So I could spin up Goblero processing inside Server A and enqueue jobs in Server A, but if I enqueue jobs in Server B, the Goblero processor within Server A won't see them.

[didil]

@asbjornu ok thanks for explaining. So goblero only aims to solve the in-process job queue part. The implementer is free to choose how jobs are created by your process. For example you could receive them via an http server or by consuming from a redis queue then enqueing them to the Blero instance .

[asbjornu]

I see. Thank you for the rationale and explanation.