Person
Tux240
Capabilities
Contributes to
Async processingCAPAsync processingDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.Job schedulingCAPJob schedulingRunning something later, or on a cadence, without keeping a process alive to do it — a nightly job, a retry in an hour, a report on the first of the month — and knowing afterwards whether it ran.
Entries
Group by
EntrySignals
Contributes to
@cap-js-community/event-queue@cap-js-community/event-queueTransactional processing of asynchronous and periodic events, with instant dispatch over Redis Pub/Sub and load spread across every application instance.community org, cap
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Transactional processing of asynchronous and periodic CAP events
Details
For your agent
- Ref
actor:tux240- JSON
- /actors/tux240.json
- MCP
- Connecting an agent