Package grq implements persistent, thread and cross process safe task queue, that uses redis as backend. It should be used, when RabbitMQ is too complicated, and MQTT is not enough (because it cannot cache messages), and BeanStalkd is classic from 21 september of 2007 year, that is hard to find in many linux distros.

GRQ means Golang Redis Queue.

You can support development of this module by sending money directly to author https://www.tbank.ru/rm/r_MarJWHfuBs.aNJjZwPrSm/5tN9636575/

package main

import (
	"context"
	"log"
	"time"

	"github.com/vodolaz095/grq"
)

func main() {
	q, err := grq.New(context.TODO(), "test")
	if err != nil {
		log.Fatalf("%s : while connecting to redis", err)
	}

	for t := range time.NewTicker(time.Second).C {
		err = q.Publish(context.TODO(), t.Format(time.Stamp))
		if err != nil {
			log.Fatalf("%s : while publishing task", err)
		}
		log.Println("Task published!")
	}
}

package main

import (
	"context"
	"errors"
	"log"
	"time"

	"github.com/vodolaz095/grq"
)

func main() {
	const concurrency = 10
	mainCtx, cancel := context.WithCancel(context.Background())
	defer cancel()

	q, err := grq.NewFromConnectionString(mainCtx, "test", grq.DefaultConnectionString)
	if err != nil {
		log.Fatalf("%s : while connecting to redis", err)
	}
	q.SetHeartbeat(100 * time.Millisecond)
	err = q.ConsumeConcurrently(mainCtx, func(ctx context.Context, payload string, indx int) error {
		log.Printf("Consumer %v %s received %v", indx, q.GetID(), payload)
		time.Sleep(time.Second)
		return nil
	}, concurrency)
	if err != nil {
		if !errors.Is(err, context.Canceled) {
			log.Fatalf("%s : error consuming", err)
		}
	}
	log.Printf("Consumer \"test\" was Canceled")
}

Protocol is very simple, it can be used by your favourite redis client, including official redis-cli. Publishing task to queue taskQueue1 with payload 1419719 can be performed by redis command lpush:

$ redis-cli lpush taskQueue1 1419719

If we want task to be executed first, it can be added to queue via rpush:

$ redis-cli rpush taskQueue1 1419719

If we want to notify consumers that task is published, and we don't want to wait, when consumers internal timers triggers, we can send notification that there is event in queue via publish redis command.

$ redis-cli publish taskQueue1 anythingAsPayloadBecauseItIsIgnored

If we want to consume an event from a queue, we can use lpop:

$ redis-cli lpop taskQueue1

and payload of 1419719 will be returned.

If we want to receive notification, when there are new messages in the queue, we can subscribe to this kind of messages easily:

$ redis-cli SUBSCRIBE "redisQueue/testHeartBeat"

The MIT License (MIT)

Copyright (c) 2020 Ostroumov Anatolij

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.