-
Notifications
You must be signed in to change notification settings - Fork 14
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
RFC 158 - port Content Store to PostgreSQL on RDS #158
Conversation
Thanks @aldavidson - this seems sensible to me and I'm happy to support. Has any thought gone in to how to mitigate the three points in the consequences section yet? If so it might be worth either expanding on that a bit, or perhaps just noting that while we haven't decided how to mitigate these issues yet we think these are all solvable problems and not blockers. |
@dgm34 I've added a "Possible Mitigations" section, how's that look now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 will be great to see this done!
Co-authored-by: Chris Ashton <ChrisBAshton@users.noreply.github.com>
Co-authored-by: Chris Ashton <ChrisBAshton@users.noreply.github.com>
Co-authored-by: Chris Ashton <ChrisBAshton@users.noreply.github.com>
Co-authored-by: Chris Ashton <ChrisBAshton@users.noreply.github.com>
Thanks for the suggestions @ChrisBAshton ! |
This all makes sense to me 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⭐
Proposal to migrate content-store from legacy MongoDB 2.6 to PostgreSQL on RDS.
Rendered version
Publishing Platform Team's Trello epic
Deadline for comments - Wednesday 10th May 2023