Event Queues#2608
Open
sjvans wants to merge 50 commits into
Open
Conversation
vkozyura
reviewed
Jun 3, 2026
vkozyura
reviewed
Jun 5, 2026
t-bonk
reviewed
Jun 17, 2026
| This is also the foundation for [SAGA-style](https://microservices.io/patterns/data/saga.html) compensation across distributed systems: two-phase commits aren't possible once an outboxed call has gone out, so you keep consistency by reacting to outcomes and compensating where needed. | ||
|
|
||
| > [!note] Node.js only | ||
| > Callback events `#succeeded` and `#failed` are currently available in Node.js only. Java doesn't have an equivalent yet, but it's on the roadmap. |
Contributor
There was a problem hiding this comment.
This feature is requested by stakeholders frequently and would solve many workarounds.
This was referenced Jun 23, 2026
Merged
Contributor
Author
|
@renejeglinsky @smahati fyi: @dimamost to check for missing java content, then we can merge |
| } | ||
| ``` | ||
|
|
||
| Some services - `cds.MessagingService` and `cds.AuditLogService` - are outboxed by default. See [*Auto-Outboxed Services*](../guides/events/event-queues#auto-outboxed-services) in the common guide. |
Contributor
There was a problem hiding this comment.
Suggested change
| Some services - `cds.MessagingService` and `cds.AuditLogService` - are outboxed by default. See [*Auto-Outboxed Services*](../guides/events/event-queues#auto-outboxed-services) in the common guide. | |
| Some services - `cds.MessagingService` and `cds.AuditLogService` - are outboxed by default. See [*Auto-Outboxed Services*](../guides/events/event-queues#auto-outboxed-services) in the Transactional Event Queues guide. |
|
|
||
| ### Scheduling | ||
|
|
||
| `srv.schedule()` queues like `cds.queued(srv).send()`, that is within the current transaction, dispatched after commit, but it **upserts** a singleton task keyed by event name (or by `.as(name)`) instead of inserting a new entry on every call. It accepts optional timing: |
Contributor
There was a problem hiding this comment.
I had issues to understand that "queues" here is a verb and not the noun. But I also do not have an idea to improve it.
Contributor
There was a problem hiding this comment.
Suggested change
| `srv.schedule()` queues like `cds.queued(srv).send()`, that is within the current transaction, dispatched after commit, but it **upserts** a singleton task keyed by event name (or by `.as(name)`) instead of inserting a new entry on every call. It accepts optional timing: | |
| The `srv.schedule()` method queues like `cds.queued(srv).send()`, that is within the current transaction, dispatched after commit. But it **upserts** a singleton task keyed by event name (or by `.as(name)`) instead of inserting a new entry on every call. It accepts optional timing: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.