Go should be faster as a queue worker in almost all cases. If you implemented the actual queue in Go that was likely your mistake, building queues is hard. If y

Go should be faster as a queue worker in almost all cases. If you implemented the actual queue in Go that was likely your mistake, building queues is hard. If you had defered that to something like que (Postgres advisory lock based), Redis or even AMQP it should have run circles around Python.