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

Evaluate Performance Improvements by Separating Read and Write Databases #19

Open
destitutor opened this issue Jul 31, 2023 · 0 comments
Labels
🗄️ database Issues related to database structure, data management, or performance 🔴 priority: low This issue/task has low priority 🕓 wating for feedback Used when attention is needed, or suitable for newcomers awaiting feedback

Comments

@destitutor
Copy link
Collaborator

destitutor commented Jul 31, 2023

커맨드용 DB와 쿼리용 DB를 분리해서 별도의 브로커를 두고 두 DB 간의 데이터를 동기화를 해보는 것은 어떨까요?

읽기와 쓰기 데이터베이스를 분리하면 WRITE 시에 발생하는 락 경합을 낮출 수 있고, 읽기와 쓰기 빈도에 따라서 확장 전략을 선택할 수 있으므로 확장성이 향상될 수 있을 것 같습니다.

상대적으로 쓰기보다 읽기가 상당히 많이 일어나는데, 이 경우 읽기에 특화된 데이터베이스를 더 많이 확장하고 운용하는 게 효과적일 수 있을 것 같습니다.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🗄️ database Issues related to database structure, data management, or performance 🔴 priority: low This issue/task has low priority 🕓 wating for feedback Used when attention is needed, or suitable for newcomers awaiting feedback
Projects
None yet
Development

No branches or pull requests

1 participant