1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
So, after lots of digging and testing I found the answer for those who come looking in the future:
- Transactions don't "exist" as far as global tables is concerned.
- Transactions will apply within a single region
- Replication of changes made via transactions are replicated async to the other regions that are enabled
- This means that the default "last writer wins" policy will come in to effect.
- TL;DR: Don't rely on transactions if you might be writing to the same thing in multiple regions; e.g. add a 'region' to your PK/SK if you want transaction qualities or some other such mechanism to prevent different regions overwriting each other's transactions. Another alternative would be writing in a single region and reading from others depending on the use case.
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr