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

JDBC Store Implementation #6

Open
maciejwalkowiak opened this issue Dec 10, 2024 · 1 comment
Open

JDBC Store Implementation #6

maciejwalkowiak opened this issue Dec 10, 2024 · 1 comment

Comments

@maciejwalkowiak
Copy link
Collaborator

While DynamoDB and Redis are both natural candidates for storing idempotency keys and values due to their key-value nature and built-in TTL, for many applications that use only RDBMs it would be more convenient to not add new infrastructure just for idempotency purposes.

I am proposing to add a JDBC based implementation of the store. Either a generic one for all/most RDBMS, or one specific to Postgres.

@arun0009
Copy link
Owner

Interesting idea. It's definitely do-able but a few questions:

  1. With a JDBC Store, the performance would be something to think about. Since we have to make that check while processing request we have to be quick enough while providing idempotency.
  2. JDCB won't have a TTL feature, so think of some cron job event that runs and deletes idempotent rows once they expire. Can we use maybe Spring JDBC Template of JPA and try to implement it for Postgres/MySQL in one module? The way to delete the idempotent rows would possibly differ for Postgres & MySQL.

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

No branches or pull requests

2 participants