Ready Bell

demo.ready-bell.com · live

Live demo

Two small services built on ready-bell. In the first, the backend sends the notification when a slow job finishes. In the second, the backend waits for a notification from an AWS Lambda. Every button below calls the real API at https://demo.ready-bell.com.

1. hello-async: the backend sends Notify

Start a job that pretends to work for a few seconds. When it finishes, the backend sends Notify <uuid> to ready-bell, and your terminal, listening on the same uuid, receives Ready <uuid>. That is the moment to fetch the result.

  1. Pick a uuid

  2. Listen for it in a terminal

    Start nc in a terminal, then paste the Listen line and press Enter. nc prints Registered … right away, then Ready … when the job below finishes. The subscription lasts 120 seconds.

    terminal 
    nc -u ready-bell.com 3137
    paste into nc 
    expected response

  3. Start the job

    POST —

  4. Get the result when Ready arrives

    GET —

2. hello-cloud: the backend waits for Ready

The work runs in AWS. You upload input.txt straight to S3, which triggers a Lambda that writes output.txt and sends Notify <uuid>. The backend listens on the uuid, so the Ready makes it check S3 right away instead of at its next 10-second poll. The event stream shows what the backend does.

  1. Pick a uuid

    Optional: listen for the Lambda's notification yourself. Start nc in a terminal, then paste the Listen line and press Enter.

    terminal 
    nc -u ready-bell.com 3137
    paste into nc 
    expected response

  2. Create the job

    POST —

  3. Watch the backend

    SSE
    disconnected
    1. No events yet.

  4. Check the job

    GET —

  5. Upload the input to S3

    The upload link is only valid for 60 seconds after the POST. If it has expired, POST again with a new uuid.

    PUT —

  6. Download the result from S3

    GET —

Questions, feedback or interested in using Ready Bell?

ready-bell@proton.me

How it works GitHub