DB Optimization - Cache Service Callback

[k-macmillan]

User Story - Business Need

Reducing the number of queries against our data is necessary to maintain a stable product. Collection of bearer tokens is done on every callback update status.

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Notify reliability dev
I want to reduce unnecessary DB calls
So that our db is only used when necessary

Additional Info and Resources

It all starts inside check_and_queue_service_callback_task and you likely want a dataclass with the following fields:

• id
• url
• bearer_token (set with Encryption.encrypt)
• include_provider_payload
• callback_type

⚠️ json.dumps does not like bytes

Acceptance Criteria

• Uses a dataclass for the necessary fields of ServiceCallback (see Additional Info)
• Uses Encryption.encrypt method and Encryption.decrypt
• Uses @cached(cache=TTLCache(maxsize=1024, ttl=600))
• 10 notifications sent should query the database at most once per worker
• Tested with a callback that requires bearer tokens
• SQS callback not forgotten
• This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

Should be no difference for end-users.

Potential Dependencies