ticketing 0.0.2

Distributed ticket lock client

Ticketing - Distributed Ticket Lock Client

An asyncio client for a network distributed lock ("ticket") service. Acquire a named lock with a wait budget and a lease, get a monotonic fencing token, run your critical section, then release.

Document

• Ticketing Online
• Example

Support Platform

• Java, Kotlin
• Javascript, Typescript
• C#
• Python
• Go
• Ruby
• C/C++ (Vcpkg)

Install

pip install ticketing

Usage

import asyncio
from saro_ticketing import TicketBroker


async def main():
    broker = TicketBroker.connect("127.0.0.1:5225", "127.0.0.1:5226")
    try:
        await broker.wait_ready(5)

        ticket = await broker.acquire("order-42", wait=5, lease=30)
        try:
            # ... critical section, guarded by ticket.token at the resource ...
            print("token:", ticket.token)
        finally:
            await ticket.release()
    finally:
        broker.close()


asyncio.run(main())

wait and lease accept either a number of seconds or a datetime.timedelta. wait=0 waits indefinitely; the server enforces the wait, so giving up never strands a lock. The lease is the safety net that frees the lock if this client dies without releasing.

A Ticket is also an async context manager, releasing on exit:

async with await broker.acquire("order-42", wait=5, lease=30) as ticket:
    ...  # critical section

Notes

• One address is held with two connections to the same node; two or more addresses form a cluster the broker fails over between.
• Everything runs on a single event loop, so the client keeps no locks of its own — a coroutine holds the loop across the read-modify-write of its internal state.