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

Limit dependencies of website on CMS #16

Open
nickick opened this issue Oct 11, 2022 · 1 comment
Open

Limit dependencies of website on CMS #16

nickick opened this issue Oct 11, 2022 · 1 comment
Assignees
Labels
P1 Large amount of significant user impact, a meaningful feature is broken

Comments

@nickick
Copy link
Contributor

nickick commented Oct 11, 2022

Make website not go down if the CMS is down (and vice versa)

@nickick nickick added the P0 Blocking an imminent release, "everything is broken", all hands on deck, etc label Oct 11, 2022
@nickick nickick self-assigned this Oct 11, 2022
@franckc
Copy link

franckc commented Oct 13, 2022

I would not consider this a blocker for launch. But a really good improvement after the launch. Downgrading to P1.

Though it's going to be a bit challenging to implement. How are we thinking it would work?

  • Have the website cache in Redis responses from the CMS so that if the CMS is down it can fetch content from the cache?
  • Put the CMS behind Cloudflare and enable caching? (though I'm not sure it would work without changing the HTTP caching headers returned by Strapi)

@franckc franckc added P1 Large amount of significant user impact, a meaningful feature is broken and removed P0 Blocking an imminent release, "everything is broken", all hands on deck, etc labels Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Large amount of significant user impact, a meaningful feature is broken
Projects
None yet
Development

No branches or pull requests

2 participants