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

Implementation Plan: Fine-grained API response cache management #1969

Closed
Tracked by #383
sarayourfriend opened this issue May 2, 2023 · 1 comment
Closed
Tracked by #383
Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧭 project: implementation plan An implementation plan for a project 🧱 stack: mgmt Related to repo management and automations

Comments

@sarayourfriend
Copy link
Contributor

Description

Project proposal: https://docs.openverse.org/projects/proposals/trust_and_safety/content_report_moderation/20230411-project_proposal_content_report_moderation.html#cache-management-requirement-5

Please refer to the project proposal section linked above for the requirements of this plan.

To reiterate what is said in the proposal, the plan must include a list of every single view that returns content with a specific determination for whether cache management can be done via Cloudflare's tools or if we need to implement the new Redis cache strategy for the view.

@sarayourfriend sarayourfriend added 🟨 priority: medium Not blocking but should be addressed soon 🌟 goal: addition Addition of new feature 📄 aspect: text Concerns the textual material in the repository 🧱 stack: mgmt Related to repo management and automations 🧭 project: implementation plan An implementation plan for a project labels May 2, 2023
@sarayourfriend sarayourfriend self-assigned this Jun 1, 2023
@sarayourfriend sarayourfriend removed their assignment Jun 30, 2023
@sarayourfriend
Copy link
Contributor Author

This part of the implementation plan needs a significant re-thinking in light of the discussion: #2453.

The work proposed for this plan is significant and complex. If we can avoid it by reducing the amount of edge caching we rely on, it would save us a lot of process and implementation work.

Closing this for now and I will revisit this plan next week with a proposed alternative for us to discuss and work though the decision making process with.

@sarayourfriend sarayourfriend closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧭 project: implementation plan An implementation plan for a project 🧱 stack: mgmt Related to repo management and automations
Projects
Archived in project
Status: Accepted
Development

No branches or pull requests

1 participant