Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Investigate Database Transactions #10467

Open
pixiwyn opened this issue Aug 22, 2024 · 1 comment
Open

Spike: Investigate Database Transactions #10467

pixiwyn opened this issue Aug 22, 2024 · 1 comment

Comments

@pixiwyn
Copy link
Collaborator

pixiwyn commented Aug 22, 2024

Description

Within Postgres/DynamoDB, given a large update, can we convert this to transactions (Kysely?).

Depends on entities being moved from DynamoDB and Opensearch.

Acceptance Criteria

Where we implement transactions first, what needs to be done first, and how would it look upon implementation?

Pain points

  • Large updates will fail, only part of the data is updated, should either all pass or fail.

Notes

@pixiwyn pixiwyn added the Devex label Aug 22, 2024
@TomElliottFlexion TomElliottFlexion added migration do not use and removed migration do not use labels Aug 26, 2024
@pixiwyn
Copy link
Collaborator Author

pixiwyn commented Sep 3, 2024

It seems like it's a little early to point this based on discussion. We've explored dynamodb transaction which are limited and we're still not quite sure how far we'll take postgres.

@akuny adding hold (dx/ox) label for this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Devex/Opex
Development

No branches or pull requests

3 participants