ADR about Application Context Supporting Different Implementations Per Thread

[halprin]

Description

Wrote an ADR about the enhancement made to ApplicationContext and a bit about load testing.

Issue

#1122.

Checklist

• I have updated the documentation accordingly

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 1122 - Partially compliant Fully compliant requirements: Sign Flexion and CDC up for the Locust preview program. Implement load test in internal including authentication against the token endpoint, testing other endpoints, and ensuring it works for longer durations and locally. Set up a GitHub Action to run tests on a schedule. Update existing ADR and/or create new one. Update readme with how to run and modify load tests in deployed environments. Configure test criteria in Azure. Add comments to app context and places where .getImplementation is used instead of @Inject. Investigate metadata endpoint failure in load test. Look into why failing to link metadata results in 5XXs. Set up mock RS endpoints for load testing. Rename internal load testing. Not compliant requirements: ADR about setting the per-thread RS implementation when a new API call is created that calls RS. Look at why load tests cause 499s again.

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Complexity Concern The new ApplicationContext#registerForThread method introduces complexity and potential for bugs, especially in multithreaded environments. This needs careful review to ensure it doesn't introduce concurrency issues. A new method was added called `ApplicationContext#registerForThread`.

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.

[saquino0827]

That's pretty cool

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud