sharded-queue 0.0.5

Sharded queue implementation

Sharded queue

Introduction

Imagine your job queue operates at very high rps and needs distribution over multiple workers. But you need to keep context-sensitive requests in same thread and manage thread request processing priority. In other words, sharded queue is a queue with sub-queues inside. Tasks are executed in FIFO order and you define how to route them correctly per handler basis.

Installation

Install using pip

pip install sharded-queue

Getting started

There are some roles that you need to understand:

• request a simple message that should be delivered to a handler
• handler request handler that performs the job
• route defines internal queue that is used for request distribution
  • thread a group of context-sensitive requests
  • priority can be used to sort requests inside the thread

Let's start with a simple notification task that is shared by 3 threads and there are no priorities. Notice, that handler methods are written using batch approach to reduce io latency per each message.

from sharded_queue import Handler, Queue, Route

class NotifyRequest:
    '''
    In this example we have simple notify request containing user identifier
    In addition, the value is used to shard requests over worker threads
    '''
    user_id: int

class NotifyHandler(Handler):
    @classmethod
    async def route(cls, *requests: NotifyRequest) -> list[Route]:
        '''
        Spread requests by 3 threads that can be concurrently processed
        '''
        return [
            Route(thread=request.user_id % 3)
            for request in requests
        ]

    async def perform(self, *requests: NotifyRequest) -> None:
        '''
        Perform is called using configurable batch size
        This allows you to reduce io per single request
        '''
        # users = await UserRepository.find_all([r.user_id for r in requests])
        # await mailer.send_all([construct_message(user) for user in users])

Usage example

When a handler is described you can use queue and worker api to manage and process tasks. Let's describe runtime components:

• coordinator is a mechanism that helps worker findout the queue
• queue is used to register requests
• storage a database containing queue data
• worker performs requests using handler

from asyncio import gather
from notifications import NotifyHandler, NotifyRequest
from sharded_queue import Queue, RuntimeCoordinator, RuntimeStorage, Worker


async def example():
    '''
    let's register notification for first 9 users
    '''
    queue: Queue = Queue(RuntimeStorage())
    await queue.register(NotifyHandler, *[NotifyRequest(n) for n in range(1, 9)])
    '''
    now all requests are waiting for workers on 3 notify handler tubes
    they were distributed using route handler method
    first tube contains notify request for users 1, 4, 7
    second tube contains requests for 2, 5, 8 and other goes to third tube
    '''
    futures = [
        Worker(RuntimeCoordinator(), queue).loop(3),
        Worker(RuntimeCoordinator(), queue).loop(3),
        Worker(RuntimeCoordinator(), queue).loop(3),
    ]
    '''
    we've just run three coroutines that will process messages
    workers will bind to each thread and process all messages
    '''
    await gather(*futures)
    '''
    now all emails were send in 3 threads
    '''

Drivers

There are several implementations of components:

• RedisCoordinator persist queue binds in redis using setnx api
• RedisStorage persist msgs using lists and lrange/lpop/rpush api
• RuntimeCoordinator persist queue binds in memory and can be used in a simple runtime distribution
• RuntimeStorage persist msgs in dict and can be used in a simple runtime distribution

Handler lifecycle

As you can notice, routing is made using static method, but perform is an instance method. When a worker start processing requests it can bootstrap and tear down the handler using start and stop methods

class ParseEventRequest(NamedTuple):
    '''
    Event identifier should be enough to get it contents from storage
    '''
    event: int

class ParseEventHandler(Handler):
    @classmethod
    async def create(cls) -> Self:
        '''
        define your own handler and dependency factory
        '''
        return cls()

    @classmethod
    async def route(cls, *requests: ParseEventRequest) -> list[Route]:
        '''
        override default single thread tube
        '''
        return [
            Route(settings.default_thread, settings.default_priority)
            for request in requests
        ]

    async def start(self):
        '''
        run any code on worker is bind to the queue
        '''

    async def perform(self, *requests: ParseEventRequest):
        '''
        the handler
        '''

    async def handle(self, *requests: ParseEventRequest) -> None:
        '''
        process requests batch
        ```

    async def stop(self):
        '''
        run any code when queue is empty and worker stops processing thread
        '''

Advanced queue configuration

You can configure sharded queue using env

• QUEUE_COORDINATOR_DELAY = 1
  Coordinator delay in seconds on empty queues
• QUEUE_COORDINATOR_PREFIX = 'lock_'
  Coordinator lock prefix
• QUEUE_COORDINATOR_TIMEOUT = 24 * 60 * 60
  Coordinator lock ttl
• QUEUE_DEFAULT_PRIORITY = 0
  Default queue priority
• QUEUE_DEFAULT_THREAD = 0
  Default queue thread
• QUEUE_TUBE_PREFIX = 'tube_'
  Default queue prefix
• QUEUE_WORKER_BATCH_SIZE = 128
  Worker batch processing size
• QUEUE_WORKER_EMPTY_LIMIT = 16
  Worker empty queue attempt limit berfore queue rebind
• QUEUE_WORKER_EMPTY_PAUSE = 0.1
  Worker pause in seconds on empty queue

You can import and change settings manually

from sharded_queue import settings
settings.coordinator_delay = 5
settings.worker_batch_size = 64

worker = Worker(RuntimeCoordinator(), Queue(RuntimeStorage()))
await worker.loop()