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.

Sign up for GitHub

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

Jump to bottom

Maintenance: Split powertools-idempotency into sub-modules #1467

Open
1 of 2 tasks
scottgerring opened this issue Oct 10, 2023 · 2 comments
Open
1 of 2 tasks

Maintenance: Split powertools-idempotency into sub-modules #1467

scottgerring opened this issue Oct 10, 2023 · 2 comments
Assignees
@eldimi
Labels
enhancement New feature or request priority:3 Neutral - not a core feature or affects less than 40% of users status/staged-major-release This change will go with the next major release v2 Version 2
Milestone
v2

Comments

@scottgerring
Copy link
Contributor

Summary

In V2, we should split powertools-idempotency into sub-modules, so that we have powertools-idempotency containing the interface to the module, and powertools-idempotency-dynamodb providing a DynamoDB-backed concrete implementation.

Why is this needed?

  • Allow us to provide pluggable extensions of the module (e.g., introducing an SQL backend) without increasing the user's deployment size
  • Follow the pattern introduced by the splitting of powertools-parameters in Maintenance: Split powertools-parameters into submodules #1402
  • Force a hands-on review of the module as part of our overall v2 work pipeline

Which area does this relate to?

Idempotency

Solution

No response

Acknowledgment
@scottgerring scottgerring added enhancement New feature or request v2 Version 2 priority:2 High - core feature or affects 60% of the users labels Oct 10, 2023
@scottgerring scottgerring mentioned this issue Oct 10, 2023
Open
2 tasks
@eldimi
Copy link
Contributor

eldimi commented Nov 6, 2023

I can take this

@jeromevdl jeromevdl moved this from Triage to Working on it in Powertools for AWS Lambda (Java) Nov 6, 2023
@eldimi eldimi mentioned this issue Nov 8, 2023
Closed
6 tasks
@jeromevdl jeromevdl added priority:3 Neutral - not a core feature or affects less than 40% of users and removed priority:2 High - core feature or affects 60% of the users labels Nov 8, 2023
@eldimi eldimi mentioned this issue Nov 13, 2023
Closed
6 tasks
@scottgerring scottgerring mentioned this issue Nov 20, 2023
Open
@scottgerring scottgerring added this to the v2 milestone Dec 21, 2023
@scottgerring scottgerring mentioned this issue Feb 13, 2024
Closed
6 tasks
@jeromevdl jeromevdl added the status/staged-major-release This change will go with the next major release label Jun 25, 2024
@jeromevdl
Copy link
Contributor

done with #1558, will be released with v2

@jeromevdl jeromevdl moved this from Working on it to Coming soon in Powertools for AWS Lambda (Java) Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eldimi eldimi

Labels
enhancement New feature or request priority:3 Neutral - not a core feature or affects less than 40% of users status/staged-major-release This change will go with the next major release v2 Version 2
Projects
Powertools for AWS Lambda (Java)
Status: Coming soon
Milestone
v2
Development

No branches or pull requests
3 participants
@jeromevdl @scottgerring @eldimi