Do it later: queues and events
Published Updated
This is the Learning Atlas from Orbit. Get your invite
HostinginfrastructuredatabasesConcepts and methodology
-
Step 1: Background job
Why this matters here
Start with a signup email that can finish after the account has been created.
In short
A task that runs outside the request a person is waiting for, often through a separate worker or a schedule.
-
Step 2: Message queue
Why this matters here
Put that work in a queue so workers can pick it up as capacity becomes available.
In short
A holding place for messages that another program picks up and processes when it has capacity.
-
Step 3: Pub/Sub
Why this matters here
Next let multiple independent subscribers react to the same announcement.
In short
Publish/subscribe messaging: send an event to a named topic so each interested subscription can receive it.
-
Step 4: Event-driven architecture
Why this matters here
Connect these reactions into an app design while accounting for delays and repeated delivery.
In short
An app design in which parts of the system announce events and other parts react to those announcements.
-
Step 5: Webhook
Why this matters here
Finish by receiving events from external services through verified HTTP notifications.
In short
An HTTP request one system sends to your app when an event happens, such as a payment succeeding.