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

refactoring of transaction processing for storage #1474

Open
1 of 13 tasks
kakcy opened this issue Jan 22, 2025 · 0 comments
Open
1 of 13 tasks

refactoring of transaction processing for storage #1474

kakcy opened this issue Jan 22, 2025 · 0 comments
Assignees

Comments

@kakcy
Copy link
Contributor

kakcy commented Jan 22, 2025

RunTransaction, Begin, etc. are called and transaction processing is performed at the API layer.

Example of code that is an issue

Solution

  • Define the necessary API for each storage layer using Interface and abstract the storage layer.
    • In the storage layer, embed the interface for each storage and move the implementation necessary for DB operations to the storage layer.
    • The API layer calls the above Interface and does not directly perform DB operations.
  • If transaction processing is required in the API layer, use RunTransactionAPI provided in the DB client to perform transaction processing.
    • If we want your API layer to handle transactions across different storages, we can do so by creating storage instances using the same DB client instance.

Package

  • account

  • auditlog

  • autoops

  • environment

  • eventcounter

  • experiment

  • feature

  • notification

  • push

  • experimentcalculator

  • mau

  • opsevent

  • subscriber

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant