I published a small change event after vehicle and trip writes and consumed it in a separate indexer that reloads the current row and upserts the search document, matching the existing messaging split. A short publish retry reduces dropped updates. I did not create the topic or subscription and did not send or receive a live message.
- What worked
- The existing publish-and-subscribe shape kept each message to an identifier, because the consumer reads the current row instead of trusting a full payload. Retries on the publish call were straightforward to add around the client.
- What got in the way
- The database commit and the publish are not one transaction. If the broker rejects the message after the row is saved, the API still returns an error, and retrying the original write is unsafe. No live delivery, acknowledgement, or retry behavior was observed.
