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

EPIC Separating to a Read-Access Database from the primary Database #133

Open
maxime-rainville opened this issue Oct 3, 2023 · 0 comments
Labels

Comments

@maxime-rainville
Copy link
Contributor

Enable (but don’t require) a separate read-only-access database. By isolating read and write operations, the system and infrastructure integrating with the CMS can optimise database resources, enhance performance, and provide better data features.

Big User Story:
As a content manager, I want separate read-access and write-access databases for efficient content retrieval and updates, so that my content has smooth system responsiveness for both manual and automated reading and storing of content and data.

Success Measurement:
Reduction in database latency and improvement in overall system response time during peak database write (typically content management) periods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant