Conversation
| language="python" | ||
| /> | ||
| <CardLink | ||
| label="Transactional Outbox" |
There was a problem hiding this comment.
I still prefer calling it something else like "Workflow Outbox" or "Durable Outbox."
I also expect some theory-purists might take issue with our use of the word "transactional". The word "atomic" might be a stretch too... it's certainly not "isolated" - someone can observe the system in a midway state potentially for a long period of time.
There was a problem hiding this comment.
It's the common name for this pattern, and it's what people (or agents) will search for.
There was a problem hiding this comment.
You can certainly use the name in the text when referring to the thing. You can even write a section called "workflow outbox vs transactional outbox." I think that could be a more interesting title to someone who's new.
There was a problem hiding this comment.
I think people will be looking for the title "transactional outbox" specifically. "Atomic" is being used correctly, it means "all or nothing" and is not the same as "isolated" (but the normal transactional outbox pattern isn't isolated either as it relies on an async background process).
No description provided.