Transactional Events
See original GitHub issueWhat are your thoughts on adding some events around the transaction process? For example committing
, committed
, rollingback
, rolledback
? Currently I believe, un-tested, we can listen to query-error
event to determine if their was an error but is there a way to determine if the transaction was committed or rolled back manually?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Transactional events - IBM
Transactional events are triggered when a specific change happens to a business object on the Sterling Order Management side. For example, when an...
Read more >Transactional Events Publishing At Brex | by Yingying Tang
TEP is aiming to provide a strong consistency guarantee between asynchronous event publishing and a database transaction.
Read more >Pattern: Transactional outbox - Microservice Architecture
Solution. A service that uses a relational database inserts messages/events into an outbox table (e.g. MESSAGE ) as part of the local transaction....
Read more >Transaction-aware Event Dispatcher for Laravel - GitHub
This Laravel package introduces Transaction-aware Event Dispatcher. It ensures the events dispatched within a database transaction are dispatched only if the ...
Read more >Transactional Event Definition | Law Insider
Define Transactional Event. means (a) a Change of Control described in clauses (i)(A) or (C) of the definition thereof, (b) a Change of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Our use case is through bookshelf events on the modal and syncing information to our external services. We only want to sync if the entire transaction is successful.
I have a similar use-case. I would like to use postgres as a transactional store and elasticsearch as a read store. When records are updated within a transaction I would like to trigger an event that causes the updated records to be sync’ed to elasticsearch, but only act on it the transaction succeeds. The transaction is created externally to the routines that use the transaction, so they don’t have access to the promise determining commit or rollback. Does anyone in this thread have a decent workaround?